<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Aurélien's room</title>
	<atom:link href="http://agateau.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://agateau.wordpress.com</link>
	<description>Random bits and things of interest</description>
	<lastBuildDate>Fri, 06 Nov 2009 21:45:57 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Gwenview Importer by Lure</title>
		<link>http://agateau.wordpress.com/2009/11/06/gwenview-importer/#comment-1500</link>
		<dc:creator>Lure</dc:creator>
		<pubDate>Fri, 06 Nov 2009 21:45:57 +0000</pubDate>
		<guid isPermaLink="false">http://agateau.wordpress.com/?p=278#comment-1500</guid>
		<description>I agree that importing could be shared more between both apps, even possibly just have one importer.

I think digikam will anyhow index/scan newly detected photos under the trees that are configured for photo collections. And having the default photo app (like e-mail, web-browser...) would be great, as importer could then auto-start the chosen application (gwenview, digikam...).

And BTW: great work on gwenview - I really like your balance between simplicity and powerfullness of the application. Most of the stuff you do, feels just enough for  &quot;typical user&quot; (like my father...).</description>
		<content:encoded><![CDATA[<p>I agree that importing could be shared more between both apps, even possibly just have one importer.</p>
<p>I think digikam will anyhow index/scan newly detected photos under the trees that are configured for photo collections. And having the default photo app (like e-mail, web-browser&#8230;) would be great, as importer could then auto-start the chosen application (gwenview, digikam&#8230;).</p>
<p>And BTW: great work on gwenview &#8211; I really like your balance between simplicity and powerfullness of the application. Most of the stuff you do, feels just enough for  &#8220;typical user&#8221; (like my father&#8230;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gwenview Importer by Aurélien</title>
		<link>http://agateau.wordpress.com/2009/11/06/gwenview-importer/#comment-1499</link>
		<dc:creator>Aurélien</dc:creator>
		<pubDate>Fri, 06 Nov 2009 20:04:28 +0000</pubDate>
		<guid isPermaLink="false">http://agateau.wordpress.com/?p=278#comment-1499</guid>
		<description>Thanks for the info, added this to my TODO.</description>
		<content:encoded><![CDATA[<p>Thanks for the info, added this to my TODO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gwenview Importer by Aurélien</title>
		<link>http://agateau.wordpress.com/2009/11/06/gwenview-importer/#comment-1498</link>
		<dc:creator>Aurélien</dc:creator>
		<pubDate>Fri, 06 Nov 2009 20:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://agateau.wordpress.com/?p=278#comment-1498</guid>
		<description>I was thinking about associating apps with devices as well.

For example there could be a &quot;Always open this device with this application&quot; checkbox at the bottom of the device importer popup. User could then manage associations via the widget settings. What do you think of this, Aaron?</description>
		<content:encoded><![CDATA[<p>I was thinking about associating apps with devices as well.</p>
<p>For example there could be a &#8220;Always open this device with this application&#8221; checkbox at the bottom of the device importer popup. User could then manage associations via the widget settings. What do you think of this, Aaron?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gwenview Importer by Aurélien</title>
		<link>http://agateau.wordpress.com/2009/11/06/gwenview-importer/#comment-1497</link>
		<dc:creator>Aurélien</dc:creator>
		<pubDate>Fri, 06 Nov 2009 19:58:52 +0000</pubDate>
		<guid isPermaLink="false">http://agateau.wordpress.com/?p=278#comment-1497</guid>
		<description>The date format cannot be changed right now. It is not the U.S format (which is month, day, year) it is the ISO format (year, month, day). The advantage of this format is that if you sort by filenames, you get image sorted by shooting date as well.

It depends on libgwenview (which is an internal library) but it could run without the gwenview binary. The only thing to change would be not hardcoding the fact that it starts Gwenview at the end. I can do this if there is enough demand for it.</description>
		<content:encoded><![CDATA[<p>The date format cannot be changed right now. It is not the U.S format (which is month, day, year) it is the ISO format (year, month, day). The advantage of this format is that if you sort by filenames, you get image sorted by shooting date as well.</p>
<p>It depends on libgwenview (which is an internal library) but it could run without the gwenview binary. The only thing to change would be not hardcoding the fact that it starts Gwenview at the end. I can do this if there is enough demand for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gwenview Importer by Aurélien</title>
		<link>http://agateau.wordpress.com/2009/11/06/gwenview-importer/#comment-1496</link>
		<dc:creator>Aurélien</dc:creator>
		<pubDate>Fri, 06 Nov 2009 19:49:58 +0000</pubDate>
		<guid isPermaLink="false">http://agateau.wordpress.com/?p=278#comment-1496</guid>
		<description>I disagree. A checkbox which you have to check everytime is tedious, and a checkbox whose state is remembered is dangerous. I don&#039;t think the user will click the button by mistake, especially since it&#039;s labeled &quot;Delete&quot; and not &quot;Yes&quot;.</description>
		<content:encoded><![CDATA[<p>I disagree. A checkbox which you have to check everytime is tedious, and a checkbox whose state is remembered is dangerous. I don&#8217;t think the user will click the button by mistake, especially since it&#8217;s labeled &#8220;Delete&#8221; and not &#8220;Yes&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gwenview Importer by Aurélien</title>
		<link>http://agateau.wordpress.com/2009/11/06/gwenview-importer/#comment-1495</link>
		<dc:creator>Aurélien</dc:creator>
		<pubDate>Fri, 06 Nov 2009 19:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://agateau.wordpress.com/?p=278#comment-1495</guid>
		<description>For now it does not decide on the structure: it defaults to the xdg pictures folders (which is ~/Pictures if I am not mistaken). It remembers the destination folder so next time you import your pictures, chances are high it will already be using the correct folder, or you will just need to change the last part of it.</description>
		<content:encoded><![CDATA[<p>For now it does not decide on the structure: it defaults to the xdg pictures folders (which is ~/Pictures if I am not mistaken). It remembers the destination folder so next time you import your pictures, chances are high it will already be using the correct folder, or you will just need to change the last part of it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gwenview Importer by Aurélien</title>
		<link>http://agateau.wordpress.com/2009/11/06/gwenview-importer/#comment-1494</link>
		<dc:creator>Aurélien</dc:creator>
		<pubDate>Fri, 06 Nov 2009 19:44:58 +0000</pubDate>
		<guid isPermaLink="false">http://agateau.wordpress.com/?p=278#comment-1494</guid>
		<description>DigiKam and Gwenview already share code through kipi plugins. I am not sure sharing the importer makes sense because DigiKam needs to do more work on the imported pictures (indexing them in its database for example)</description>
		<content:encoded><![CDATA[<p>DigiKam and Gwenview already share code through kipi plugins. I am not sure sharing the importer makes sense because DigiKam needs to do more work on the imported pictures (indexing them in its database for example)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gwenview Importer by thorGT</title>
		<link>http://agateau.wordpress.com/2009/11/06/gwenview-importer/#comment-1493</link>
		<dc:creator>thorGT</dc:creator>
		<pubDate>Fri, 06 Nov 2009 17:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://agateau.wordpress.com/?p=278#comment-1493</guid>
		<description>Well, to be honest there is a renaming tool in Digikam, which is quite similar to what is described here. So you could maybe have a look at what they do?
OT: Why couldn&#039;t Gwenview and Digikam share *some* code in future? They seem to be duplicating each other, e.g. icon view with similar overlays, now Import and Rename tool..... I know that Digikam is more of a professional photo-management program, but manpower is limited, you see :)</description>
		<content:encoded><![CDATA[<p>Well, to be honest there is a renaming tool in Digikam, which is quite similar to what is described here. So you could maybe have a look at what they do?<br />
OT: Why couldn&#8217;t Gwenview and Digikam share *some* code in future? They seem to be duplicating each other, e.g. icon view with similar overlays, now Import and Rename tool&#8230;.. I know that Digikam is more of a professional photo-management program, but manpower is limited, you see <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gwenview Importer by Aaron Seigo</title>
		<link>http://agateau.wordpress.com/2009/11/06/gwenview-importer/#comment-1492</link>
		<dc:creator>Aaron Seigo</dc:creator>
		<pubDate>Fri, 06 Nov 2009 17:04:53 +0000</pubDate>
		<guid isPermaLink="false">http://agateau.wordpress.com/?p=278#comment-1492</guid>
		<description>Yes, it does know. In StorageDrive there is the DriveType enum which has these values: { HardDisk, CdromDrive, Floppy, Tape, CompactFlash, MemoryStick, SmartMedia, SdMmc, Xd }</description>
		<content:encoded><![CDATA[<p>Yes, it does know. In StorageDrive there is the DriveType enum which has these values: { HardDisk, CdromDrive, Floppy, Tape, CompactFlash, MemoryStick, SmartMedia, SdMmc, Xd }</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gwenview Importer by Aaron Seigo</title>
		<link>http://agateau.wordpress.com/2009/11/06/gwenview-importer/#comment-1491</link>
		<dc:creator>Aaron Seigo</dc:creator>
		<pubDate>Fri, 06 Nov 2009 17:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://agateau.wordpress.com/?p=278#comment-1491</guid>
		<description>The number of times people plug in USB drives (solid state or just external drives) that have generic data on dwarfs the number of times camera storage cards are plugged in. Optimizing for the small use case doesn&#039;t make sense, and it makes the interface look very stupid when it asks to import photos from your USB stick or in my case a 500MB drive that doesn&#039;t have photos at all on it.

In the case of an SD card directly slotted in, one can start the important from gwenview or digikam directly.

Someone could also work on Solid&#039;s actions being slightly more intelligent by being able to look at what&#039;s on a device or remembering specific volume labels (so when you manually import into gwenview once, it would record the label of that volume and prompt to do the same thing automatically next time you plug it in; aka &quot;trainging&quot;).

That would be the &quot;right&quot; way of going about it. A mostly-of-the-time-wrong dumb interface isn&#039;t.</description>
		<content:encoded><![CDATA[<p>The number of times people plug in USB drives (solid state or just external drives) that have generic data on dwarfs the number of times camera storage cards are plugged in. Optimizing for the small use case doesn&#8217;t make sense, and it makes the interface look very stupid when it asks to import photos from your USB stick or in my case a 500MB drive that doesn&#8217;t have photos at all on it.</p>
<p>In the case of an SD card directly slotted in, one can start the important from gwenview or digikam directly.</p>
<p>Someone could also work on Solid&#8217;s actions being slightly more intelligent by being able to look at what&#8217;s on a device or remembering specific volume labels (so when you manually import into gwenview once, it would record the label of that volume and prompt to do the same thing automatically next time you plug it in; aka &#8220;trainging&#8221;).</p>
<p>That would be the &#8220;right&#8221; way of going about it. A mostly-of-the-time-wrong dumb interface isn&#8217;t.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
