<?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: Vista picture &#8220;Web Publishing&#8221; regression</title>
	<atom:link href="http://bergs.biz/blog/2009/06/07/vista-picture-web-publishing-regression/feed/" rel="self" type="application/rss+xml" />
	<link>http://bergs.biz/blog/2009/06/07/vista-picture-web-publishing-regression/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 06 Mar 2012 08:56:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Jochen Wolters</title>
		<link>http://bergs.biz/blog/2009/06/07/vista-picture-web-publishing-regression/#comment-20455</link>
		<dc:creator>Jochen Wolters</dc:creator>
		<pubDate>Mon, 24 Aug 2009 08:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://bergs.biz/blog/?p=78#comment-20455</guid>
		<description>Well, I don&#039;t think that iPhoto or Aperture will be EOL&#039;ed anytime soon, but if they are, you will still be able to use either application&#039;s export functions to move your media into another application. What&#039;s more, many competing programs allow importing existing databases from other applications, so the threat of lock-in almost becomes a non-issue.

As for keeping files in a database, both iPhoto and Aperture on the Mac use packages for their databases, and these do contain the unmodified original photos. If all else — including exporting from within the app — fails, you can still &quot;Show Package Contents&quot; for a database in the Finder and rescue the media that way.

Same for iTunes, by the way: its media library is just a folder tree, sorted by artists and albums, and the important metadata is embedded right inside the individual files.

Of course, if you do not &lt;em&gt;like&lt;/em&gt; any of these applications because you find their user interfaces lacking, that&#039;s a different matter entirely…</description>
		<content:encoded><![CDATA[<p>Well, I don&#8217;t think that iPhoto or Aperture will be EOL&#8217;ed anytime soon, but if they are, you will still be able to use either application&#8217;s export functions to move your media into another application. What&#8217;s more, many competing programs allow importing existing databases from other applications, so the threat of lock-in almost becomes a non-issue.</p>
<p>As for keeping files in a database, both iPhoto and Aperture on the Mac use packages for their databases, and these do contain the unmodified original photos. If all else — including exporting from within the app — fails, you can still &#8220;Show Package Contents&#8221; for a database in the Finder and rescue the media that way.</p>
<p>Same for iTunes, by the way: its media library is just a folder tree, sorted by artists and albums, and the important metadata is embedded right inside the individual files.</p>
<p>Of course, if you do not <em>like</em> any of these applications because you find their user interfaces lacking, that&#8217;s a different matter entirely…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://bergs.biz/blog/2009/06/07/vista-picture-web-publishing-regression/#comment-20422</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Sun, 23 Aug 2009 08:56:35 +0000</pubDate>
		<guid isPermaLink="false">http://bergs.biz/blog/?p=78#comment-20422</guid>
		<description>@Jochen Wolters: It&#039;s not exactly &quot;fear of using software that manages files for you,&quot; but I simply don&#039;t want to depend on a particular piece of software.

What if some day this piece of software is no longer available or supported? Then all my efforts I put into it are lost. And this risk I simply don&#039;t wonna take.

Moreover, some pieces of software like this don&#039;t operate on an existing file tree, but they insist on importing files they &quot;administer&quot; into a proprietary &quot;database,&quot; so that I have two copies of them -- one is the original, unmodified file, the other one is the one in the database. I could delete the original copy, but what if the &quot;proprietary database&quot; is corrupt one day? Sometimes you can&#039;t (easily, if at all) extract individual files from such databases. Sometimes original files will be modified in some way, such as flattening folder paths, renaming files, modifying the file content (e. g. by embedding meta info), etc.

All this is simply not acceptable for me.</description>
		<content:encoded><![CDATA[<p>@Jochen Wolters: It&#8217;s not exactly &#8220;fear of using software that manages files for you,&#8221; but I simply don&#8217;t want to depend on a particular piece of software.</p>
<p>What if some day this piece of software is no longer available or supported? Then all my efforts I put into it are lost. And this risk I simply don&#8217;t wonna take.</p>
<p>Moreover, some pieces of software like this don&#8217;t operate on an existing file tree, but they insist on importing files they &#8220;administer&#8221; into a proprietary &#8220;database,&#8221; so that I have two copies of them &#8212; one is the original, unmodified file, the other one is the one in the database. I could delete the original copy, but what if the &#8220;proprietary database&#8221; is corrupt one day? Sometimes you can&#8217;t (easily, if at all) extract individual files from such databases. Sometimes original files will be modified in some way, such as flattening folder paths, renaming files, modifying the file content (e. g. by embedding meta info), etc.</p>
<p>All this is simply not acceptable for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jochen Wolters</title>
		<link>http://bergs.biz/blog/2009/06/07/vista-picture-web-publishing-regression/#comment-19415</link>
		<dc:creator>Jochen Wolters</dc:creator>
		<pubDate>Wed, 29 Jul 2009 23:49:40 +0000</pubDate>
		<guid isPermaLink="false">http://bergs.biz/blog/?p=78#comment-19415</guid>
		<description>I&#039;m sorry to hear that you had to go through all that trouble, Ralf, but, to be frank, you&#039;d run into a lot fewer problems like this one if you would overcome your  apparent fear of using software that manages files for you.

Had you used iPhoto (on OS X) or Picasa (on Windows), for example, you would have been done with resizing and uploading in a few minutes, instead of spending much more time and unnecessary effort like you apparently did.

In a blog post about note-taking software, I recently read that only programmers insist on managing media data on a file level, and I wholeheartedly agree with that sentiment: if it wasn&#039;t for Aperture, whose manual expressly reminds one not to mess around with the raw image files contained in Aperture&#039;s library, I&#039;d either have given up on digital photography or lost my mind. If I do, however, want to manage some files manually, I can easily export images from Aperture as needed.

The very fact that I do _not_ have to handle such media on the file level, and can instead resort to using extensive organizing features -- including keywords, EXIF data management, calendar filtering, and more -- lets me concentrate on what I really want to do, which is managing content, not containers.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sorry to hear that you had to go through all that trouble, Ralf, but, to be frank, you&#8217;d run into a lot fewer problems like this one if you would overcome your  apparent fear of using software that manages files for you.</p>
<p>Had you used iPhoto (on OS X) or Picasa (on Windows), for example, you would have been done with resizing and uploading in a few minutes, instead of spending much more time and unnecessary effort like you apparently did.</p>
<p>In a blog post about note-taking software, I recently read that only programmers insist on managing media data on a file level, and I wholeheartedly agree with that sentiment: if it wasn&#8217;t for Aperture, whose manual expressly reminds one not to mess around with the raw image files contained in Aperture&#8217;s library, I&#8217;d either have given up on digital photography or lost my mind. If I do, however, want to manage some files manually, I can easily export images from Aperture as needed.</p>
<p>The very fact that I do _not_ have to handle such media on the file level, and can instead resort to using extensive organizing features &#8212; including keywords, EXIF data management, calendar filtering, and more &#8212; lets me concentrate on what I really want to do, which is managing content, not containers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

