<?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: Dojo Grid Widget Updated. Data Integration and Editing Improvements.</title>
	<atom:link href="http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements</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: sturdyworks</title>
		<link>http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements/comment-page-1#comment-268627</link>
		<dc:creator>sturdyworks</dc:creator>
		<pubDate>Sun, 02 Nov 2008 04:35:10 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements#comment-268627</guid>
		<description>I am most likely an old school client server developer but why in the heck is &quot;dojo.data store based off of a JSON file from a URL&quot; an interesting example. I am interested in displaying the results of a query from a RDBMS like MySQL and the Dojo UI related benefits. This example is just gibberish to me. Might I ask if there is support for that basic column sorting stuff, how about sorting multiple columns, any sort of asynchronous hooks?. I mean in what way is a &quot;based on a file&quot; example useful for a data table grid example? I think either Ajaxian is doing some sort of cut and paste, or Dojo has got a pretty weak table widget.</description>
		<content:encoded><![CDATA[<p>I am most likely an old school client server developer but why in the heck is &#8220;dojo.data store based off of a JSON file from a URL&#8221; an interesting example. I am interested in displaying the results of a query from a RDBMS like MySQL and the Dojo UI related benefits. This example is just gibberish to me. Might I ask if there is support for that basic column sorting stuff, how about sorting multiple columns, any sort of asynchronous hooks?. I mean in what way is a &#8220;based on a file&#8221; example useful for a data table grid example? I think either Ajaxian is doing some sort of cut and paste, or Dojo has got a pretty weak table widget.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sfoster</title>
		<link>http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements/comment-page-1#comment-265973</link>
		<dc:creator>sfoster</dc:creator>
		<pubDate>Mon, 21 Jul 2008 09:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements#comment-265973</guid>
		<description>I cant let the &quot;&#039;X&#039; in dojox stands for experimental&quot; comment stand. Project status is indicated in each dojox project&#039;s README file. The &#039;X&#039; is for eXtensions - some of which are production ready and in regular use. The Grid will eventually move to dijit - when it can meet Dijit&#039;s more stringent requirements - which include fully accessibility, as well as API stability. Other components in dojox will never move to dojo core or dijit - not because they are substandard in any way, but because they are specific in nature and have no place in the core distribution.</description>
		<content:encoded><![CDATA[<p>I cant let the &#8220;&#8216;X&#8217; in dojox stands for experimental&#8221; comment stand. Project status is indicated in each dojox project&#8217;s README file. The &#8216;X&#8217; is for eXtensions &#8211; some of which are production ready and in regular use. The Grid will eventually move to dijit &#8211; when it can meet Dijit&#8217;s more stringent requirements &#8211; which include fully accessibility, as well as API stability. Other components in dojox will never move to dojo core or dijit &#8211; not because they are substandard in any way, but because they are specific in nature and have no place in the core distribution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bryanforbes</title>
		<link>http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements/comment-page-1#comment-265905</link>
		<dc:creator>bryanforbes</dc:creator>
		<pubDate>Thu, 17 Jul 2008 16:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements#comment-265905</guid>
		<description>@Jeria: You can do paging like that if you want; the content going away is the result of the grid being able to handle 100,000 rows of data without it having to load all 100,000 rows at once

@Nosrenda: Dojo 1.2 beta is imminent

@Les: The reason we put the grid in DojoX to begin was so we could do a refactoring like this before dropping it into Dijit.  Right now the API should be mostly stable and we&#039;ll be adding features and stabilizing the grid for 1.3.  A refactor like this shouldn&#039;t be needed for a long time.  That said, you could choose to continue using the 1.1 Grid until 1.3 or later if you prefer.</description>
		<content:encoded><![CDATA[<p>@Jeria: You can do paging like that if you want; the content going away is the result of the grid being able to handle 100,000 rows of data without it having to load all 100,000 rows at once</p>
<p>@Nosrenda: Dojo 1.2 beta is imminent</p>
<p>@Les: The reason we put the grid in DojoX to begin was so we could do a refactoring like this before dropping it into Dijit.  Right now the API should be mostly stable and we&#8217;ll be adding features and stabilizing the grid for 1.3.  A refactor like this shouldn&#8217;t be needed for a long time.  That said, you could choose to continue using the 1.1 Grid until 1.3 or later if you prefer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simongil</title>
		<link>http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements/comment-page-1#comment-265881</link>
		<dc:creator>simongil</dc:creator>
		<pubDate>Wed, 16 Jul 2008 23:04:37 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements#comment-265881</guid>
		<description>I want to use dojo but a kick ass grid is essential to my apps. Unfortunately this still doesn&#039;t make the grade. In this regard, extjs is just so much stronger.</description>
		<content:encoded><![CDATA[<p>I want to use dojo but a kick ass grid is essential to my apps. Unfortunately this still doesn&#8217;t make the grade. In this regard, extjs is just so much stronger.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Les</title>
		<link>http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements/comment-page-1#comment-265878</link>
		<dc:creator>Les</dc:creator>
		<pubDate>Wed, 16 Jul 2008 19:34:14 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements#comment-265878</guid>
		<description>Dojo 1.2 DataGrid is a major refactoring of the previous version - dojox.Grid, but the code still is located in dojox (x stands for experimental).

Does it mean we can expect another major refactoring before the Grid moves to dojo? ... or will it always be a part ot dojox?</description>
		<content:encoded><![CDATA[<p>Dojo 1.2 DataGrid is a major refactoring of the previous version &#8211; dojox.Grid, but the code still is located in dojox (x stands for experimental).</p>
<p>Does it mean we can expect another major refactoring before the Grid moves to dojo? &#8230; or will it always be a part ot dojox?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eyelidlessness</title>
		<link>http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements/comment-page-1#comment-265877</link>
		<dc:creator>eyelidlessness</dc:creator>
		<pubDate>Wed, 16 Jul 2008 18:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements#comment-265877</guid>
		<description>It feels really hackish. No, it&#039;s not an easy task, but doing better is possible. I&#039;ve done it. Unfortunately it&#039;s not a public work or I&#039;d share it. :(</description>
		<content:encoded><![CDATA[<p>It feels really hackish. No, it&#8217;s not an easy task, but doing better is possible. I&#8217;ve done it. Unfortunately it&#8217;s not a public work or I&#8217;d share it. :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nosredna</title>
		<link>http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements/comment-page-1#comment-265876</link>
		<dc:creator>Nosredna</dc:creator>
		<pubDate>Wed, 16 Jul 2008 18:33:52 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements#comment-265876</guid>
		<description>How close is Dojo 1.2 to coming out? I seem to remember that there&#039;s great new debugging stuff coming as well.</description>
		<content:encoded><![CDATA[<p>How close is Dojo 1.2 to coming out? I seem to remember that there&#8217;s great new debugging stuff coming as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeria</title>
		<link>http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements/comment-page-1#comment-265874</link>
		<dc:creator>Jeria</dc:creator>
		<pubDate>Wed, 16 Jul 2008 15:51:58 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/dojo-grid-widget-updated-data-integration-and-editing-improvements#comment-265874</guid>
		<description>I am not so fond that the content goes away when you drag the scrollbar. Why not use a pagination widget (previous and next button to show the next x items)?</description>
		<content:encoded><![CDATA[<p>I am not so fond that the content goes away when you drag the scrollbar. Why not use a pagination widget (previous and next button to show the next x items)?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

