[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: better (?) than DOM

  • From: "Nathan Young -X \(natyoung - Artizen at Cisco\)" <natyoung@c...>
  • To: "Manos Batsis" <manos_lists@g...>, "XML Developers List" <xml-dev@l...>
  • Date: Thu, 22 Feb 2007 09:45:16 -0800

RE:  better (?) than DOM
I think your points are very good.  I realized looking back at it that the whole "DOM is or might be broken" premise was a bit of a troll.

If you measure success based on how much something is used then DOM is kicking but.  The fact that there is a new layer of APIs coalescing atop the DOM API could be taken as further proof of that success.

Of the examples I sent, the shortcuts for creating nodes was the strangest and at the same time it was the least specific to interface coding in the browser in that many of the contexts in which DOM programming is used require creating and adding nodes.

I'll repost with a little explanation because I'm curious if anyone has seen something like this.  Absent XML4J it's not completely crazy to create violent shortcuts for creating nodes programmatically.  Although it is chained method calls, it comes remarkably close to looking like a markup language:

jQuery('#myDiv').append(
    jQuery.DIV({'class':'big'},
        jQuery.SPAN({id:'one','class':'ps'},
            'Hello Joe', jQuery.I({},'!')
        )
    )
);

If you started with:

<root>
   <div id="myDiv"></div>
</root>

and ran the code shown above you'd end up with:

<root>
   <div id="myDiv"><div class="big"><span id="one" class="ps">Hello Joe<i>!</i></span></div></div>
</root>

---->Nathan


.:||:._.:||:._.:||:._.:||:._.:||:._.:||:._.:||:._.:||:._.:||:._.:||:._.:||:.

Nathan Young
Cisco.com->Interface Development
A: ncy1717
E: natyoung@c...  

> -----Original Message-----
> From: Manos Batsis [mailto:manos_lists@g...] 
> Sent: Thursday, February 22, 2007 4:24 AM
> To: Nathan Young -X (natyoung - Artizen at Cisco)
> Subject: Re:  better (?) than DOM
> 
> Quoting "Nathan Young -X (natyoung - Artizen at Cisco)"
> <natyoung@c...>:
> > [...] The
> > perennial topic is "DOM programming is 
> broken/clunky/doesn't fit task
> > X well and should be replaced/enhanced/etc"
> 
> Whether DOM is broken or not is largely irrelevant IMHO. Browsers have
> built their codebases on lots of legacy stuff that makes the situation
> more complex, for example their distinction between XML and HTML (i.e.
> tagsoup) nodes and hence, the incompatibility between those.
> Interoperability is probably the greatest obstacle.
> 
> 
> [...]
> > I'm not aware of any crosstalk between JS library creators 
> and anyone
> > who may be working on formal enhancements to DOM.
> 
> Making good DOM extensions is not trivial; different code styles and
> backgrounds makes it hard to come up with generic requirements. Some
> people are client-side purists while others demand better integration
> with their server-side logic. In other news, binding data state to UI
> elements or widgets is something XForms tried to do with few 
> followers.
> 
> 
> > I think over the next
> > year or so these libraries are going to consolidate and some good
> > ideas will float to the top.
> 
> Perhaps they will, but the competitive mentality right now 
> leaves little
> room for co-op. Mailinglists where created for the purpose 
> that ended up
> as generic ajax talk.
> 
> 
> > This is a long way from pure DOM programming and it goes deep in
> > javascript only territory.  Parts of it though are pure shortcut
> > across multiple DOM calls.
> 
> I think thats natural. DOM had to address different types of languages
> (as in strongly versus loosly typed) so different implementations of 
> the Fa├žades/utility methods are appropriate in different languages.
> 
> My point is, (i think :-) that DOM more or less did what it had to do
> and the situation you describe concerns not the API but the 
> client-side
> scripting community, the browser vendors and the interaction 
> between the
> different (sub)parties in those.
> 
> Kindest regards,
> 
> Manos
> 

  • References:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.