<?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"
	>
<channel>
	<title>Comments for It is what it is</title>
	<atom:link href="http://blog.julienviet.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.julienviet.com</link>
	<description>A pure technical trip</description>
	<pubDate>Sun, 01 Aug 2010 06:08:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>Comment on Nikon D80 HDR bracketing tutorial by Mike</title>
		<link>http://blog.julienviet.com/2009/01/06/nikon-d80-hdr-bracketing-tutorial/#comment-242</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 08 Jul 2009 12:05:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.julienviet.com/?p=92#comment-242</guid>
		<description>&#62;Focus mode should be configured to manual (perhaps it’s possible to use  &#62;automatic but I never tried).

In the past I left the focusing to Automatic and the shutter to continuos mode.  I am sure when I first tried this that the focus locked on first depression and stayed locked for the three shots.  However I may be mistaken.  
Having upgraded the firmware I see that it refocuses between shots which is a bit of a pain so manual it is.   I (and  one or two others) have registered  a support ticket with Nikon to get a firmware fix but don't hold your breath,  I guess we need a few million of us to do this before anything happens....</description>
		<content:encoded><![CDATA[<p>&gt;Focus mode should be configured to manual (perhaps it’s possible to use  &gt;automatic but I never tried).</p>
<p>In the past I left the focusing to Automatic and the shutter to continuos mode.  I am sure when I first tried this that the focus locked on first depression and stayed locked for the three shots.  However I may be mistaken.<br />
Having upgraded the firmware I see that it refocuses between shots which is a bit of a pain so manual it is.   I (and  one or two others) have registered  a support ticket with Nikon to get a firmware fix but don&#8217;t hold your breath,  I guess we need a few million of us to do this before anything happens&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Nikon D80 HDR bracketing tutorial by Srini</title>
		<link>http://blog.julienviet.com/2009/01/06/nikon-d80-hdr-bracketing-tutorial/#comment-232</link>
		<dc:creator>Srini</dc:creator>
		<pubDate>Thu, 18 Jun 2009 18:59:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.julienviet.com/?p=92#comment-232</guid>
		<description>You tutorial is awesome, I got what I need to setup my D80</description>
		<content:encoded><![CDATA[<p>You tutorial is awesome, I got what I need to setup my D80</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Nikon D80 HDR bracketing tutorial by Ikeer Savage</title>
		<link>http://blog.julienviet.com/2009/01/06/nikon-d80-hdr-bracketing-tutorial/#comment-221</link>
		<dc:creator>Ikeer Savage</dc:creator>
		<pubDate>Mon, 18 May 2009 20:48:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.julienviet.com/?p=92#comment-221</guid>
		<description>I have been trying to take HDR pictures and i found out that i made 2 mistakes.. I never change the focus to manual and the shooting mode was not continous.. as a result... very difficult to make a nice HDR :(.. thank you.!!!</description>
		<content:encoded><![CDATA[<p>I have been trying to take HDR pictures and i found out that i made 2 mistakes.. I never change the focus to manual and the shooting mode was not continous.. as a result&#8230; very difficult to make a nice HDR :(.. thank you.!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Nikon D80 HDR bracketing tutorial by nikon digital camera review</title>
		<link>http://blog.julienviet.com/2009/01/06/nikon-d80-hdr-bracketing-tutorial/#comment-212</link>
		<dc:creator>nikon digital camera review</dc:creator>
		<pubDate>Thu, 26 Mar 2009 17:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.julienviet.com/?p=92#comment-212</guid>
		<description>I should know there is great post like this earlier so I can save a lot of time to search, surely bookmark this page, thx!</description>
		<content:encoded><![CDATA[<p>I should know there is great post like this earlier so I can save a lot of time to search, surely bookmark this page, thx!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The future is so bright&#8230; by Kevin Viet</title>
		<link>http://blog.julienviet.com/2008/09/05/the-future-is-so-bright/#comment-85</link>
		<dc:creator>Kevin Viet</dc:creator>
		<pubDate>Sat, 06 Sep 2008 11:35:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.julienviet.com/?p=41#comment-85</guid>
		<description>Congrat bro'
I wish the best for you</description>
		<content:encoded><![CDATA[<p>Congrat bro&#8217;<br />
I wish the best for you</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The future is so bright&#8230; by Michael Neale</title>
		<link>http://blog.julienviet.com/2008/09/05/the-future-is-so-bright/#comment-80</link>
		<dc:creator>Michael Neale</dc:creator>
		<pubDate>Fri, 05 Sep 2008 22:12:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.julienviet.com/?p=41#comment-80</guid>
		<description>Congrats Julien - sounds like you will have a blast there. Hopefully you had some time off between gigs !</description>
		<content:encoded><![CDATA[<p>Congrats Julien - sounds like you will have a blast there. Hopefully you had some time off between gigs !</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The footprint of the Air Ajax runtime by Julien Viet</title>
		<link>http://blog.julienviet.com/2008/08/21/air-ajax-runtime-footprint/#comment-17</link>
		<dc:creator>Julien Viet</dc:creator>
		<pubDate>Fri, 22 Aug 2008 13:53:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.julienviet.com/?p=23#comment-17</guid>
		<description>@Finkler: I agree with you that 20megs is not the fundamental problem. For me the most problematic issue is the CPU consumed. Spaz itself consumes around 10% of my CPU even if it does not seem active (i.e just waiting the next refresh). About the leak, indeed the memory consumed seems to increase and Adobe does not provide the tools or the hooks (à la Java VM instrumentation) to properly know what happens.</description>
		<content:encoded><![CDATA[<p>@Finkler: I agree with you that 20megs is not the fundamental problem. For me the most problematic issue is the CPU consumed. Spaz itself consumes around 10% of my CPU even if it does not seem active (i.e just waiting the next refresh). About the leak, indeed the memory consumed seems to increase and Adobe does not provide the tools or the hooks (à la Java VM instrumentation) to properly know what happens.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The footprint of the Air Ajax runtime by Ed Finkler</title>
		<link>http://blog.julienviet.com/2008/08/21/air-ajax-runtime-footprint/#comment-16</link>
		<dc:creator>Ed Finkler</dc:creator>
		<pubDate>Fri, 22 Aug 2008 13:50:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.julienviet.com/?p=23#comment-16</guid>
		<description>AIR itself isn't slim, for sure. Instantiating a webkit instance makes it even bigger, though, but that's not surprising: browser engines are not lightweight. What is particularly problematic is that there seem to be memory leaks within the webkit engine as used in AIR, and there is no way to profile memory usage. Apps like Spaz run into this problem because it's constantly pulling in large amounts of new data, loading new images, and the like.

Also note that the CPU usage while idling is particularly a problem with OS X. On Windows, AIR seems to not have this problem.

I don't think using 20MB or more is horrible, considering the technology. AIR is a full Flash runtime, and HTML apps add a webkit renderer on top of that. The memory and CPU usage is in line -- or a bit lower -- than most SSBs. Using traditional browser tech to build a desktop app is going to be a tradeoff in terms of memory and CPU usage, no doubt.</description>
		<content:encoded><![CDATA[<p>AIR itself isn&#8217;t slim, for sure. Instantiating a webkit instance makes it even bigger, though, but that&#8217;s not surprising: browser engines are not lightweight. What is particularly problematic is that there seem to be memory leaks within the webkit engine as used in AIR, and there is no way to profile memory usage. Apps like Spaz run into this problem because it&#8217;s constantly pulling in large amounts of new data, loading new images, and the like.</p>
<p>Also note that the CPU usage while idling is particularly a problem with OS X. On Windows, AIR seems to not have this problem.</p>
<p>I don&#8217;t think using 20MB or more is horrible, considering the technology. AIR is a full Flash runtime, and HTML apps add a webkit renderer on top of that. The memory and CPU usage is in line &#8212; or a bit lower &#8212; than most SSBs. Using traditional browser tech to build a desktop app is going to be a tradeoff in terms of memory and CPU usage, no doubt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The footprint of the Air Ajax runtime by Chui Tey</title>
		<link>http://blog.julienviet.com/2008/08/21/air-ajax-runtime-footprint/#comment-15</link>
		<dc:creator>Chui Tey</dc:creator>
		<pubDate>Fri, 22 Aug 2008 12:35:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.julienviet.com/?p=23#comment-15</guid>
		<description>JavaFX is pretty fat too. There isn't a base CPU load, but 30 Mbs RAM on a hello world app is not uncommon.</description>
		<content:encoded><![CDATA[<p>JavaFX is pretty fat too. There isn&#8217;t a base CPU load, but 30 Mbs RAM on a hello world app is not uncommon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The footprint of the Air Ajax runtime by Gaurav</title>
		<link>http://blog.julienviet.com/2008/08/21/air-ajax-runtime-footprint/#comment-14</link>
		<dc:creator>Gaurav</dc:creator>
		<pubDate>Fri, 22 Aug 2008 08:41:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.julienviet.com/?p=23#comment-14</guid>
		<description>Yes, it does take 20 megs. I tried it out too. Its fault on the part of the air runtime definitely.</description>
		<content:encoded><![CDATA[<p>Yes, it does take 20 megs. I tried it out too. Its fault on the part of the air runtime definitely.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
