<?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: XForms for Firefox 3.5</title>
	<atom:link href="http://philipp.wagner.name/blog/2009/03/xforms-for-firefox-35/feed/" rel="self" type="application/rss+xml" />
	<link>http://philipp.wagner.name/blog/2009/03/xforms-for-firefox-35/</link>
	<description>whatever comes to a developer's mind</description>
	<lastBuildDate>Fri, 06 Jan 2012 10:10:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Philipp</title>
		<link>http://philipp.wagner.name/blog/2009/03/xforms-for-firefox-35/comment-page-1/#comment-89</link>
		<dc:creator>Philipp</dc:creator>
		<pubDate>Thu, 22 Oct 2009 12:58:53 +0000</pubDate>
		<guid isPermaLink="false">http://philipp.wagner.name/blog/?p=33#comment-89</guid>
		<description>As it turns out, XForms are too heavy for the average web developer, which means they probably will never be a core part of Firefox. This decision may change in the future of course. But I don&#039;t have much of a problem with the add-on approach, either.
I also see that the benefit of a client-side solution is decreasing every day. With the advantage of AJAX technologies, XForms can be emulated pretty well in plain HTML and JavaScript, as it&#039;s done in Orbeon Forms or Ubiquity. There are still some benefits of a client-side solution, but I don&#039;t know how long these advantages will last. (they are mainly problems of the browser security model which does not allow some operations, e.g. a picture upload field and a xf:output displaying the picture right away from hard disk).
Regarding development, currently no company is supporting the development of Mozilla XForms any more and thus progress is really slow atm. Previously, Novell and IBM had some developers working on Mozilla XForms full time. Let&#039;s see how this changes in the future.</description>
		<content:encoded><![CDATA[<p>As it turns out, XForms are too heavy for the average web developer, which means they probably will never be a core part of Firefox. This decision may change in the future of course. But I don&#8217;t have much of a problem with the add-on approach, either.<br />
I also see that the benefit of a client-side solution is decreasing every day. With the advantage of AJAX technologies, XForms can be emulated pretty well in plain HTML and JavaScript, as it&#8217;s done in Orbeon Forms or Ubiquity. There are still some benefits of a client-side solution, but I don&#8217;t know how long these advantages will last. (they are mainly problems of the browser security model which does not allow some operations, e.g. a picture upload field and a xf:output displaying the picture right away from hard disk).<br />
Regarding development, currently no company is supporting the development of Mozilla XForms any more and thus progress is really slow atm. Previously, Novell and IBM had some developers working on Mozilla XForms full time. Let&#8217;s see how this changes in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ludwig Jaffe</title>
		<link>http://philipp.wagner.name/blog/2009/03/xforms-for-firefox-35/comment-page-1/#comment-88</link>
		<dc:creator>Ludwig Jaffe</dc:creator>
		<pubDate>Thu, 22 Oct 2009 08:31:06 +0000</pubDate>
		<guid isPermaLink="false">http://philipp.wagner.name/blog/?p=33#comment-88</guid>
		<description>Are you getting much help with developing XForms for Firefox 3.5? 

I&#039;m using the add-on XForms 0.8.6.ff3. I am interested in learning about what needs  to be done and lobbying Firefox to integrate this capability in a future release.</description>
		<content:encoded><![CDATA[<p>Are you getting much help with developing XForms for Firefox 3.5? </p>
<p>I&#8217;m using the add-on XForms 0.8.6.ff3. I am interested in learning about what needs  to be done and lobbying Firefox to integrate this capability in a future release.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

