<?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: Your questions answered #1</title>
	<atom:link href="http://html5doctor.com/your-questions-answered-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://html5doctor.com/your-questions-answered-1/</link>
	<description>helping you implement HTML5 today</description>
	<lastBuildDate>Tue, 22 May 2012 11:38:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Remy Sharp</title>
		<link>http://html5doctor.com/your-questions-answered-1/#comment-433</link>
		<dc:creator>Remy Sharp</dc:creator>
		<pubDate>Fri, 31 Jul 2009 10:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=390#comment-433</guid>
		<description>@Girish - no doubt you got the reply via email, but we felt it would be useful to share this on HTML 5 Doctor too:

Technically it &lt;em&gt;should&lt;/em&gt; be possible.  Certainly the HTML 5 offline applications API (via the manifest) gives you all that ability to create a client side app and it run locally without a web connection.

However, the browser is the problem.  Prism might be a good way to deploy this as a standalone app, but I don&#039;t know if Prism is running the latest Gecko engine (or whether that comes with the JS engine, etc) - and even if it does - Firefox 3.5 currently has a pretty severe bug with the offline applications: it doesn&#039;t work!

I have logged the bug with Mozilla and I know they&#039;re working (in fact, I believe they&#039;ve fixed it and are now testing).

The alternative is to use Fluid (a Webkit based app) - but again, that&#039;s only if they have updated to the latest Webkit and thus including the offline applications API (that said, quickly looking at the Fluid site, their in-progress version may have the latest Webkit).

Regarding launch from start up scripts - you could achieve this though the custom scheme handlers (but this is just Firefox IIRC): http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#custom-handlers

Equally, there may be an API that you could exploit via the standalone browser, either Prism or Fluid.

I realise this reply might be a little vague, but the technology is coming together!</description>
		<content:encoded><![CDATA[<p>@Girish &#8211; no doubt you got the reply via email, but we felt it would be useful to share this on HTML 5 Doctor too:</p>
<p>Technically it <em>should</em> be possible.  Certainly the HTML 5 offline applications API (via the manifest) gives you all that ability to create a client side app and it run locally without a web connection.</p>
<p>However, the browser is the problem.  Prism might be a good way to deploy this as a standalone app, but I don&#8217;t know if Prism is running the latest Gecko engine (or whether that comes with the JS engine, etc) &#8211; and even if it does &#8211; Firefox 3.5 currently has a pretty severe bug with the offline applications: it doesn&#8217;t work!</p>
<p>I have logged the bug with Mozilla and I know they&#8217;re working (in fact, I believe they&#8217;ve fixed it and are now testing).</p>
<p>The alternative is to use Fluid (a Webkit based app) &#8211; but again, that&#8217;s only if they have updated to the latest Webkit and thus including the offline applications API (that said, quickly looking at the Fluid site, their in-progress version may have the latest Webkit).</p>
<p>Regarding launch from start up scripts &#8211; you could achieve this though the custom scheme handlers (but this is just Firefox IIRC): <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#custom-handlers" rel="nofollow">http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#custom-handlers</a></p>
<p>Equally, there may be an API that you could exploit via the standalone browser, either Prism or Fluid.</p>
<p>I realise this reply might be a little vague, but the technology is coming together!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Girish</title>
		<link>http://html5doctor.com/your-questions-answered-1/#comment-393</link>
		<dc:creator>Girish</dc:creator>
		<pubDate>Wed, 29 Jul 2009 14:56:17 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=390#comment-393</guid>
		<description>Is it possible to create a complete client side application using HTML 5 (it will embed chat clients, stock ticker) + JavaScript, and then bundle is with underlining Firefox 3.5 engine, so that user can install it as a desktop app on Linux, and then it runs in its own window using firefox 3.5 engine. The app will store everything in local storage - like url, usernames etc, and will not interact with any local server.

It would pure HTML5 + JavaScript based client web app which would be packaged, and can be installed or launched from startup scripts.

Or instead of using firefox 3.5 engine, we can use Mozilla Prism to convert it to web app, and then bundle it, is it possible?</description>
		<content:encoded><![CDATA[<p>Is it possible to create a complete client side application using HTML 5 (it will embed chat clients, stock ticker) + JavaScript, and then bundle is with underlining Firefox 3.5 engine, so that user can install it as a desktop app on Linux, and then it runs in its own window using firefox 3.5 engine. The app will store everything in local storage &#8211; like url, usernames etc, and will not interact with any local server.</p>
<p>It would pure HTML5 + JavaScript based client web app which would be packaged, and can be installed or launched from startup scripts.</p>
<p>Or instead of using firefox 3.5 engine, we can use Mozilla Prism to convert it to web app, and then bundle it, is it possible?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Clark</title>
		<link>http://html5doctor.com/your-questions-answered-1/#comment-207</link>
		<dc:creator>Rich Clark</dc:creator>
		<pubDate>Thu, 16 Jul 2009 15:36:54 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=390#comment-207</guid>
		<description>Oli, you&#039;re absolutely spot on when you say that HTML 5 is a sliding scale. We have a few articles coming up that will cover the complete basics of swapping to HTML 5. 

Your cheatsheet has definately helped the adoption of HTML 5 semantic naming too.</description>
		<content:encoded><![CDATA[<p>Oli, you&#8217;re absolutely spot on when you say that HTML 5 is a sliding scale. We have a few articles coming up that will cover the complete basics of swapping to HTML 5. </p>
<p>Your cheatsheet has definately helped the adoption of HTML 5 semantic naming too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oli</title>
		<link>http://html5doctor.com/your-questions-answered-1/#comment-175</link>
		<dc:creator>oli</dc:creator>
		<pubDate>Tue, 14 Jul 2009 13:46:44 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=390#comment-175</guid>
		<description>Regarding converting HTML4/XHTML1 to HTML5, I think a lot of the benefit in moving to HTML5 is a richer set of semantics. This means if you’re converting standard HTML4/XHTML1 you’ll get the most value out of rethinking everything, which as Richard states makes automatic conversion impossible. However using HTML5 is a sliding scale (not all or nothing), and we don’t have to go ‘all the way’ to get benefits :) Because HTML5 is so backwards compatible often just a change of Doctype will get you most of the way to a valid HTML5 document with your current code. While you won’t get the semantic benefits of rethinking everything, you can then eg use the improved HTML5 validators with only a small time investment.

If you decide to use the HTML5 doctype but not use the new structural elements for the time being (eg due to worries about IE without JS turned on),  or have to use HTML4/XHTML1 for the moment, I’d recommend the &lt;div class=&quot;html5-element-name&quot;&gt; approach. If you’re consistent you’d be able to do some of the conversion (class names to opening elements) via regex. Richard has linked to a cheatsheet I wrote above (thanks!), but if you’d like more info (ie this comment as an article ;-) I just wrote &lt;a href=&quot;http://boblet.tumblr.com/post/141239118/html5-structure4&quot; rel=&quot;nofollow&quot;&gt;HTML5 structure—HTML4 and XHTML1 to HTML5&lt;/a&gt;, which might help…

\me wonders what formatting is supported in comments… here’s hoping</description>
		<content:encoded><![CDATA[<p>Regarding converting HTML4/XHTML1 to HTML5, I think a lot of the benefit in moving to HTML5 is a richer set of semantics. This means if you’re converting standard HTML4/XHTML1 you’ll get the most value out of rethinking everything, which as Richard states makes automatic conversion impossible. However using HTML5 is a sliding scale (not all or nothing), and we don’t have to go ‘all the way’ to get benefits :) Because HTML5 is so backwards compatible often just a change of Doctype will get you most of the way to a valid HTML5 document with your current code. While you won’t get the semantic benefits of rethinking everything, you can then eg use the improved HTML5 validators with only a small time investment.</p>
<p>If you decide to use the HTML5 doctype but not use the new structural elements for the time being (eg due to worries about IE without JS turned on),  or have to use HTML4/XHTML1 for the moment, I’d recommend the &lt;div class=&#8221;html5-element-name&#8221;&gt; approach. If you’re consistent you’d be able to do some of the conversion (class names to opening elements) via regex. Richard has linked to a cheatsheet I wrote above (thanks!), but if you’d like more info (ie this comment as an article ;-) I just wrote <a href="http://boblet.tumblr.com/post/141239118/html5-structure4" rel="nofollow">HTML5 structure—HTML4 and XHTML1 to HTML5</a>, which might help…</p>
<p>\me wonders what formatting is supported in comments… here’s hoping</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Clark</title>
		<link>http://html5doctor.com/your-questions-answered-1/#comment-105</link>
		<dc:creator>Rich Clark</dc:creator>
		<pubDate>Tue, 07 Jul 2009 08:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=390#comment-105</guid>
		<description>Thanks Henry, glad you enjoyed the article we hope to have plenty more of them as your questions come in.</description>
		<content:encoded><![CDATA[<p>Thanks Henry, glad you enjoyed the article we hope to have plenty more of them as your questions come in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren</title>
		<link>http://html5doctor.com/your-questions-answered-1/#comment-104</link>
		<dc:creator>Darren</dc:creator>
		<pubDate>Tue, 07 Jul 2009 08:18:50 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=390#comment-104</guid>
		<description>@Henry. EVERYONE would be a better developer if IE just went away completely!! ;)</description>
		<content:encoded><![CDATA[<p>@Henry. EVERYONE would be a better developer if IE just went away completely!! ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren</title>
		<link>http://html5doctor.com/your-questions-answered-1/#comment-103</link>
		<dc:creator>Darren</dc:creator>
		<pubDate>Tue, 07 Jul 2009 08:13:20 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=390#comment-103</guid>
		<description>Excellent tips, thanks Rich!</description>
		<content:encoded><![CDATA[<p>Excellent tips, thanks Rich!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henry</title>
		<link>http://html5doctor.com/your-questions-answered-1/#comment-100</link>
		<dc:creator>Henry</dc:creator>
		<pubDate>Mon, 06 Jul 2009 18:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=390#comment-100</guid>
		<description>Great article Rich! I have been wanting to mess around with HTML 5 but what&#039;s holding me back is the same reason I don&#039;t use CSS3. I wish that IE 6 would disappear although I also feel that IE has made everyone that developes for it make  them a better programmer in the sense that they have to clearly understand how exactly elements  work with CSS and how to &#039;hack it&#039; to make it work. Keep up the great articles looking forward for more!</description>
		<content:encoded><![CDATA[<p>Great article Rich! I have been wanting to mess around with HTML 5 but what&#8217;s holding me back is the same reason I don&#8217;t use CSS3. I wish that IE 6 would disappear although I also feel that IE has made everyone that developes for it make  them a better programmer in the sense that they have to clearly understand how exactly elements  work with CSS and how to &#8216;hack it&#8217; to make it work. Keep up the great articles looking forward for more!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

