Re: ANN: SDOM project development release 0.4

[Julian Graham <joolean-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

On 12/31/05, Neil Jerram <neil-0S17iFHR5lf2/9iHc7UuXF6hYfS7NtTn@public.gmane.org> wrote:
> I'm afraid that doesn't help me much ... unless there are JDOM
> applications that I could refer to as examples?

I think this is turning into a defense of the DOM spec itself, which I
think would answer most of your questions.  When it comes to JDOM, I'd
say that you'd use it any place you wanted to easily manipulate an XML
document in Java as a tree of nodes instead of as a stream of XML
tokens -- obviously, web applications are a major market for this, but
a trivial non-web application might be... parsing and querying an XML
configuration file.

> But isn't everything event-driven?  As in, execute so-and-so script on
> so-and-so objects when I click on this link?  And in that case, don't
> you need something that amounts to a web browser (or at least, an
> HTML/XML page renderer) to exercise the DOM?

Yes, but the DOM spec allows you to embed event handlers in the
document tree that respond in a cascading fashion to changes in the
document that may or may not be triggered by the user of the embedding
application -- for example, you might have an event handler that sorts
the nodes in a tree by attribute value whenever it's notified by the
DOM that a new node has been added to the document.  You could
certainly implement this at the level of the embedding application,
but I think it's quite efficient to have the DOM handle such flows of
events for you.


Regards,
Julian


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click