<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>The Rich Internet Experience</title>
<link>http://ajax.sys-con.com/</link>
<description>Latest articles from The Rich Internet Experience</description>
<copyright>Copyright 2008 AJAXWORLD MAGAZINE</copyright>
<lastBuildDate>Tue, 13 May 2008 03:05:00 GMT</lastBuildDate>
<generator>AJAXWORLD MAGAZINE</generator>
<ttl>10</ttl>
<docs>http://backend.userland.com/rss</docs>

<item>
<title>Engelbart&apos;s Usability Dilemma: Efficiency vs Ease-of-Use</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/536976.htm</guid><link>http://ajax.sys-con.com/read/536976.htm</link>
<pubDate>Thu, 10 Apr 2008 09:15:00 GMT</pubDate>
<description>The mouse was the original idea of Doug Engelbart who was the head of the Augmentation Research Center (ARC) at Stanford Research Institute. Engelbart&apos;s philosophy is best embodied, in my opinion, in the design of another device that he invented, the five-finger keyboard - with keys like a piano, used by one hand. The problem was, Engelbart&apos;s five-finger keyboard and mouse combination was very difficult to learn.</description>

</item><item>
<title>The &quot;Uncanny Valley&quot; Theory Doesn&apos;t Apply to Desktop UI</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/531419.htm</guid><link>http://ajax.sys-con.com/read/531419.htm</link>
<pubDate>Wed, 02 Apr 2008 14:45:00 GMT</pubDate>
<description>If you design an application that runs on Windows but doesn&apos;t look exactly like Windows, so the old argument goes, the effect will be unsettling for users. But sticking to the native look and feel (L&amp;F) should not be the end-goal of designers.</description>

</item><item>
<title>Enterprise Widgets: The Story So Far</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/524527.htm</guid><link>http://ajax.sys-con.com/read/524527.htm</link>
<pubDate>Sun, 30 Mar 2008 02:45:00 GMT</pubDate>
<description>Desktop widgets have been around for a very long time. The first set of desktop widgets were introduced by Apple back in 1983 with their release of Apple Desktop Accessories. Obviously Apple was way ahead of the curve, but these early widgets were not Internet enabled - the popular Internet, as we know it, didn&apos;t exist - so their utility was pretty limited.</description>

</item><item>
<title>The Grand Convergence: Web + RIA + Widgets + Client/Server</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/516151.htm</guid><link>http://ajax.sys-con.com/read/516151.htm</link>
<pubDate>Thu, 13 Mar 2008 06:30:00 GMT</pubDate>
<description>For the past ten years application developers have been stuck with only two desktop client choices. Traditionally, they can choose either a very thin Web-client technology implemented in HTML and CSS, or a very heavyweight thick client experience implemented using traditional client/server (C/S) technologies (e.g. Java Swing, MFC). It wasn&apos;t until the introduction of RIA technologies (e.g. AJAX, Adobe Flex, Curl, and Silverlight) and widget engines (e.g. Yahoo! Widgets and Google Gadgets) that we were given more options.</description>

</item><item>
<title>The Rise of the Fit Client</title>
<guid isPermaLink="true">http://ajax.sys-con.com/read/510792.htm</guid><link>http://ajax.sys-con.com/read/510792.htm</link>
<pubDate>Tue, 04 Mar 2008 06:15:00 GMT</pubDate>
<description>If Gartner&apos;s assessment of AJAX&apos;s position on the Hype Cycle is correct, then the days when AJAX is the only game in town are over. Enter the age of what Anne Thomas Manes of the Burton Group calls &apos;Fit Clients&apos; - a hybrid of Thick Clients (a.k.a. Fat Clients) and Thin Clients (HTML and RIA). Adobe AIR is definitely a Fit Client technology, but it&apos;s not the first and won&apos;t be the only player in this space.</description>

</item></channel></rss>