<?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>DavidJB.com &#187; form</title>
	<atom:link href="http://davidjb.com/blog/tag/form/feed" rel="self" type="application/rss+xml" />
	<link>http://davidjb.com</link>
	<description>The ramblings of an IT professional about life, the Universe, and Plone</description>
	<lastBuildDate>Thu, 22 Jul 2010 07:21:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Plone, Dexterity, and Incorrect Widgets</title>
		<link>http://davidjb.com/blog/2010/06/plone-dexterity-and-incorrect-widgets</link>
		<comments>http://davidjb.com/blog/2010/06/plone-dexterity-and-incorrect-widgets#comments</comments>
		<pubDate>Mon, 21 Jun 2010 05:09:31 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[content type]]></category>
		<category><![CDATA[datetime]]></category>
		<category><![CDATA[dexterity]]></category>
		<category><![CDATA[fields]]></category>
		<category><![CDATA[form]]></category>
		<category><![CDATA[plone]]></category>
		<category><![CDATA[problem]]></category>
		<category><![CDATA[product]]></category>
		<category><![CDATA[zope]]></category>

		<guid isPermaLink="false">http://davidjb.com/?p=463</guid>
		<description><![CDATA[A nice &#8216;gotcha&#8217; is the distinction between Zope&#8217;s schema.Date and schema.Datetime. The difference is obvious and straightforward when the two terms are laid out side-by-side: one is for dates only and the other adds a time component. Where things fell down for me in my usage of these fields with a Dexterity-based content type in [...]]]></description>
		<wfw:commentRss>http://davidjb.com/blog/2010/06/plone-dexterity-and-incorrect-widgets/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PloneFormGen (Plone) &amp; Google Calendar Integration</title>
		<link>http://davidjb.com/blog/2009/09/ploneformgen-plone-google-calendar-integration</link>
		<comments>http://davidjb.com/blog/2009/09/ploneformgen-plone-google-calendar-integration#comments</comments>
		<pubDate>Tue, 22 Sep 2009 00:40:34 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[calendar]]></category>
		<category><![CDATA[form]]></category>
		<category><![CDATA[gen]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[mash]]></category>
		<category><![CDATA[pfg]]></category>
		<category><![CDATA[plone]]></category>
		<category><![CDATA[product]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[script]]></category>

		<guid isPermaLink="false">http://davidjb.com/?p=233</guid>
		<description><![CDATA[It&#8217;s a little bit of a different mash-up, but it&#8217;s still nonetheless useful to have, given types of booking forms and so forth that could utilise it.  The easiest way I found (to avoid security issues with Python scripts in Plone) was to create an external method and just import it within a PFG Custom [...]]]></description>
		<wfw:commentRss>http://davidjb.com/blog/2009/09/ploneformgen-plone-google-calendar-integration/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Plone: URL Encoding In A Script</title>
		<link>http://davidjb.com/blog/2009/01/plone-url-encoding-in-a-script</link>
		<comments>http://davidjb.com/blog/2009/01/plone-url-encoding-in-a-script#comments</comments>
		<pubDate>Thu, 29 Jan 2009 22:46:06 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[adapter]]></category>
		<category><![CDATA[form]]></category>
		<category><![CDATA[plone]]></category>
		<category><![CDATA[ploneformgen]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[quote]]></category>
		<category><![CDATA[url]]></category>

		<guid isPermaLink="false">http://davidjb.com/?p=155</guid>
		<description><![CDATA[So, for today&#8217;s problem, how can we get a URL (specifically the GET request arguments) suitably encoded? Easy, if we&#8217;re talking about a Python script that lives on the file system and can be used within Zope/Plone that way. But what about some sort of Python script that has to exist on the Plone site [...]]]></description>
		<wfw:commentRss>http://davidjb.com/blog/2009/01/plone-url-encoding-in-a-script/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
