<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>OpenWack Community Software Blog &#187; forms</title>
	<atom:link href="http://www.openwack.org/blog/tag/forms/feed" rel="self" type="application/rss+xml" />
	<link>http://www.openwack.org/blog</link>
	<description>The best free community software highlighted</description>
	<lastBuildDate>Sat, 24 Jul 2010 18:28:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Forms engine in the works</title>
		<link>http://www.openwack.org/blog/2009/04/forms-engine-in-the-works.html</link>
		<comments>http://www.openwack.org/blog/2009/04/forms-engine-in-the-works.html#comments</comments>
		<pubDate>Mon, 06 Apr 2009 10:48:25 +0000</pubDate>
		<dc:creator>Emil</dc:creator>
				<category><![CDATA[Core Development]]></category>
		<category><![CDATA[forms]]></category>

		<guid isPermaLink="false">http://www.openwack.org/blog/?p=70</guid>
		<description><![CDATA[We currently work on the engine of HTTP forms for OpenWack core that will be used everywhere: on the user pages, admin area, and plugins. Needless to say, it&#8217;s an important task to make forms as easy to operate as possible meanwhile retaining flexibility.
For example, 80% of admin area will consist of forms in their [...]]]></description>
			<content:encoded><![CDATA[<p>We currently work on the engine of HTTP forms for OpenWack core that will be used everywhere: on the user pages, admin area, and plugins. Needless to say, it&#8217;s an important task to make forms as easy to operate as possible meanwhile retaining flexibility.</p>
<p>For example, 80% of admin area will consist of forms in their basic incarnation, such as listing sectioned fields of settings with &#8220;Submit&#8221; button. On the other hand plugins may require all kinds of forms, response types, before-submit validations and all.</p>
<p>A basic form is going to have default <a href="http://www.openwack.org/blog/2009/03/openwack-theming-and-display-mechanisms.html">decorator</a>. This can be overridden right in the markup if your form requires that. Also you will be given program tools to control submit methods, Ajax, validation, and so on.</p>
<p>Forms, as a critical part of the OpenWack core is most likely to have several iterations through the product versions to mature but at this point we have a very good understanding of their requirements. We have seen them all with other <a href="http://www.skalfa.com/products/">Skalfa products</a>. OpenWack will contain all technical experience of the company and introduce our understanding of the current and future community software market.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.openwack.org/blog/2009/04/forms-engine-in-the-works.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
