<?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: Integrating JavaFX with regular Java &#8211; Part 2</title>
	<atom:link href="http://www.jhkuperus.nl/articles/java/javafx/integrating-javafx-with-regular-java-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jhkuperus.nl/articles/java/javafx/integrating-javafx-with-regular-java-part-2/</link>
	<description>Random Ramblings of an Engineer</description>
	<lastBuildDate>Tue, 27 Sep 2011 04:23:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: JCN Blog &#187; Blog Archive &#187; Integrating JavaFX with regular Java &#8211; Part 2</title>
		<link>http://www.jhkuperus.nl/articles/java/javafx/integrating-javafx-with-regular-java-part-2/#comment-224</link>
		<dc:creator>JCN Blog &#187; Blog Archive &#187; Integrating JavaFX with regular Java &#8211; Part 2</dc:creator>
		<pubDate>Mon, 16 Aug 2010 14:04:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.jhkuperus.nl/?p=82#comment-224</guid>
		<description>[...] Originally posted on www.jhkuperus.nl [...]</description>
		<content:encoded><![CDATA[<p>[...] Originally posted on <a href="http://www.jhkuperus.nl" rel="nofollow">http://www.jhkuperus.nl</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan-Hendrik Kuperus</title>
		<link>http://www.jhkuperus.nl/articles/java/javafx/integrating-javafx-with-regular-java-part-2/#comment-12</link>
		<dc:creator>Jan-Hendrik Kuperus</dc:creator>
		<pubDate>Fri, 25 Jun 2010 22:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.jhkuperus.nl/?p=82#comment-12</guid>
		<description>Thanks! I certainly agree with you that JavaFX needs to respect where it came from. There will probably be many applications out there already built in Java that merely need a better User Experience.

I certainly hope the next release will make this piece of code of mine superfluous. :)

--JH</description>
		<content:encoded><![CDATA[<p>Thanks! I certainly agree with you that JavaFX needs to respect where it came from. There will probably be many applications out there already built in Java that merely need a better User Experience.</p>
<p>I certainly hope the next release will make this piece of code of mine superfluous. <img src='http://www.jhkuperus.nl/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>&#8211;JH</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Torch</title>
		<link>http://www.jhkuperus.nl/articles/java/javafx/integrating-javafx-with-regular-java-part-2/#comment-11</link>
		<dc:creator>Torch</dc:creator>
		<pubDate>Fri, 25 Jun 2010 03:46:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.jhkuperus.nl/?p=82#comment-11</guid>
		<description>Thanks for such an insightful article, it deserves many accolades! Any information about bridging the divide between Java and JavaFX is very rare while being extremely important. It seems that the JavaFX camp has rocked to its own drummer and hopes to teach everyone more limited drum rolls. Its nice to see this put into perspective where Java can do the things it already does best and JavaFX fulfills a niche with its UI toolkit.

I hope more information like this surfaces as it is grounded in the reality of real world application development. JavaFX will continue to come up short as long as it ignores two way Java interoperability with JavaFX and also the inclusion of immediate rendering via Java2D into its memory and performance expensive retained rendering system.</description>
		<content:encoded><![CDATA[<p>Thanks for such an insightful article, it deserves many accolades! Any information about bridging the divide between Java and JavaFX is very rare while being extremely important. It seems that the JavaFX camp has rocked to its own drummer and hopes to teach everyone more limited drum rolls. Its nice to see this put into perspective where Java can do the things it already does best and JavaFX fulfills a niche with its UI toolkit.</p>
<p>I hope more information like this surfaces as it is grounded in the reality of real world application development. JavaFX will continue to come up short as long as it ignores two way Java interoperability with JavaFX and also the inclusion of immediate rendering via Java2D into its memory and performance expensive retained rendering system.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

