<?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 for Benjamin Stover</title>
	<atom:link href="http://stechz.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://stechz.com</link>
	<description></description>
	<lastBuildDate>Mon, 01 Feb 2010 18:22:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Creating a robust kinetic animation by Benjamin Stover</title>
		<link>http://stechz.com/2010/robust-kinetic-animation/comment-page-1/#comment-251</link>
		<dc:creator>Benjamin Stover</dc:creator>
		<pubDate>Mon, 01 Feb 2010 18:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://stechz.com/?p=119#comment-251</guid>
		<description>Forgot about this comment!  I think it&#039;d be fun to try ~ -v, if only because it&#039;s a differential equation :)

Also, Wordpress does not seem to like *&#039;s in URLs.  Huh.</description>
		<content:encoded><![CDATA[<p>Forgot about this comment!  I think it&#8217;d be fun to try ~ -v, if only because it&#8217;s a differential equation :)</p>
<p>Also, Wordpress does not seem to like *&#8217;s in URLs.  Huh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox for Maemo RC3 is out by Benjamin Stover</title>
		<link>http://stechz.com/2010/rc3-is-out/comment-page-1/#comment-250</link>
		<dc:creator>Benjamin Stover</dc:creator>
		<pubDate>Mon, 01 Feb 2010 18:20:07 +0000</pubDate>
		<guid isPermaLink="false">http://stechz.com/?p=279#comment-250</guid>
		<description>@voracity: Yep, you hit it dead on.  Since drawing competes with responsiveness, we try to be careful about when we draw parts of the page that are not on screen, especially if there is a lot of animation on the page.</description>
		<content:encoded><![CDATA[<p>@voracity: Yep, you hit it dead on.  Since drawing competes with responsiveness, we try to be careful about when we draw parts of the page that are not on screen, especially if there is a lot of animation on the page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox for Maemo RC3 is out by voracity</title>
		<link>http://stechz.com/2010/rc3-is-out/comment-page-1/#comment-239</link>
		<dc:creator>voracity</dc:creator>
		<pubDate>Sat, 30 Jan 2010 05:46:44 +0000</pubDate>
		<guid isPermaLink="false">http://stechz.com/?p=279#comment-239</guid>
		<description>Once the page has loaded, it works pretty well. Although, I&#039;ve noticed that I see the checkmarked background during scrolling more than I&#039;d like --- certainly more than microb. It seems to only redraw the checkmarked areas _after_ the scrolling stops. Is that right? Another job for electrolysis?</description>
		<content:encoded><![CDATA[<p>Once the page has loaded, it works pretty well. Although, I&#8217;ve noticed that I see the checkmarked background during scrolling more than I&#8217;d like &#8212; certainly more than microb. It seems to only redraw the checkmarked areas _after_ the scrolling stops. Is that right? Another job for electrolysis?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox for Maemo RC3 is out by Benjamin Stover</title>
		<link>http://stechz.com/2010/rc3-is-out/comment-page-1/#comment-233</link>
		<dc:creator>Benjamin Stover</dc:creator>
		<pubDate>Fri, 29 Jan 2010 18:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://stechz.com/?p=279#comment-233</guid>
		<description>@Manuel: It sounds like you have a mismatched xulrunner.  Make sure you are on the stable channel (http://ftp.mozilla.org/pub/mozilla.org/mobile/mozilla-fennec.install), uninstall fennec and xulrunner, and reinstall.  Sorry for the trouble!

@voracity: I definitely feel your pain on loading pages, but for me after most of the content has loaded it becomes pretty usable.  Is that not your experience?  Regardless, I&#039;m super excited about where electrolysis can take us in terms of responsiveness.  Thanks for being patient with us :)</description>
		<content:encoded><![CDATA[<p>@Manuel: It sounds like you have a mismatched xulrunner.  Make sure you are on the stable channel (<a href="http://ftp.mozilla.org/pub/mozilla.org/mobile/mozilla-fennec.install" rel="nofollow">http://ftp.mozilla.org/pub/mozilla.org/mobile/mozilla-fennec.install</a>), uninstall fennec and xulrunner, and reinstall.  Sorry for the trouble!</p>
<p>@voracity: I definitely feel your pain on loading pages, but for me after most of the content has loaded it becomes pretty usable.  Is that not your experience?  Regardless, I&#8217;m super excited about where electrolysis can take us in terms of responsiveness.  Thanks for being patient with us :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox for Maemo RC3 is out by voracity</title>
		<link>http://stechz.com/2010/rc3-is-out/comment-page-1/#comment-231</link>
		<dc:creator>voracity</dc:creator>
		<pubDate>Fri, 29 Jan 2010 11:24:09 +0000</pubDate>
		<guid isPermaLink="false">http://stechz.com/?p=279#comment-231</guid>
		<description>It&#039;s getting better, but the page is still completely unusable while it&#039;s loading (which, given loading times on mobile, is not a good thing...) I guess I have to wait for electrolysis before I can start using it.</description>
		<content:encoded><![CDATA[<p>It&#8217;s getting better, but the page is still completely unusable while it&#8217;s loading (which, given loading times on mobile, is not a good thing&#8230;) I guess I have to wait for electrolysis before I can start using it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Firefox for Maemo RC3 is out by Manuel Serrano</title>
		<link>http://stechz.com/2010/rc3-is-out/comment-page-1/#comment-229</link>
		<dc:creator>Manuel Serrano</dc:creator>
		<pubDate>Fri, 29 Jan 2010 05:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://stechz.com/?p=279#comment-229</guid>
		<description>As soon as I read the announce, I update my fennec and xulrunner packages and now, I&#039;m no longer able to run firefox on
the n900. I have tried twice to remove fennec and xulrunner and re-install them but I&#039;m stuck with:

$ fennec
Could not find compatible GRE between version 1.9.2b5pre and 1.9.2.1.

would you have some advices for me?

Thanks in advance.

--
Manuel</description>
		<content:encoded><![CDATA[<p>As soon as I read the announce, I update my fennec and xulrunner packages and now, I&#8217;m no longer able to run firefox on<br />
the n900. I have tried twice to remove fennec and xulrunner and re-install them but I&#8217;m stuck with:</p>
<p>$ fennec<br />
Could not find compatible GRE between version 1.9.2b5pre and 1.9.2.1.</p>
<p>would you have some advices for me?</p>
<p>Thanks in advance.</p>
<p>&#8211;<br />
Manuel</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating a robust kinetic animation by Axel Hecht</title>
		<link>http://stechz.com/2010/robust-kinetic-animation/comment-page-1/#comment-184</link>
		<dc:creator>Axel Hecht</dc:creator>
		<pubDate>Tue, 19 Jan 2010 20:30:18 +0000</pubDate>
		<guid isPermaLink="false">http://stechz.com/?p=119#comment-184</guid>
		<description>eddy current brakes are a ~ -v, so you&#039;ll get a higher de-acceleration on higher speeds, and lower on lower speeds. The solution without any other tweaks is an exponential decline in velocity, http://www.wolframalpha.com/input/?i=v%27%28t%29+%3D+-k*v%28t%29 or http://www.wolframalpha.com/input/?i=v%27%28t%29+%3D+-k*v%28t%29. If you&#039;re adding a constant additional force, you end up with http://www.wolframalpha.com/input/?i=x%27%27%28t%29+%3D+-k*x%27%28t%29-a

Not sure if that&#039;d feel more natural or not.</description>
		<content:encoded><![CDATA[<p>eddy current brakes are a ~ -v, so you&#8217;ll get a higher de-acceleration on higher speeds, and lower on lower speeds. The solution without any other tweaks is an exponential decline in velocity, <a href="http://www.wolframalpha.com/input/?i=v%27%28t%29+%3D+-k" rel="nofollow">http://www.wolframalpha.com/input/?i=v%27%28t%29+%3D+-k</a>*v%28t%29 or <a href="http://www.wolframalpha.com/input/?i=v%27%28t%29+%3D+-k" rel="nofollow">http://www.wolframalpha.com/input/?i=v%27%28t%29+%3D+-k</a>*v%28t%29. If you&#8217;re adding a constant additional force, you end up with <a href="http://www.wolframalpha.com/input/?i=x%27%27%28t%29+%3D+-k" rel="nofollow">http://www.wolframalpha.com/input/?i=x%27%27%28t%29+%3D+-k</a>*x%27%28t%29-a</p>
<p>Not sure if that&#8217;d feel more natural or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating a robust kinetic animation by Benjamin Stover</title>
		<link>http://stechz.com/2010/robust-kinetic-animation/comment-page-1/#comment-183</link>
		<dc:creator>Benjamin Stover</dc:creator>
		<pubDate>Tue, 19 Jan 2010 18:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://stechz.com/?p=119#comment-183</guid>
		<description>&lt;blockquote&gt;
I kinda doubt your last time formula. On perfect timing, that’d make time be close to zero throughout. Maybe a ‘+’ instead of a ‘-’?
&lt;/blockquote&gt;

Good catch.  This is an average so it should be a +.

&lt;blockquote&gt;
I suspect the speed bump could come from checkerboard vs not. I.e., your t_now is start_paint, but the user sees end_paint time. If the regular page drawing takes more time than the checkerboard drawing, you’d get a speed up, going from the delayed page-rendering parabola to the less-delayed checkerboard-rendering parabola.
&lt;/blockquote&gt;

I was always testing with a completely rendered page, without any checkerboards.  I think you&#039;re right about the delay being different later in the pan though.

&lt;blockquote&gt;
I wonder if you can already assume that the time-location data that you use to calculate initial position and velocity are page-rendering delayed. If so, you’d get into the parabula fine. If not, you’d end up with a skewed initial path, too.
&lt;/blockquote&gt;

I had toyed with this idea, shifting time a little more in the beginning than in the end.  Ultimately I found something that worked but felt the time average was more elegant and improved the smoothness of the animation at the same time.

&lt;blockquote&gt;
That said, have you tried other friction algorithms? Like an eddy current brake? Not sure that’s even terminating in time, but you could add a tad of mechanical friction to it for that.
&lt;/blockquote&gt;

I based my parabola on classical friction that you learn in mechanical physics.  Classical friction force is a function of the normal force and the textures of the two surfaces but not position or velocity or time, so if F=ma then a=F/m, so the acceleration factor is a constant for us, creating a parabola.  I don&#039;t really know anything about eddy current brakes and I didn&#039;t find any useful formulas with a quick Google search.

I have been curious about other higher-order formulas.  I&#039;ve tried a few different polynomials several months ago, and I believe Fennec has used sqrt in earlier iterations.  At the end it comes down to &quot;how does it feel,&quot; and so far parabolas have felt the best to me.</description>
		<content:encoded><![CDATA[<blockquote><p>
I kinda doubt your last time formula. On perfect timing, that’d make time be close to zero throughout. Maybe a ‘+’ instead of a ‘-’?
</p></blockquote>
<p>Good catch.  This is an average so it should be a +.</p>
<blockquote><p>
I suspect the speed bump could come from checkerboard vs not. I.e., your t_now is start_paint, but the user sees end_paint time. If the regular page drawing takes more time than the checkerboard drawing, you’d get a speed up, going from the delayed page-rendering parabola to the less-delayed checkerboard-rendering parabola.
</p></blockquote>
<p>I was always testing with a completely rendered page, without any checkerboards.  I think you&#8217;re right about the delay being different later in the pan though.</p>
<blockquote><p>
I wonder if you can already assume that the time-location data that you use to calculate initial position and velocity are page-rendering delayed. If so, you’d get into the parabula fine. If not, you’d end up with a skewed initial path, too.
</p></blockquote>
<p>I had toyed with this idea, shifting time a little more in the beginning than in the end.  Ultimately I found something that worked but felt the time average was more elegant and improved the smoothness of the animation at the same time.</p>
<blockquote><p>
That said, have you tried other friction algorithms? Like an eddy current brake? Not sure that’s even terminating in time, but you could add a tad of mechanical friction to it for that.
</p></blockquote>
<p>I based my parabola on classical friction that you learn in mechanical physics.  Classical friction force is a function of the normal force and the textures of the two surfaces but not position or velocity or time, so if F=ma then a=F/m, so the acceleration factor is a constant for us, creating a parabola.  I don&#8217;t really know anything about eddy current brakes and I didn&#8217;t find any useful formulas with a quick Google search.</p>
<p>I have been curious about other higher-order formulas.  I&#8217;ve tried a few different polynomials several months ago, and I believe Fennec has used sqrt in earlier iterations.  At the end it comes down to &#8220;how does it feel,&#8221; and so far parabolas have felt the best to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating a robust kinetic animation by Axel Hecht</title>
		<link>http://stechz.com/2010/robust-kinetic-animation/comment-page-1/#comment-180</link>
		<dc:creator>Axel Hecht</dc:creator>
		<pubDate>Tue, 19 Jan 2010 00:00:09 +0000</pubDate>
		<guid isPermaLink="false">http://stechz.com/?p=119#comment-180</guid>
		<description>I kinda doubt your last time formula. On perfect timing, that&#039;d make time be close to zero throughout. Maybe a &#039;+&#039; instead of a &#039;-&#039;?

I suspect the speed bump could come from checkerboard vs not. I.e., your t_now is start_paint, but the user sees end_paint time. If the regular page drawing takes more time than the checkerboard drawing, you&#039;d get a speed up, going from the delayed page-rendering parabola to the less-delayed checkerboard-rendering parabola.

Taking a mean between real time and equidistant timing probably eases that effect, as you&#039;re late in the page-rendering part, and you claim you&#039;re not by taking some fraction of the equidistant timing, and thus making your start_paint be a tad early. Kind-of averages out the being-late of the last step with the being late of the next step.

I wonder if you can already assume that the time-location data that you use to calculate initial position and velocity are page-rendering delayed. If so, you&#039;d get into the parabula fine. If not, you&#039;d end up with a skewed initial path, too.

That said, have you tried other friction algorithms? Like an eddy current brake? Not sure that&#039;s even terminating in time, but you could add a tad of mechanical friction to it for that.</description>
		<content:encoded><![CDATA[<p>I kinda doubt your last time formula. On perfect timing, that&#8217;d make time be close to zero throughout. Maybe a &#8216;+&#8217; instead of a &#8216;-&#8217;?</p>
<p>I suspect the speed bump could come from checkerboard vs not. I.e., your t_now is start_paint, but the user sees end_paint time. If the regular page drawing takes more time than the checkerboard drawing, you&#8217;d get a speed up, going from the delayed page-rendering parabola to the less-delayed checkerboard-rendering parabola.</p>
<p>Taking a mean between real time and equidistant timing probably eases that effect, as you&#8217;re late in the page-rendering part, and you claim you&#8217;re not by taking some fraction of the equidistant timing, and thus making your start_paint be a tad early. Kind-of averages out the being-late of the last step with the being late of the next step.</p>
<p>I wonder if you can already assume that the time-location data that you use to calculate initial position and velocity are page-rendering delayed. If so, you&#8217;d get into the parabula fine. If not, you&#8217;d end up with a skewed initial path, too.</p>
<p>That said, have you tried other friction algorithms? Like an eddy current brake? Not sure that&#8217;s even terminating in time, but you could add a tad of mechanical friction to it for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creating a robust kinetic animation by Sam Alexander</title>
		<link>http://stechz.com/2010/robust-kinetic-animation/comment-page-1/#comment-179</link>
		<dc:creator>Sam Alexander</dc:creator>
		<pubDate>Mon, 18 Jan 2010 21:54:48 +0000</pubDate>
		<guid isPermaLink="false">http://stechz.com/?p=119#comment-179</guid>
		<description>Gorrilas!  That &amp; Nibbles were my first ever &quot;peak-under-the-hood&quot; as well.

Ben -- you are a mathematician masquerading as a programmer.  Someone will find you out.  You can&#039;t hide forever.</description>
		<content:encoded><![CDATA[<p>Gorrilas!  That &amp; Nibbles were my first ever &#8220;peak-under-the-hood&#8221; as well.</p>
<p>Ben &#8212; you are a mathematician masquerading as a programmer.  Someone will find you out.  You can&#8217;t hide forever.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
