<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Beyond DOM</title>
	<atom:link href="http://ajaxian.com/archives/beyond-dom/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/beyond-dom</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Jordan</title>
		<link>http://ajaxian.com/archives/beyond-dom/comment-page-1#comment-260454</link>
		<dc:creator>Jordan</dc:creator>
		<pubDate>Wed, 09 Jan 2008 02:06:19 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3181#comment-260454</guid>
		<description>&lt;blockquote&gt;Recently I have been using (and pretty impressed by) the mootools library. Itâ€™s events class is great for handling this sort of thing. Just write some simple functions to update/manipulate the DOM in accordance with custom events.&lt;/blockquote&gt;
@tj111:
The idea of the post is to go &quot;beyond DOM&quot; which is why MooTools is the kind of tool which the author wants to get rid of. No offence to MooTools.</description>
		<content:encoded><![CDATA[<blockquote><p>Recently I have been using (and pretty impressed by) the mootools library. Itâ€™s events class is great for handling this sort of thing. Just write some simple functions to update/manipulate the DOM in accordance with custom events.</p></blockquote>
<p>@tj111:<br />
The idea of the post is to go &#8220;beyond DOM&#8221; which is why MooTools is the kind of tool which the author wants to get rid of. No offence to MooTools.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tj111</title>
		<link>http://ajaxian.com/archives/beyond-dom/comment-page-1#comment-260442</link>
		<dc:creator>tj111</dc:creator>
		<pubDate>Tue, 08 Jan 2008 19:12:34 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3181#comment-260442</guid>
		<description>Yeah, this gets very annoying, but I have my own workarounds I use.  Recently I have been using (and pretty impressed by) the mootools library.  It&#039;s events class is great for handling this sort of thing.  Just write some simple functions to update/manipulate the DOM in accordance with custom events.  So when new data is received from the server, I can have all necassary objects fire a &quot;onDataChange&quot; event, then just use a simple event listener to handle it.</description>
		<content:encoded><![CDATA[<p>Yeah, this gets very annoying, but I have my own workarounds I use.  Recently I have been using (and pretty impressed by) the mootools library.  It&#8217;s events class is great for handling this sort of thing.  Just write some simple functions to update/manipulate the DOM in accordance with custom events.  So when new data is received from the server, I can have all necassary objects fire a &#8220;onDataChange&#8221; event, then just use a simple event listener to handle it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikael Bergkvist</title>
		<link>http://ajaxian.com/archives/beyond-dom/comment-page-1#comment-260440</link>
		<dc:creator>Mikael Bergkvist</dc:creator>
		<pubDate>Tue, 08 Jan 2008 17:24:17 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3181#comment-260440</guid>
		<description>The XML runtime of widgetplus apps represents the state of the app at any given time, and that runtime sits on the server, and this is why the apps data remains persistent from one session to another.
http://www.widgetplus.com</description>
		<content:encoded><![CDATA[<p>The XML runtime of widgetplus apps represents the state of the app at any given time, and that runtime sits on the server, and this is why the apps data remains persistent from one session to another.<br />
<a href="http://www.widgetplus.com" rel="nofollow">http://www.widgetplus.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: khakman</title>
		<link>http://ajaxian.com/archives/beyond-dom/comment-page-1#comment-260439</link>
		<dc:creator>khakman</dc:creator>
		<pubDate>Tue, 08 Jan 2008 17:13:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3181#comment-260439</guid>
		<description>A higher level DOM abstraction is EXACTLY the way in which TIBCO GI is architected so as to handle increasingly feature rich, full featured Ajax apps.  Instead of working directly with the HTML DOM, TIBCO GI provides an &quot;AOM&quot; -- Application Object Model with which you work.  Then in a MVC  pattern, the Model of the application is used to generate the View -- and it&#039;s the View that&#039;s rendered via the HTML DOM.  There are TIBCO GI apps out there with over 180 modules in them that run over full-workday long sessions.  The abstraction to an Application Object Model makes full featured apps easier to build and manage and serves to assist with better memory management via automated garbage collection when components and data are removed.  The full source of TIBCO GI is @ http://gi.tibco.com.</description>
		<content:encoded><![CDATA[<p>A higher level DOM abstraction is EXACTLY the way in which TIBCO GI is architected so as to handle increasingly feature rich, full featured Ajax apps.  Instead of working directly with the HTML DOM, TIBCO GI provides an &#8220;AOM&#8221; &#8212; Application Object Model with which you work.  Then in a MVC  pattern, the Model of the application is used to generate the View &#8212; and it&#8217;s the View that&#8217;s rendered via the HTML DOM.  There are TIBCO GI apps out there with over 180 modules in them that run over full-workday long sessions.  The abstraction to an Application Object Model makes full featured apps easier to build and manage and serves to assist with better memory management via automated garbage collection when components and data are removed.  The full source of TIBCO GI is @ <a href="http://gi.tibco.com" rel="nofollow">http://gi.tibco.com</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gossi</title>
		<link>http://ajaxian.com/archives/beyond-dom/comment-page-1#comment-260438</link>
		<dc:creator>gossi</dc:creator>
		<pubDate>Tue, 08 Jan 2008 16:16:44 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3181#comment-260438</guid>
		<description>I&#039;m working on gara a eclipse swt/jface clone for javascript. So jsface is maybe the thing you want. It&#039;s about representing javascript objects in widgets. Saving and updating is just a XHR request. Updating the UI is done by just one refresh(); method. I will send this to ajaxian soon as more can be seen, so prepared ;)

There you go: http://gara.creative2.net</description>
		<content:encoded><![CDATA[<p>I&#8217;m working on gara a eclipse swt/jface clone for javascript. So jsface is maybe the thing you want. It&#8217;s about representing javascript objects in widgets. Saving and updating is just a XHR request. Updating the UI is done by just one refresh(); method. I will send this to ajaxian soon as more can be seen, so prepared ;)</p>
<p>There you go: <a href="http://gara.creative2.net" rel="nofollow">http://gara.creative2.net</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Asberry</title>
		<link>http://ajaxian.com/archives/beyond-dom/comment-page-1#comment-260437</link>
		<dc:creator>Dale Asberry</dc:creator>
		<pubDate>Tue, 08 Jan 2008 16:12:54 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3181#comment-260437</guid>
		<description>This is the hard problem we run into, regardless of language... they are cross cutting concerns ;-)</description>
		<content:encoded><![CDATA[<p>This is the hard problem we run into, regardless of language&#8230; they are cross cutting concerns ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://ajaxian.com/archives/beyond-dom/comment-page-1#comment-260435</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 08 Jan 2008 12:46:53 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3181#comment-260435</guid>
		<description>html state management?</description>
		<content:encoded><![CDATA[<p>html state management?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Snowcore</title>
		<link>http://ajaxian.com/archives/beyond-dom/comment-page-1#comment-260434</link>
		<dc:creator>Snowcore</dc:creator>
		<pubDate>Tue, 08 Jan 2008 11:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3181#comment-260434</guid>
		<description>I agree, it becomes a real problem, when your UI is too complicated...</description>
		<content:encoded><![CDATA[<p>I agree, it becomes a real problem, when your UI is too complicated&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

