I was just googling to see if someone else had written an EO wrapper for a DOM Document model, and came up with this gem: XML and WebObjects KeyValueCoding by Michael Henderson.
At first blush, this looks like exactly what I need to do. It should be possible to build a pretty solid/transparent/functional DOM wrapper. Probably in a subclass of EOGenericRecord or something like it.
UPDATE: 2004/06/02 - I got it working quite nicely this morning. I query an XStreamDB database, pull all results, read out the full XML of each result, and then feed these into the wrapper class based on Michael’s XMLKeyValueCoding class. I use lazy binding, so the parse to Document doesn’t happen unless/until it’s needed - this should save a lot of time in cases where the results are used in WODisplayGroups etc…
I’m working on finishing the EOAdaptor for XStreamDB, and one route I’m exploring is taking the source XML from XStreamDB, running it through DOM and then into full EOs. I’ve been playing around with DOM libraries, and just checked out the latest beta of dom4j.
It’s evolved into one sweet library - basically takes the standard Document model, and wraps XPath, XSLT and other goodness around it. They’re even working on adding schema and validation support (which will be very handy for anyone creating XML documents on the fly. Like, say, in APOLLO…
I’ve had this happen several times, so I guess it’s pretty repeatable. If you are editing some text in a multiline text field in form in Safari, hitting undo (command+z) crashes the browser.
Especially frustrating when editing documents in say, a wiki… I was just beefing up my page for the NMC 2004 summer conference, and accidentally deleted a link on the wiki form. I hit undo, hoping to just drop the link back in there, but was greeted instead by a MacOSX Application Crash dialog box.
Feel free to contribute to this weblog. It’s running on Blosxom, and is using a plugin that allows editing of posts via a web browser. All you need to know is the password, and you can create posts.
Editing existing entries
To edit this post, just click the “edit” link below. An editing form will show up, letting you type some text.
Posts should be entered as HTML in order to be formatted properly. It’s pretty straightforward. Just look at the source of this post in the edit page.
This is the place to publish the support (or the lack thereof) for the “Decentralists” in terms of maximizing effectiveness through the use of small, organized, and distributed resources.
In this presentation, we have created three groups who will use a collection of “small” discrete, loosely joined technologies, to argue positions of Centralized, Decentralized, and Mixed implementations of instructional technologies. Participants include those present at our session June 15 as well as other edubloggers who can join us in blogs, wiki, and chat space. Follow the coverage via the EDU_RSS feed.
The nature of a decentralized system can lead to fragmentation - many different types of tools, each with its own pecularities. This can lead to a steep learning curve for users of the decentralized system.
Decentralized systems are generally more reliable than single, monolithic Centralized systems. If one part of a Decentralized system becomes unavailable for some reason, the rest of the system is able to function without it.
Stephen Downes just posted 2 links that might be useful.
Latest issue of JIME. Topic is “The Educational Semantic Web”. This is important because it may form a common way of describing resources in a more distributed way. APOLLO will need to tie into these concepts when they become available.
An article called “Improving Metadata Quality: Augmentation and Recombination” that talks about metadata as a collection of statements about a resource, and the possibility of managing metadata at the statement level. Sound familiar? APOLLO basically does this now.
A bunch of us here in the Learning Commons were poised above our keyboards at precisely noon today - when the available Saddledome seats were released to ticketmaster.ca
Well, the rabid Flames fans basically brought the Ticketmaster server to its knees - search results were displaying an estimate of 15 minutes to find anything, and all tickets were sold out before search results were displayed.
I’m guessing all seats, for both games #3 and #4, were sold out in under 10 minutes. To those lucky enough to sneak through the Ticketmaster screen.
This weblog started out a couple of years ago (first post retained from that era was July 2002 ) as a personal project, run under a beta of Blosxom, and published to my .Mac account. Most of the “early” posts from this era have been dropped, but I kept the ones relating to the projects I was/am working on.
Since then, it evolved to be hosted as a MovableType weblog, and ran on that software for over a year. It was switched back to Blosxom 2.0 in May 2004, and switched once more in September 2004 - this time to Wordpress (which is running the weblog now).