Friday, January 25, 2008
well, the mozilla behavior wrapper for htc's is one thing, getting the cross-browser implementation right is quite another.
this next htc that i'm working on is my "transform" behavior. it's purpose is to allow client-side declarative xml/xsl tranforms:
<style>
#divTransform {
behavior: url(transform.htc);
-moz-binding: url(bindings.xml#transform-moz.htc);
}
</style>
...
<div
id="divTransform"
hrefXML="main.opml"
hrefXSL="main_opml.xsl"
asynch="true"
load="true"
>
loading csweb main opml...
</div>
but that says nothing about how completely different such processing is done in ie v. ff. rather than use a single htc and effectively branch everything anyway using browser detection, i may as well use the behavior binding css differences to do that for me, and encapsulate the separate implementations in separate files. makes much more sense. [but then i didn't do it this way in the end anyway ;-) there turned out to be far more in common than different, so i got my wish in the next paragraph.]
i wish i could keep the interface details in common, though. and really, the logic is the same as well. what i really need is a generic xml processing wrapper. *can of worms, can of worms*
surely that's been done. well, there's the e4x stuff, but not for ie. or json, but that's not the data i'm handling. too bad i'm all done but for the debugging.
[insert hours of elapsed time here]
whew. well, that was interesting. had to get into a whole lot of other materials on the web for this one. pretty cool. that's why i do this shit. still don't have the mozilla version up & running yet, and there are a lot of css changes needed on my site.
primary resources:
i'll continue tomorrow; time to veg now.