<?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: J2ME: Write Once, Be Disappointed Everywhere</title>
	<atom:link href="http://www.pervasivecode.com/blog/2007/08/19/j2me-write-once-be-disappointed-everywhere/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pervasivecode.com/blog/2007/08/19/j2me-write-once-be-disappointed-everywhere/</link>
	<description>Jamie Flournoy's Software Development Blog</description>
	<lastBuildDate>Sat, 23 Jan 2010 19:19:54 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jamie Flournoy</title>
		<link>http://www.pervasivecode.com/blog/2007/08/19/j2me-write-once-be-disappointed-everywhere/comment-page-1/#comment-1733</link>
		<dc:creator>Jamie Flournoy</dc:creator>
		<pubDate>Mon, 08 Oct 2007 05:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.pervasivecode.com/blog/2007/08/19/j2me-write-once-be-disappointed-everywhere/#comment-1733</guid>
		<description>&gt;SWT is a wrapper for native widgets.
&gt;It uses native visual interface elements.

True, but SWT adds its own widgets as well.
http://www.eclipse.org/swt/widgets/
(This makes perfect sense from a SWT designer&#039;s POV; if I were developing a portable GUI layer like SWT I&#039;d want to make sure I included a bunch of commonly used widgets to make my toolkit complete and robust for developers.)

Sadly, just because some platform somewhere has a widget that you like doesn&#039;t mean that cloning it and putting it on all platforms as-is is a good idea for usability. Strange widgets that are unique to this one funky application do not make users happy.

Examples: CTabFolder is SWT specific. CoolBar is as well. Most of the SWT widgets are similar in concept and general look and feel to native widgets, or widgets found in popular applications but they are not native.

The Eclipse and Azureus UIs are quite similar in the ways that they suck, and I don&#039;t think that&#039;s a coincidence.

In particular, the oddity of the single paned window with lots of docked tabs is very clumsy. Try using Eclipse on 2 screens (laptop with external monitor), or generally in any multi-window configuration, and you&#039;ll quickly see how poorly it works. Compare this to Photoshop&#039;s support of multiple windows on the same document, drag and drop working well within or between documents, oodles of dockable closeable resizable collapsible tabbed palettes, and it all works.</description>
		<content:encoded><![CDATA[<p>>SWT is a wrapper for native widgets.<br />
>It uses native visual interface elements.</p>
<p>True, but SWT adds its own widgets as well.<br />
<a href="http://www.eclipse.org/swt/widgets/" rel="nofollow">http://www.eclipse.org/swt/widgets/</a><br />
(This makes perfect sense from a SWT designer&#8217;s POV; if I were developing a portable GUI layer like SWT I&#8217;d want to make sure I included a bunch of commonly used widgets to make my toolkit complete and robust for developers.)</p>
<p>Sadly, just because some platform somewhere has a widget that you like doesn&#8217;t mean that cloning it and putting it on all platforms as-is is a good idea for usability. Strange widgets that are unique to this one funky application do not make users happy.</p>
<p>Examples: CTabFolder is SWT specific. CoolBar is as well. Most of the SWT widgets are similar in concept and general look and feel to native widgets, or widgets found in popular applications but they are not native.</p>
<p>The Eclipse and Azureus UIs are quite similar in the ways that they suck, and I don&#8217;t think that&#8217;s a coincidence.</p>
<p>In particular, the oddity of the single paned window with lots of docked tabs is very clumsy. Try using Eclipse on 2 screens (laptop with external monitor), or generally in any multi-window configuration, and you&#8217;ll quickly see how poorly it works. Compare this to Photoshop&#8217;s support of multiple windows on the same document, drag and drop working well within or between documents, oodles of dockable closeable resizable collapsible tabbed palettes, and it all works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adolfojp</title>
		<link>http://www.pervasivecode.com/blog/2007/08/19/j2me-write-once-be-disappointed-everywhere/comment-page-1/#comment-1726</link>
		<dc:creator>adolfojp</dc:creator>
		<pubDate>Sun, 07 Oct 2007 22:58:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.pervasivecode.com/blog/2007/08/19/j2me-write-once-be-disappointed-everywhere/#comment-1726</guid>
		<description>http://en.wikipedia.org/wiki/Standard_Widget_Toolkit

Your second paragraph doesn&#039;t make much sense.

Eclipse and Azureus use SWT. SWT is a wrapper for native widgets. It uses native visual interface elements. If Azureus is an eyesore and Eclipse is difficult to use it has nothing to do with Java. 

However, the fact that they consume an obscene amount of memory and have dreadful startup times has everything to do with Java. ;-)</description>
		<content:encoded><![CDATA[<p><a href="http://en.wikipedia.org/wiki/Standard_Widget_Toolkit" rel="nofollow">http://en.wikipedia.org/wiki/Standard_Widget_Toolkit</a></p>
<p>Your second paragraph doesn&#8217;t make much sense.</p>
<p>Eclipse and Azureus use SWT. SWT is a wrapper for native widgets. It uses native visual interface elements. If Azureus is an eyesore and Eclipse is difficult to use it has nothing to do with Java. </p>
<p>However, the fact that they consume an obscene amount of memory and have dreadful startup times has everything to do with Java. ;-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
