<?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: Looping in FX</title>
	<atom:link href="http://fxexperience.com/2009/11/looping-in-fx/feed/" rel="self" type="application/rss+xml" />
	<link>http://fxexperience.com/2009/11/looping-in-fx/</link>
	<description>Sharing the Experience of JavaFX</description>
	<lastBuildDate>Sat, 04 Feb 2012 00:40:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Michal Margiel</title>
		<link>http://fxexperience.com/2009/11/looping-in-fx/comment-page-1/#comment-1499</link>
		<dc:creator>Michal Margiel</dc:creator>
		<pubDate>Sun, 15 Nov 2009 22:22:30 +0000</pubDate>
		<guid isPermaLink="false">http://fxexperience.com/?p=188#comment-1499</guid>
		<description>yeah, but having in mind performance issue when using binding i don&#039;t think that it is worth it.</description>
		<content:encoded><![CDATA[<p>yeah, but having in mind performance issue when using binding i don&#8217;t think that it is worth it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://fxexperience.com/2009/11/looping-in-fx/comment-page-1/#comment-1498</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sun, 15 Nov 2009 21:50:03 +0000</pubDate>
		<guid isPermaLink="false">http://fxexperience.com/?p=188#comment-1498</guid>
		<description>As an alternative for fun, and probably lots of problems with this idea, but if popups know their parent popup, what about something like:

var visControl bind parentPopup.visible on replace {
    if (! visControl) then visible = false;
    }

I realise somewhat less efficient and would require the parent maintenance which may go against the grain, but then simply setting the parent visibility false would be all that was required :-)</description>
		<content:encoded><![CDATA[<p>As an alternative for fun, and probably lots of problems with this idea, but if popups know their parent popup, what about something like:</p>
<p>var visControl bind parentPopup.visible on replace {<br />
    if (! visControl) then visible = false;<br />
    }</p>
<p>I realise somewhat less efficient and would require the parent maintenance which may go against the grain, but then simply setting the parent visibility false would be all that was required <img src='http://fxexperience.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Java desktop links of the week, November 16 &#124; Jonathan Giles</title>
		<link>http://fxexperience.com/2009/11/looping-in-fx/comment-page-1/#comment-1495</link>
		<dc:creator>Java desktop links of the week, November 16 &#124; Jonathan Giles</dc:creator>
		<pubDate>Sun, 15 Nov 2009 20:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://fxexperience.com/?p=188#comment-1495</guid>
		<description>[...] Bair posted three blogs on FXExperience.com this week. They are related to looping in FX, function delegation, and seeking feedback on node [...]</description>
		<content:encoded><![CDATA[<p>[...] Bair posted three blogs on FXExperience.com this week. They are related to looping in FX, function delegation, and seeking feedback on node [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michal Margiel</title>
		<link>http://fxexperience.com/2009/11/looping-in-fx/comment-page-1/#comment-1490</link>
		<dc:creator>Michal Margiel</dc:creator>
		<pubDate>Sun, 15 Nov 2009 11:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://fxexperience.com/?p=188#comment-1490</guid>
		<description>Thx for this post. I didn&#039;t know that we can use &quot;where&quot; in loops.

We could also do the same using :

    for (p in childrenPopups[child &#124; child.visible]) {
       p.hideAll();
   }

Regards
Michał</description>
		<content:encoded><![CDATA[<p>Thx for this post. I didn&#8217;t know that we can use &#8220;where&#8221; in loops.</p>
<p>We could also do the same using :</p>
<p>    for (p in childrenPopups[child | child.visible]) {<br />
       p.hideAll();<br />
   }</p>
<p>Regards<br />
Michał</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Bair</title>
		<link>http://fxexperience.com/2009/11/looping-in-fx/comment-page-1/#comment-1477</link>
		<dc:creator>Richard Bair</dc:creator>
		<pubDate>Sat, 14 Nov 2009 08:31:58 +0000</pubDate>
		<guid isPermaLink="false">http://fxexperience.com/?p=188#comment-1477</guid>
		<description>And this is in fact what the current code looks like. However to be honest I think all of the last 3 suggestions (pretty well everything but the first) have the same level of simplicity and clarity, just a matter of taste.</description>
		<content:encoded><![CDATA[<p>And this is in fact what the current code looks like. However to be honest I think all of the last 3 suggestions (pretty well everything but the first) have the same level of simplicity and clarity, just a matter of taste.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali Ebrahimi</title>
		<link>http://fxexperience.com/2009/11/looping-in-fx/comment-page-1/#comment-1476</link>
		<dc:creator>Ali Ebrahimi</dc:creator>
		<pubDate>Sat, 14 Nov 2009 08:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://fxexperience.com/?p=188#comment-1476</guid>
		<description>even, simpler version:

public function hideAll():Void {
         for (p in childrenPopups where p.visible) p.hideAll();
         hide();
}</description>
		<content:encoded><![CDATA[<p>even, simpler version:</p>
<p>public function hideAll():Void {<br />
         for (p in childrenPopups where p.visible) p.hideAll();<br />
         hide();<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl Dea</title>
		<link>http://fxexperience.com/2009/11/looping-in-fx/comment-page-1/#comment-1474</link>
		<dc:creator>Carl Dea</dc:creator>
		<pubDate>Fri, 13 Nov 2009 20:34:38 +0000</pubDate>
		<guid isPermaLink="false">http://fxexperience.com/?p=188#comment-1474</guid>
		<description>Rich,

I agree with the others. The third option is cleaner. JavaFX&#039;s &#039;where&#039; keyword makes me think of database SQL statements. 

I&#039;m still getting into the JavaFX Script Language mindset (JavaFX-isms, JavaFX-esque). I still have recent code that looks like option one. 

-Carl</description>
		<content:encoded><![CDATA[<p>Rich,</p>
<p>I agree with the others. The third option is cleaner. JavaFX&#8217;s &#8216;where&#8217; keyword makes me think of database SQL statements. </p>
<p>I&#8217;m still getting into the JavaFX Script Language mindset (JavaFX-isms, JavaFX-esque). I still have recent code that looks like option one. </p>
<p>-Carl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zammbi</title>
		<link>http://fxexperience.com/2009/11/looping-in-fx/comment-page-1/#comment-1471</link>
		<dc:creator>zammbi</dc:creator>
		<pubDate>Fri, 13 Nov 2009 14:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://fxexperience.com/?p=188#comment-1471</guid>
		<description>I agree with Steven. The 3rd option is much nicer.</description>
		<content:encoded><![CDATA[<p>I agree with Steven. The 3rd option is much nicer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Antônio Siqueira</title>
		<link>http://fxexperience.com/2009/11/looping-in-fx/comment-page-1/#comment-1470</link>
		<dc:creator>William Antônio Siqueira</dc:creator>
		<pubDate>Fri, 13 Nov 2009 14:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://fxexperience.com/?p=188#comment-1470</guid>
		<description>@sherod - me too</description>
		<content:encoded><![CDATA[<p>@sherod &#8211; me too</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Herod</title>
		<link>http://fxexperience.com/2009/11/looping-in-fx/comment-page-1/#comment-1466</link>
		<dc:creator>Steven Herod</dc:creator>
		<pubDate>Fri, 13 Nov 2009 10:20:28 +0000</pubDate>
		<guid isPermaLink="false">http://fxexperience.com/?p=188#comment-1466</guid>
		<description>I think the third option is significantly better than the first option. 

And it shows the elegance of jfx script nicely.</description>
		<content:encoded><![CDATA[<p>I think the third option is significantly better than the first option. </p>
<p>And it shows the elegance of jfx script nicely.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

