<?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: Adobe onAir show in London</title>
	<atom:link href="http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/</link>
	<description>Chris Heilmann - Accessibilty, Web Development and Pragmatism - can talk, will travel</description>
	<pubDate>Sun, 06 Jul 2008 20:01:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Rogier Schoenmaker</title>
		<link>http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/#comment-7726</link>
		<dc:creator>Rogier Schoenmaker</dc:creator>
		<pubDate>Sat, 24 May 2008 22:01:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/#comment-7726</guid>
		<description>I really like the idea behind AIR, but it just doesn't work easy enough yet for developers. I'm a pretty advanced ECMAscripter :), but I keep getting errors that are not really helpfull and there's just too few documentation. And what documentation there is, is often not working anymore in current versions.

They still have a lot of work to do.

PS. I was there in Amsterdam and the conference was great, except for two speakers (one guy nobody could understand, and one a bit too much marketing his own framework).</description>
		<content:encoded><![CDATA[<p>I really like the idea behind <span class="caps">AIR, </span>but it just doesn&#8217;t work easy enough yet for developers. I&#8217;m a pretty advanced <span class="caps">ECMA</span>scripter :), but I keep getting errors that are not really helpfull and there&#8217;s just too few documentation. And what documentation there is, is often not working anymore in current versions.</p>
<p>They still have a lot of work to do.</p>
<p><span class="caps">PS.</span> I was there in Amsterdam and the conference was great, except for two speakers (one guy nobody could understand, and one a bit too much marketing his own framework).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjan</title>
		<link>http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/#comment-7464</link>
		<dc:creator>Arjan</dc:creator>
		<pubDate>Thu, 10 Apr 2008 18:39:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/#comment-7464</guid>
		<description>I've visited the On Air tour in Amsterdam last week. The whole event was in my opinion very professional, free goodies and stuff is very cool.

However, I'm not a great fan of AIR itself. I have tried to develop three very different applications with it, but it lacks many features I really need.

For example, it is not possible to communicate with another computer/mac without using a server. So, peer-to-peer communication is impossible. Also, it is not possible to use OS native interface widgets. The radio buttons, datagrids, buttons etc, it really looks stupid. For example, by default the text input has a blue border when you focus it (why??).

The AIR team has to do quite a lot work on this and also other things. It is a nice start, though. I hope to see it being a professional framework for desktop-web applications.

By the way, what did you win?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve visited the On Air tour in Amsterdam last week. The whole event was in my opinion very professional, free goodies and stuff is very cool.</p>
<p>However, I&#8217;m not a great fan of <span class="caps">AIR </span>itself. I have tried to develop three very different applications with it, but it lacks many features I really need.</p>
<p>For example, it is not possible to communicate with another computer/mac without using a server. So, peer-to-peer communication is impossible. Also, it is not possible to use OS native interface widgets. The radio buttons, datagrids, buttons etc, it really looks stupid. For example, by default the text input has a blue border when you focus it (why??).</p>
<p>The <span class="caps">AIR </span>team has to do quite a lot work on this and also other things. It is a nice start, though. I hope to see it being a professional framework for desktop-web applications.</p>
<p>By the way, what did you win?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Snook</title>
		<link>http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/#comment-7460</link>
		<dc:creator>Jonathan Snook</dc:creator>
		<pubDate>Thu, 10 Apr 2008 14:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/#comment-7460</guid>
		<description>Just to clarify the point about the memory usage, it's not specifically the &lt;a href="http://code.google.com/p/as3notificationlib/" rel="nofollow"&gt;growl-like application&lt;/a&gt; but Snitter and other AIR apps that use it will notice memory leaks in using it. 

When I have the feature turned off, Snitter (on Windows, anyways) sits around 40MB even if I've had it open for days. 40MB is still a lot for what is essentially an overdone "widget" but it's a browser (er, rendering engine) and a flash runtime all tied into one and that's going to take up some memory regardless.

Managing memory leaks will be an important issue when it comes to building AIR apps, more so than web apps, simply because they stay around longer and have more of an opportunity to leak memory.</description>
		<content:encoded><![CDATA[<p>Just to clarify the point about the memory usage, it&#8217;s not specifically the <a href="http://code.google.com/p/as3notificationlib/" rel="nofollow">growl-like application</a> but Snitter and other <span class="caps">AIR </span>apps that use it will notice memory leaks in using it. </p>
<p>When I have the feature turned off, Snitter (on Windows, anyways) sits around 40MB even if I&#8217;ve had it open for days. 40MB is still a lot for what is essentially an overdone &#8220;widget&#8221; but it&#8217;s a browser (er, rendering engine) and a flash runtime all tied into one and that&#8217;s going to take up some memory regardless.</p>
<p>Managing memory leaks will be an important issue when it comes to building <span class="caps">AIR </span>apps, more so than web apps, simply because they stay around longer and have more of an opportunity to leak memory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andre Charland</title>
		<link>http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/#comment-7459</link>
		<dc:creator>Andre Charland</dc:creator>
		<pubDate>Thu, 10 Apr 2008 14:21:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/#comment-7459</guid>
		<description>Thanks Chris! Glad you liked the event:)</description>
		<content:encoded><![CDATA[<p>Thanks Chris! Glad you liked the event:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marc thiele</title>
		<link>http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/#comment-7454</link>
		<dc:creator>marc thiele</dc:creator>
		<pubDate>Thu, 10 Apr 2008 11:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.wait-till-i.com/2008/04/10/adobe-onair-show-in-london/#comment-7454</guid>
		<description>Hi Chris,

thanks for this really nice report. That makes me looking forward to the German spots of the tour.

marc</description>
		<content:encoded><![CDATA[<p>Hi Chris,</p>
<p>thanks for this really nice report. That makes me looking forward to the German spots of the tour.</p>
<p>marc</p>
]]></content:encoded>
	</item>
</channel>
</rss>
