<?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: TwitterFX &#8211; What next?</title>
	<atom:link href="http://blogs.herod.net/javafx/2009/07/twitterfx-what-next/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.herod.net/javafx/2009/07/twitterfx-what-next/</link>
	<description>Steven Herod's adventures with JavaFX</description>
	<lastBuildDate>Thu, 08 Oct 2009 21:33:16 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andre</title>
		<link>http://blogs.herod.net/javafx/2009/07/twitterfx-what-next/comment-page-1/#comment-971</link>
		<dc:creator>Andre</dc:creator>
		<pubDate>Fri, 17 Jul 2009 07:27:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=28#comment-971</guid>
		<description>Hi,

I have an eye on your project and I hope that the port to JavaFX 1.2 brings some synergy effect to the project. At the moment I&#039;m not familiar with JavaFX, but when TwitterFX is ported I what to train myself with yout project.
Maybe in the future I can support you with some patches. Because there are a lot of features which aren&#039;t implemented by any client but which I&#039;d like to have.

About the payment... I think you can try to implement a donate function on your twitterfxsite, but this would be only a drop in a bucket.
I belive like Roland above me, that the value of reputation of this project is a good investment in the future.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I have an eye on your project and I hope that the port to JavaFX 1.2 brings some synergy effect to the project. At the moment I&#8217;m not familiar with JavaFX, but when TwitterFX is ported I what to train myself with yout project.<br />
Maybe in the future I can support you with some patches. Because there are a lot of features which aren&#8217;t implemented by any client but which I&#8217;d like to have.</p>
<p>About the payment&#8230; I think you can try to implement a donate function on your twitterfxsite, but this would be only a drop in a bucket.<br />
I belive like Roland above me, that the value of reputation of this project is a good investment in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roland</title>
		<link>http://blogs.herod.net/javafx/2009/07/twitterfx-what-next/comment-page-1/#comment-912</link>
		<dc:creator>Roland</dc:creator>
		<pubDate>Sat, 11 Jul 2009 07:52:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=28#comment-912</guid>
		<description>Hi!
Thought one can&#039;t be wrong from any standpoint. It would also make the application easier to support. 

Thought two, I can&#039;t see the value of that. Either TwitterFx is good and is used or else it isn&#039;t good and isn&#039;t used. If it&#039;s going to be reference it is by example, not by being written to be reference. 

Thought three can&#039;t be wrong either. Twitterfx is hopefully going to live for a long time so maintainablity is important. It is also a factory for thought two.

Thought four should be handled through thought one and  three. Separation of well written code into libraries should make different versions of twitterfx a breeze. Just use the functions and the gui you need right now. 

Thought five is hard. Ofcourse you should have money and spare time with your family. But until TwitterFx is one of the top 2 twitterapps I think it&#039;s hard to get paid. Try the market, current version for a couple of $ and previous version for free. But be carefull. TwitterFx lead developer might be more valuble for you in your resume than in cash.</description>
		<content:encoded><![CDATA[<p>Hi!<br />
Thought one can&#8217;t be wrong from any standpoint. It would also make the application easier to support. </p>
<p>Thought two, I can&#8217;t see the value of that. Either TwitterFx is good and is used or else it isn&#8217;t good and isn&#8217;t used. If it&#8217;s going to be reference it is by example, not by being written to be reference. </p>
<p>Thought three can&#8217;t be wrong either. Twitterfx is hopefully going to live for a long time so maintainablity is important. It is also a factory for thought two.</p>
<p>Thought four should be handled through thought one and  three. Separation of well written code into libraries should make different versions of twitterfx a breeze. Just use the functions and the gui you need right now. </p>
<p>Thought five is hard. Ofcourse you should have money and spare time with your family. But until TwitterFx is one of the top 2 twitterapps I think it&#8217;s hard to get paid. Try the market, current version for a couple of $ and previous version for free. But be carefull. TwitterFx lead developer might be more valuble for you in your resume than in cash.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
