[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: better (?) than DOM
Nathan Young -X (natyoung - Artizen at Cisco) wrote: > jQuery('#myDiv').append( > jQuery.DIV({'class':'big'}, > jQuery.SPAN({id:'one','class':'ps'}, > 'Hello Joe', jQuery.I({},'!') > ) > ) > ); Looks very convenient.Maybe i need to add something like it in sarissa ;-) Cheers, Manos > > 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 >> > > _______________________________________________________________________ > > XML-DEV is a publicly archived, unmoderated list hosted by OASIS > to support XML implementation and development. To minimize > spam in the archives, you must subscribe before posting. > > [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ > Or unsubscribe: xml-dev-unsubscribe@l... > subscribe: xml-dev-subscribe@l... > List archive: http://lists.xml.org/archives/xml-dev/ > List Guidelines: http://www.oasis-open.org/maillists/guidelines.php > >
[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! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|