<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: &#8220;JPEG&#8221; tile in beagle..</title>
	<link>http://www.tigert.com/archives/2004/11/11/jpeg-tile-in-beagle/</link>
	<description>um, what do I write here?</description>
	<pubDate>Wed, 19 Nov 2008 23:25:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3</generator>
		<item>
		<title>By: bkor</title>
		<link>http://www.tigert.com/archives/2004/11/11/jpeg-tile-in-beagle/#comment-209</link>
		<dc:creator>bkor</dc:creator>
		<pubDate>Thu, 11 Nov 2004 20:04:19 +0000</pubDate>
		<guid>http://www.tigert.com/archives/2004/11/11/jpeg-tile-in-beagle/#comment-209</guid>
		<description>Can you try to add --enable-default-toolkit=gtk2 to your Mozilla build? This should fix the scrollbars issue. I think you can configure this in jhbuild by using something like:
module_autogenargs['mozilla'] = autogenargs + '--enable-default-toolkit=gtk2'
in your ~/.jhbuildrc

Oh and I really like these screenshots. Nice to see this kind of progress since Guadec (the first time I heard about this).</description>
		<content:encoded><![CDATA[<p>Can you try to add &#8211;enable-default-toolkit=gtk2 to your Mozilla build? This should fix the scrollbars issue. I think you can configure this in jhbuild by using something like:<br />
module_autogenargs[&#8217;mozilla&#8217;] = autogenargs + &#8216;&#8211;enable-default-toolkit=gtk2&#8242;<br />
in your ~/.jhbuildrc</p>
<p>Oh and I really like these screenshots. Nice to see this kind of progress since Guadec (the first time I heard about this).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian McIntosh</title>
		<link>http://www.tigert.com/archives/2004/11/11/jpeg-tile-in-beagle/#comment-205</link>
		<dc:creator>Ian McIntosh</dc:creator>
		<pubDate>Thu, 11 Nov 2004 18:00:15 +0000</pubDate>
		<guid>http://www.tigert.com/archives/2004/11/11/jpeg-tile-in-beagle/#comment-205</guid>
		<description>This looks really nice.

Will we see the image’s dimensions (x,y) and file size show up there, too?  That sort of thing is probably more important than shutter speed to non-photographers.  :)

I don't know if this is your domain, but the word “More” in “Show More Results” might not be ideal.  Although it sounds good there, the opposite is “less” or “fewer", so the left button should really be “Show Fewer Results".  But "Fewer Results" doesn't really make sense. :)  If BEST is going to use paging, perhaps it should be "Next Page" and "Previous Page" or "Next Results" and "Previous Results".  Or, like Google, just "Next" and "Previous".  These have the added benefit of being shorter, so the window could be made thinner by the user (it looks like the buttons would prevent it from shrinking much as it is now).

An alternative to paging just occurred to me as I was writing: if the button remained as "More Results" it could literally put &lt;em&gt;more&lt;/em&gt; results on the page: up to 10, then 15, then 20.  Each time it would auto-scroll down to the first new one.  In that case it wouldn't need a "Less" button at all.  If the user wanted to go back to select a previous hit, they could just scroll up instead of paging/scrolling multiple times.  Just an idea.</description>
		<content:encoded><![CDATA[<p>This looks really nice.</p>
<p>Will we see the image’s dimensions (x,y) and file size show up there, too?  That sort of thing is probably more important than shutter speed to non-photographers.  <img src='http://www.tigert.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I don&#8217;t know if this is your domain, but the word “More” in “Show More Results” might not be ideal.  Although it sounds good there, the opposite is “less” or “fewer&#8221;, so the left button should really be “Show Fewer Results&#8221;.  But &#8220;Fewer Results&#8221; doesn&#8217;t really make sense. <img src='http://www.tigert.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  If BEST is going to use paging, perhaps it should be &#8220;Next Page&#8221; and &#8220;Previous Page&#8221; or &#8220;Next Results&#8221; and &#8220;Previous Results&#8221;.  Or, like Google, just &#8220;Next&#8221; and &#8220;Previous&#8221;.  These have the added benefit of being shorter, so the window could be made thinner by the user (it looks like the buttons would prevent it from shrinking much as it is now).</p>
<p>An alternative to paging just occurred to me as I was writing: if the button remained as &#8220;More Results&#8221; it could literally put <em>more</em> results on the page: up to 10, then 15, then 20.  Each time it would auto-scroll down to the first new one.  In that case it wouldn&#8217;t need a &#8220;Less&#8221; button at all.  If the user wanted to go back to select a previous hit, they could just scroll up instead of paging/scrolling multiple times.  Just an idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://www.tigert.com/archives/2004/11/11/jpeg-tile-in-beagle/#comment-203</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Thu, 11 Nov 2004 16:56:21 +0000</pubDate>
		<guid>http://www.tigert.com/archives/2004/11/11/jpeg-tile-in-beagle/#comment-203</guid>
		<description>I know youre wont be the one to deal with it, but I have a bit of a concern about the size of those tiles. 5 results per page seems constrictive. What would it take to have more results per page, tighter tile spacing and OSX Bar like zooming for the thumbnails (on either mouse over or click). Just a thought.</description>
		<content:encoded><![CDATA[<p>I know youre wont be the one to deal with it, but I have a bit of a concern about the size of those tiles. 5 results per page seems constrictive. What would it take to have more results per page, tighter tile spacing and OSX Bar like zooming for the thumbnails (on either mouse over or click). Just a thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Garrett LeSage</title>
		<link>http://www.tigert.com/archives/2004/11/11/jpeg-tile-in-beagle/#comment-200</link>
		<dc:creator>Garrett LeSage</dc:creator>
		<pubDate>Thu, 11 Nov 2004 14:41:03 +0000</pubDate>
		<guid>http://www.tigert.com/archives/2004/11/11/jpeg-tile-in-beagle/#comment-200</guid>
		<description>Somebody just needs to make Canon raw thumbnailing work... I'm sure somebody will (at least I hope); there are so many people in the office who have a Canon DSLR.

...Maybe I can convince &lt;a href="http://tech9.net/rml/log/"&gt;rml&lt;/a&gt; to do it. (:</description>
		<content:encoded><![CDATA[<p>Somebody just needs to make Canon raw thumbnailing work&#8230; I&#8217;m sure somebody will (at least I hope); there are so many people in the office who have a Canon DSLR.</p>
<p>&#8230;Maybe I can convince <a href="http://tech9.net/rml/log/" onclick="javascript:urchinTracker ('/outbound/comment/tech9.net');">rml</a> to do it. (:</p>
]]></content:encoded>
	</item>
</channel>
</rss>
