Skip to main content

Eggs, Ham, Hell

I like XML, I use it from time to time in the course of my job but find it's tag based structure clumsy to work with in comparison with other alternatives out there. Recently working with some OpenXML code I frequently had to check the validity and structure of XML coming in and XML I was writing to file.

Normally I'd google search a free online XML Parser and check my code is valid. But for this recent task, the amount of XML that needed parsing was quite a lot. I decided to find a tool to compliment my text editor of choice TextWrangler.

It turns out that my Mac already has probably the best lightweight XML validator, parser, and display formatter, namely xmllint. What's even better I discovered a way to use xmllint directly in TextWrangler. Xmllint ships out of the box with OS-X

AndrĂ© Bergonse provides the method to connect TextWrangler to xmllint and process one's XML with a few key presses. So if you use TextWrangler and have a need to work with XML, you will like this.

Comments

Popular posts from this blog

The Winner Takes It All

I attended Scotch On The Road last week. A Coldfusion conference held throughout Europe and managed like a rock tour. It was a good day and I reacquainted myself with ex-colleagues from 3 different companies I have worked for. So it was nice to catch up with all. The session over the day were pretty specialist but a lot devoted to CF9, Adobe's new CFML server. Glad to say it's pretty good and a reasonable advance from CF8. I also won the raffle and have just finished choosing my $2000 worth of software, which will fit nicely onto the Macbook Pro.

I'm out of prison!

Actually I haven't been to prison I have been very busy working every hour I can in iOS development. I am now a iOS contractor with over 2 years experience under my belt and enjoying every minute of it.  I have decided to return to this blog and start sharing again the things I come across on my day to day travels.

Version Diversions

As a contractor I have to be light on my toes when it comes to using my own equipment and maintaining the ability to develop to the correct target version. Apple have recently made this a bit harder for the likes of me with the introduction of Xcode 4.5 (now at 4.5.2) The issue is - from Xcode 4.5, Apple dropped support for older devices that have the Arm processers Arm6. No big deal you may think. But a lot of my clients have clients that denote the minimum target iOS version to build for. This can cause problems and to compound things some directives specify iOS versions that are a) No longer supported by Apple, b) Have no device (both simulator nor handset) to test on. They are now starting to ask about updating their apps for the iPhone 5 resolution. It's hard to tell them that because of their target iOS, this can only be achieved by developing blindly relying on provisioning for device testing and the associated increase in development (known as cost) or increasing the ...