<?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"
	>
<channel>
	<title>Comments on: Fun and despair with ExtJS</title>
	<atom:link href="http://blog.workaround.org/2008/01/15/fun-and-despair-with-extjs/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.workaround.org/2008/01/15/fun-and-despair-with-extjs/</link>
	<description>Rants, discoveries and my tireless search for perfect Linux tools</description>
	<pubDate>Thu, 04 Dec 2008 21:16:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Christoph Haas</title>
		<link>http://blog.workaround.org/2008/01/15/fun-and-despair-with-extjs/#comment-1696</link>
		<dc:creator>Christoph Haas</dc:creator>
		<pubDate>Mon, 27 Oct 2008 14:22:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.workaround.org/2008/01/15/fun-and-despair-with-extjs/#comment-1696</guid>
		<description>(I wonder if people are ashamed of the things they say. Nicknames in blog comments? Anyway...)

@Animal: I have since worked on a real-life project using ExtJS. The article you commented on is a tad old already. The problem hasn't changed that much though. You say that using "unsupported, ad-hoc code" is a bad idea. But the problem is that there is no real documentation besides the examples and the API documentation. Say I want to understand the purpose of each attribute used in a certain panel in an example. Then I often can't find it quickly (if at all). This is an example I made up but it felt like "TabPanel is derived from GeneralPanel which is a subclass of LayoutThings which is derived from AllThings and FoobarThings which in turn...". You can click your way through but in some cases it's hard to find the actual documentation. ExtJS is too complicated to just throw a few cool demos at the users and have them look up everything else in the API docs. And if you make a mistake in the attributes you just get confusing errors in the Javascript console (no, in most cases I had the debug version lead to different but equaly confusing messages) and the applications stops working. It might be a general problem of UI frameworks. But then we need a good GUI builder or an IDE that lets us click the components together. Writing everything from scratch spending countless hours in the docs has - at least for me - been no joy.</description>
		<content:encoded><![CDATA[<p>(I wonder if people are ashamed of the things they say. Nicknames in blog comments? Anyway&#8230;)</p>
<p>@Animal: I have since worked on a real-life project using ExtJS. The article you commented on is a tad old already. The problem hasn&#8217;t changed that much though. You say that using &#8220;unsupported, ad-hoc code&#8221; is a bad idea. But the problem is that there is no real documentation besides the examples and the API documentation. Say I want to understand the purpose of each attribute used in a certain panel in an example. Then I often can&#8217;t find it quickly (if at all). This is an example I made up but it felt like &#8220;TabPanel is derived from GeneralPanel which is a subclass of LayoutThings which is derived from AllThings and FoobarThings which in turn&#8230;&#8221;. You can click your way through but in some cases it&#8217;s hard to find the actual documentation. ExtJS is too complicated to just throw a few cool demos at the users and have them look up everything else in the API docs. And if you make a mistake in the attributes you just get confusing errors in the Javascript console (no, in most cases I had the debug version lead to different but equaly confusing messages) and the applications stops working. It might be a general problem of UI frameworks. But then we need a good GUI builder or an IDE that lets us click the components together. Writing everything from scratch spending countless hours in the docs has - at least for me - been no joy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Animal</title>
		<link>http://blog.workaround.org/2008/01/15/fun-and-despair-with-extjs/#comment-1695</link>
		<dc:creator>Animal</dc:creator>
		<pubDate>Mon, 27 Oct 2008 13:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.workaround.org/2008/01/15/fun-and-despair-with-extjs/#comment-1695</guid>
		<description>"but unusable to me. It defines all possible parameters and options but those are inherited from one another, some aren’t documented because they are “common”"

That's just rubbish. The inheritance level which each member is from is clearly labeled.

Plus, you can hide all inherited members. Just explore the API browsing UI a litle more. At the top left, there's a button do hide all inherited member so that you can see just what is defined at the current class level.

If you want to cobble up an app from unsupported, ad-hoc code snippets from random places on the web, that's up to you...</description>
		<content:encoded><![CDATA[<p>&#8220;but unusable to me. It defines all possible parameters and options but those are inherited from one another, some aren’t documented because they are “common”&#8221;</p>
<p>That&#8217;s just rubbish. The inheritance level which each member is from is clearly labeled.</p>
<p>Plus, you can hide all inherited members. Just explore the API browsing UI a litle more. At the top left, there&#8217;s a button do hide all inherited member so that you can see just what is defined at the current class level.</p>
<p>If you want to cobble up an app from unsupported, ad-hoc code snippets from random places on the web, that&#8217;s up to you&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JC</title>
		<link>http://blog.workaround.org/2008/01/15/fun-and-despair-with-extjs/#comment-663</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Wed, 13 Aug 2008 03:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.workaround.org/2008/01/15/fun-and-despair-with-extjs/#comment-663</guid>
		<description>The latest version (2.2) weighs in at around 150k (gzipped by the server).</description>
		<content:encoded><![CDATA[<p>The latest version (2.2) weighs in at around 150k (gzipped by the server).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elmar</title>
		<link>http://blog.workaround.org/2008/01/15/fun-and-despair-with-extjs/#comment-380</link>
		<dc:creator>Elmar</dc:creator>
		<pubDate>Mon, 25 Feb 2008 12:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.workaround.org/2008/01/15/fun-and-despair-with-extjs/#comment-380</guid>
		<description>Are you aware that these 500k are cached on the client on subsequent calls? That actually means that you have a lot less traffic than generating UI-stuff on the server. It actually loads processing power off to the client quite nicely. I don´t think it´s a bad idea to do this.</description>
		<content:encoded><![CDATA[<p>Are you aware that these 500k are cached on the client on subsequent calls? That actually means that you have a lot less traffic than generating UI-stuff on the server. It actually loads processing power off to the client quite nicely. I don´t think it´s a bad idea to do this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
