Processing is built on top of Java, which means I have to deal with its various quirks.
My 3D tracker stuff worked fine when I was dealing with just one XML flavour, but I decided to throw another one into the mix. Google's KML is a nasty file format, and setting up my code to work with it is pretty much a game of, how much have I busted what already works? Okay, fix it. And now? Fix that too. And so on.
Still haven't even started parsing KML, but I have a feeling that all the groundwork I'm laying now will make it a breeze, once I get to that point.
5 Responses
Pro
Dave Shea
Processing is built on top of Java, which means I have to deal with its various quirks.
My 3D tracker stuff worked fine when I was dealing with just one XML flavour, but I decided to throw another one into the mix. Google's KML is a nasty file format, and setting up my code to work with it is pretty much a game of, how much have I busted what already works? Okay, fix it. And now? Fix that too. And so on.
Still haven't even started parsing KML, but I have a feeling that all the groundwork I'm laying now will make it a breeze, once I get to that point.
over 2 years ago
Pro
Dan Cederholm
I hear HTML5 is considering a <trkseg> element. Why not.
But seriously, ouch!
over 2 years ago
Pro
Rich Thornett
Manipulating XML in code is always laborious and clunky. You have my sympathies.
Love the visual juxtaposition of code and data in this shot. Neat way to tell the story. (I could feel the pain before I even read your comment.)
over 2 years ago
Pro
Dave Shea
Sure enough, I was right. Slept off the headache and fixed the remaining parsing errors this morning, and then integrating KML was a breeze.
It's almost like I know what I'm doing or something.
over 2 years ago
Can we get a "Do Not Like" button up in here? :P
over 2 years ago