<?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: Adobe LiveCycle ES Technical U: integrated Flex and LiveCycle training</title>
	<atom:link href="http://jochem.vandieten.net/2008/02/11/adobe-livecycle-es-technical-u-integrated-flex-and-livecycle-training/feed/" rel="self" type="application/rss+xml" />
	<link>http://jochem.vandieten.net/2008/02/11/adobe-livecycle-es-technical-u-integrated-flex-and-livecycle-training/</link>
	<description>Jochem's tech exploits</description>
	<pubDate>Wed, 10 Jun 2026 08:11:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: &#8220;it could be bunnies&#8221; &#187; Blog Archive &#187; Localizing LiveCycle ES Workspace with FlexBuilder 3</title>
		<link>http://jochem.vandieten.net/2008/02/11/adobe-livecycle-es-technical-u-integrated-flex-and-livecycle-training/comment-page-1/#comment-8</link>
		<dc:creator>&#8220;it could be bunnies&#8221; &#187; Blog Archive &#187; Localizing LiveCycle ES Workspace with FlexBuilder 3</dc:creator>
		<pubDate>Fri, 29 Feb 2008 17:33:14 +0000</pubDate>
		<guid isPermaLink="false">http://jochem.vandieten.net/2008/02/11/adobe-livecycle-es-technical-u-integrated-flex-and-livecycle-training/#comment-8</guid>
		<description>[...] FlexBuilder 2 (if that works we don&#8217;t need to include FlexBuilder 2 in the software for the Adobe TechU). I didn&#8217;t expect too many problems because according to Customizing the LiveCycle® [...]</description>
		<content:encoded><![CDATA[<p>[...] FlexBuilder 2 (if that works we don&#8217;t need to include FlexBuilder 2 in the software for the Adobe TechU). I didn&#8217;t expect too many problems because according to Customizing the LiveCycle® [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
