<?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: JavaFX effects and hardware acceleration&#8230;</title>
	<atom:link href="http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/</link>
	<description>Steven Herod's adventures with JavaFX</description>
	<lastBuildDate>Sun, 06 Mar 2011 22:30:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: JavaFX Hardware Acceleration &#124; _mindMeld</title>
		<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/comment-page-1/#comment-1036</link>
		<dc:creator>JavaFX Hardware Acceleration &#124; _mindMeld</dc:creator>
		<pubDate>Fri, 31 Jul 2009 12:51:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=30#comment-1036</guid>
		<description>[...] This is a nice little article which helps you understand whether your javafx implementation is hardware accelerated.Fumbling Forward » Blog Archive » JavaFX effects and hardware acceleration… [...]</description>
		<content:encoded><![CDATA[<p>[...] This is a nice little article which helps you understand whether your javafx implementation is hardware accelerated.Fumbling Forward » Blog Archive » JavaFX effects and hardware acceleration… [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fumbling Forward &#187; Blog Archive &#187; JavaFX and Hardware Acceleration (Take 3)</title>
		<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/comment-page-1/#comment-1001</link>
		<dc:creator>Fumbling Forward &#187; Blog Archive &#187; JavaFX and Hardware Acceleration (Take 3)</dc:creator>
		<pubDate>Wed, 22 Jul 2009 03:52:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=30#comment-1001</guid>
		<description>[...] forget everything I said in part 1 and part 2 of this [...]</description>
		<content:encoded><![CDATA[<p>[...] forget everything I said in part 1 and part 2 of this [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitri Trembovetski</title>
		<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/comment-page-1/#comment-998</link>
		<dc:creator>Dmitri Trembovetski</dc:creator>
		<pubDate>Tue, 21 Jul 2009 22:07:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=30#comment-998</guid>
		<description>Note that this becomes an issue only if the application explicitly initializes effect&#039;s peers by calling Effect.getAccelType() before the runtime has a chance to do so. When that happens there&#039;s user code on stack which causes the security exception.

This version of the app should correctly report acceleration:
import javafx.scene.Scene;
import javafx.scene.control.ListView;
import javafx.scene.effect.*;
import javafx.stage.Stage;
import java.awt.GraphicsEnvironment;
import javafx.scene.shape.Rectangle;

def gc = GraphicsEnvironment.
    getLocalGraphicsEnvironment().getDefaultScreenDevice().getDefaultConfiguration();
def effects = [
    Blend {}
    Bloom {}
    BoxBlur {}
    ColorAdjust {}
    DisplacementMap {}
    DropShadow {}
    Flood {}
    GaussianBlur {}
    Glow {}
    Identity {}
    InnerShadow {}
    InvertMask {}
    Lighting {}
    MotionBlur {}
    PerspectiveTransform {}
    Reflection {}
    SepiaTone {}
    Shadow {}
];
var accel : String[];

Stage {
    scene: Scene {
        content: [
            Rectangle { width: 10 height: 10 effect: GaussianBlur {} }
            ListView {
                width: 350
                items: bind accel
            }
        ]
    }
}
FX.deferAction(function():Void {
    accel = for (effect in effects)
        &quot;{effect.getClass().getSimpleName()}.getAccelType(gc)={effect.getAccelType(gc)}&quot;;
});

Dmitri</description>
		<content:encoded><![CDATA[<p>Note that this becomes an issue only if the application explicitly initializes effect&#8217;s peers by calling Effect.getAccelType() before the runtime has a chance to do so. When that happens there&#8217;s user code on stack which causes the security exception.</p>
<p>This version of the app should correctly report acceleration:<br />
import javafx.scene.Scene;<br />
import javafx.scene.control.ListView;<br />
import javafx.scene.effect.*;<br />
import javafx.stage.Stage;<br />
import java.awt.GraphicsEnvironment;<br />
import javafx.scene.shape.Rectangle;</p>
<p>def gc = GraphicsEnvironment.<br />
    getLocalGraphicsEnvironment().getDefaultScreenDevice().getDefaultConfiguration();<br />
def effects = [<br />
    Blend {}<br />
    Bloom {}<br />
    BoxBlur {}<br />
    ColorAdjust {}<br />
    DisplacementMap {}<br />
    DropShadow {}<br />
    Flood {}<br />
    GaussianBlur {}<br />
    Glow {}<br />
    Identity {}<br />
    InnerShadow {}<br />
    InvertMask {}<br />
    Lighting {}<br />
    MotionBlur {}<br />
    PerspectiveTransform {}<br />
    Reflection {}<br />
    SepiaTone {}<br />
    Shadow {}<br />
];<br />
var accel : String[];</p>
<p>Stage {<br />
    scene: Scene {<br />
        content: [<br />
            Rectangle { width: 10 height: 10 effect: GaussianBlur {} }<br />
            ListView {<br />
                width: 350<br />
                items: bind accel<br />
            }<br />
        ]<br />
    }<br />
}<br />
FX.deferAction(function():Void {<br />
    accel = for (effect in effects)<br />
        &#8220;{effect.getClass().getSimpleName()}.getAccelType(gc)={effect.getAccelType(gc)}&#8221;;<br />
});</p>
<p>Dmitri</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Osbaldeston</title>
		<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/comment-page-1/#comment-996</link>
		<dc:creator>Richard Osbaldeston</dc:creator>
		<pubDate>Tue, 21 Jul 2009 09:12:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=30#comment-996</guid>
		<description>Oh wait a minute app is signed but theres no security declaration in the JNLP resources section? was expecting to see  ?? 

I really hate that little floaty warning app window icon.. completely missed it, joe user dosent stand a chance (not that he&#039;d understand even if he did).</description>
		<content:encoded><![CDATA[<p>Oh wait a minute app is signed but theres no security declaration in the JNLP resources section? was expecting to see  ?? </p>
<p>I really hate that little floaty warning app window icon.. completely missed it, joe user dosent stand a chance (not that he&#8217;d understand even if he did).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Osbaldeston</title>
		<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/comment-page-1/#comment-995</link>
		<dc:creator>Richard Osbaldeston</dc:creator>
		<pubDate>Tue, 21 Jul 2009 09:01:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=30#comment-995</guid>
		<description>Hmm I&#039;ve just run it under Windows XP SP2 and got the same mix of CPU/SIMD &amp; Intrinsic result (NVidia 6600 here). The app was definitely signed but I still didnt see Direct3D, have Dmitri&#039;s changes been applied - did they make any difference?</description>
		<content:encoded><![CDATA[<p>Hmm I&#8217;ve just run it under Windows XP SP2 and got the same mix of CPU/SIMD &amp; Intrinsic result (NVidia 6600 here). The app was definitely signed but I still didnt see Direct3D, have Dmitri&#8217;s changes been applied &#8211; did they make any difference?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Herod</title>
		<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/comment-page-1/#comment-994</link>
		<dc:creator>Steven Herod</dc:creator>
		<pubDate>Tue, 21 Jul 2009 08:47:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=30#comment-994</guid>
		<description>Thanks Steve

And to think I paused over that checkbox and though.  &quot;Nah, it doesn&#039;t need signing...&quot;

This might explain why it seems to be fine on mac.  

I&#039;m going to write all this up in another blog entry...</description>
		<content:encoded><![CDATA[<p>Thanks Steve</p>
<p>And to think I paused over that checkbox and though.  &#8220;Nah, it doesn&#8217;t need signing&#8230;&#8221;</p>
<p>This might explain why it seems to be fine on mac.  </p>
<p>I&#8217;m going to write all this up in another blog entry&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Chin</title>
		<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/comment-page-1/#comment-993</link>
		<dc:creator>Stephen Chin</dc:creator>
		<pubDate>Tue, 21 Jul 2009 08:21:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=30#comment-993</guid>
		<description>I tracked down the issue with hardware acceleration on Windows Vista/7 where it was reporting CPU/SIMD from webstart applications, but Direct3D from regular applications.

It seems like there is a bug in the Decora code that prevents the Direct3D pipeline from running in the sandbox.  If you sign your application you will see that the problem goes away and it behaves identically to a desktop app, taking advantage of the Direct3D pipeline.  I filed this issue as RT-5193 in the JavaFX issue tracking system.</description>
		<content:encoded><![CDATA[<p>I tracked down the issue with hardware acceleration on Windows Vista/7 where it was reporting CPU/SIMD from webstart applications, but Direct3D from regular applications.</p>
<p>It seems like there is a bug in the Decora code that prevents the Direct3D pipeline from running in the sandbox.  If you sign your application you will see that the problem goes away and it behaves identically to a desktop app, taking advantage of the Direct3D pipeline.  I filed this issue as RT-5193 in the JavaFX issue tracking system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by sherod</title>
		<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/comment-page-1/#comment-991</link>
		<dc:creator>Twitted by sherod</dc:creator>
		<pubDate>Tue, 21 Jul 2009 06:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=30#comment-991</guid>
		<description>[...] This post was Twitted by sherod [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by sherod [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Giles</title>
		<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/comment-page-1/#comment-990</link>
		<dc:creator>Jonathan Giles</dc:creator>
		<pubDate>Tue, 21 Jul 2009 03:18:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=30#comment-990</guid>
		<description>Try the following code to get the graphics config:

var ge:GraphicsEnvironment = GraphicsEnvironment.getLocalGraphicsEnvironment();
var gs:GraphicsDevice[] = ge.getScreenDevices();
var gc:GraphicsConfiguration = gs[0].getDefaultConfiguration();</description>
		<content:encoded><![CDATA[<p>Try the following code to get the graphics config:</p>
<p>var ge:GraphicsEnvironment = GraphicsEnvironment.getLocalGraphicsEnvironment();<br />
var gs:GraphicsDevice[] = ge.getScreenDevices();<br />
var gc:GraphicsConfiguration = gs[0].getDefaultConfiguration();</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Giles</title>
		<link>http://blogs.herod.net/javafx/2009/07/javafx-effects-and-hardware-acceleration/comment-page-1/#comment-989</link>
		<dc:creator>Jonathan Giles</dc:creator>
		<pubDate>Tue, 21 Jul 2009 02:22:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.herod.net/javafx/?p=30#comment-989</guid>
		<description>From Chris Campbell at Sun: Intrinsic just means the &quot;platform&quot; handles the filtering operation.  Like, Reflection is implemented using Java2D operations, no shaders, no special software loops, so it&#039;s marked &quot;intrinsic&quot;.  Yeah, not the best name, but then again, people aren&#039;t supposed to know about getAccelType() either if the apidocs kept it hidden like it&#039;s supposed to be</description>
		<content:encoded><![CDATA[<p>From Chris Campbell at Sun: Intrinsic just means the &#8220;platform&#8221; handles the filtering operation.  Like, Reflection is implemented using Java2D operations, no shaders, no special software loops, so it&#8217;s marked &#8220;intrinsic&#8221;.  Yeah, not the best name, but then again, people aren&#8217;t supposed to know about getAccelType() either if the apidocs kept it hidden like it&#8217;s supposed to be</p>
]]></content:encoded>
	</item>
</channel>
</rss>

