<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<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: UI Changes in Jungle Disk 2.0</title>
	<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/</link>
	<description>Reliable online storage powered by Amazon S3</description>
	<pubDate>Sun, 07 Sep 2008 18:49:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Peter G</title>
		<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-945</link>
		<dc:creator>Peter G</dc:creator>
		<pubDate>Sat, 09 Aug 2008 20:27:45 +0000</pubDate>
		<guid>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-945</guid>
		<description>To JD:
Nice product.  I'm running first backups today.  A bit slow, but that's about my pipe, not the product.

To John &#38; Mark:
I've used a program (XYZService?) that presents *.exe files as a service.  Don't know if it would work here, but is worth a look - though JD should offer a run-as-service option.</description>
		<content:encoded><![CDATA[<p>To JD:<br />
Nice product.  I&#8217;m running first backups today.  A bit slow, but that&#8217;s about my pipe, not the product.</p>
<p>To John &amp; Mark:<br />
I&#8217;ve used a program (XYZService?) that presents *.exe files as a service.  Don&#8217;t know if it would work here, but is worth a look - though JD should offer a run-as-service option.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Perry</title>
		<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-874</link>
		<dc:creator>Perry</dc:creator>
		<pubDate>Thu, 10 Jul 2008 01:49:53 +0000</pubDate>
		<guid>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-874</guid>
		<description>When will we get the "run as service" feature. Have been waiting for this for years. Can't use this without this feature because I want this to run from our backup server. I can't comprehend how such a basic feature is still not implemented.</description>
		<content:encoded><![CDATA[<p>When will we get the &#8220;run as service&#8221; feature. Have been waiting for this for years. Can&#8217;t use this without this feature because I want this to run from our backup server. I can&#8217;t comprehend how such a basic feature is still not implemented.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-791</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Mon, 09 Jun 2008 16:17:13 +0000</pubDate>
		<guid>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-791</guid>
		<description>RUN AS A SERVICE please!!
My backups are useless, they never run based on scheduled task.
All is well in logs, the user and pw are correct, but they never fire.
I have gigs of data to backup, without a service this won't work on a server!  Can't use whack solutions like firedaemon

Come on, please, run as service is standard in the industry for serious win32/64 software.</description>
		<content:encoded><![CDATA[<p>RUN AS A SERVICE please!!<br />
My backups are useless, they never run based on scheduled task.<br />
All is well in logs, the user and pw are correct, but they never fire.<br />
I have gigs of data to backup, without a service this won&#8217;t work on a server!  Can&#8217;t use whack solutions like firedaemon</p>
<p>Come on, please, run as service is standard in the industry for serious win32/64 software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jungle Disk &#187; Blog Archive &#187; Jungle Disk 2.0 Beta Released!</title>
		<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-647</link>
		<dc:creator>Jungle Disk &#187; Blog Archive &#187; Jungle Disk 2.0 Beta Released!</dc:creator>
		<pubDate>Fri, 02 May 2008 21:47:09 +0000</pubDate>
		<guid>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-647</guid>
		<description>[...] engine and user interface for Jungle Disk. We now support multiple bucket types, there is an entirely new user interface including a brand new backup selection interface, and a whole host of new features including [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] engine and user interface for Jungle Disk. We now support multiple bucket types, there is an entirely new user interface including a brand new backup selection interface, and a whole host of new features including [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jungle Dave</title>
		<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-493</link>
		<dc:creator>Jungle Dave</dc:creator>
		<pubDate>Fri, 21 Mar 2008 12:50:28 +0000</pubDate>
		<guid>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-493</guid>
		<description>@John - lots of good stuff in there. Sync, Service support, and continuous backup are being looked at post-2.0. Configuration got a major revamp in 2.0, I think you'll be pleased. 
We're offering more previous version options, although not quite the TM style. We'll also be rolling out a more TM-style "point in time" look at your previous versions, although probably not in the first 2.0 release.</description>
		<content:encoded><![CDATA[<p>@John - lots of good stuff in there. Sync, Service support, and continuous backup are being looked at post-2.0. Configuration got a major revamp in 2.0, I think you&#8217;ll be pleased.<br />
We&#8217;re offering more previous version options, although not quite the TM style. We&#8217;ll also be rolling out a more TM-style &#8220;point in time&#8221; look at your previous versions, although probably not in the first 2.0 release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Rothlisberger</title>
		<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-490</link>
		<dc:creator>John Rothlisberger</dc:creator>
		<pubDate>Fri, 21 Mar 2008 03:31:33 +0000</pubDate>
		<guid>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-490</guid>
		<description>Hi there,

I love Jungle Disk. Comments in no particular order:

- I agree with the comment about bloat. I am amazed at how lean JD is, and I place high value on that.

- I also agree fully with the author's comment about users using JD for one thing or the other. I use it for backup only.

- I think "synchronisation while keeping previous versions and deleted items" would be very useful; i.e. let me have 2 or more computers synchronised, while keeping the online version, while keeping previous versions and deleted items. Does that make sense? Dropbox is an example of this.

- Make JD run as a service (separate the engine from the GUI which is only needed for configuration and monitoring). This would also get rid of the requirement for "run as administrator" for the VSS stuff to work (which is a terrible hack).

- Make configuration more resilient. Currently I get "configuration can't be updated because there is a job running". It should be able to apply changes which would take effect "next time".

- Instead of scheduled backups, which on my current backup set takes almost six minutes just to troll through everything to detect changes, is it possible to "notice changes" and back them up? i.e. something like continuous backup. If I'm working on a document, it would be handy to keep the history of changes as I'm working on it (i.e. every time I hit save).

- Is it worth implementing a more "intelligent" way of getting rid of previous versions? As an example, I think Apple's Time Machine keeps every hour for a week, then every day after that for a month, then every month for a year, or something like that (granular for recent stuff, less and less granular as time progresses). Would need to think about all the use-cases for this, to make sure this wouldn't impact anyone.

- Is it possible to implement something like the rsync method of using hard links to represent point-in-time snapshots of what the filesystem looked like at any given moment?

That's all I can think of at present. Thanks for a fabulous little program, and I look forward to version 2.0. Am happy to beta test if needed. Oh, and email me if you want clarification on any of the above.

Cheers!</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>I love Jungle Disk. Comments in no particular order:</p>
<p>- I agree with the comment about bloat. I am amazed at how lean JD is, and I place high value on that.</p>
<p>- I also agree fully with the author&#8217;s comment about users using JD for one thing or the other. I use it for backup only.</p>
<p>- I think &#8220;synchronisation while keeping previous versions and deleted items&#8221; would be very useful; i.e. let me have 2 or more computers synchronised, while keeping the online version, while keeping previous versions and deleted items. Does that make sense? Dropbox is an example of this.</p>
<p>- Make JD run as a service (separate the engine from the GUI which is only needed for configuration and monitoring). This would also get rid of the requirement for &#8220;run as administrator&#8221; for the VSS stuff to work (which is a terrible hack).</p>
<p>- Make configuration more resilient. Currently I get &#8220;configuration can&#8217;t be updated because there is a job running&#8221;. It should be able to apply changes which would take effect &#8220;next time&#8221;.</p>
<p>- Instead of scheduled backups, which on my current backup set takes almost six minutes just to troll through everything to detect changes, is it possible to &#8220;notice changes&#8221; and back them up? i.e. something like continuous backup. If I&#8217;m working on a document, it would be handy to keep the history of changes as I&#8217;m working on it (i.e. every time I hit save).</p>
<p>- Is it worth implementing a more &#8220;intelligent&#8221; way of getting rid of previous versions? As an example, I think Apple&#8217;s Time Machine keeps every hour for a week, then every day after that for a month, then every month for a year, or something like that (granular for recent stuff, less and less granular as time progresses). Would need to think about all the use-cases for this, to make sure this wouldn&#8217;t impact anyone.</p>
<p>- Is it possible to implement something like the rsync method of using hard links to represent point-in-time snapshots of what the filesystem looked like at any given moment?</p>
<p>That&#8217;s all I can think of at present. Thanks for a fabulous little program, and I look forward to version 2.0. Am happy to beta test if needed. Oh, and email me if you want clarification on any of the above.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jungle Disk &#187; Blog Archive &#187; What do you backup?</title>
		<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-483</link>
		<dc:creator>Jungle Disk &#187; Blog Archive &#187; What do you backup?</dc:creator>
		<pubDate>Tue, 18 Mar 2008 16:08:48 +0000</pubDate>
		<guid>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-483</guid>
		<description>[...] we mentioned in the UI redesign blog post, the user interface for configuring automatic backups is getting a major overhaul in Jungle Disk [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] we mentioned in the UI redesign blog post, the user interface for configuring automatic backups is getting a major overhaul in Jungle Disk [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phurge</title>
		<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-452</link>
		<dc:creator>Phurge</dc:creator>
		<pubDate>Mon, 03 Mar 2008 01:42:52 +0000</pubDate>
		<guid>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-452</guid>
		<description>I think the client is ok. It could do with a little "prettying up" but not at the expense of functionality please.

Re the web interface, keep it simple html. Please none of this awful &#38; often buggy flash/ajax/java etc.</description>
		<content:encoded><![CDATA[<p>I think the client is ok. It could do with a little &#8220;prettying up&#8221; but not at the expense of functionality please.</p>
<p>Re the web interface, keep it simple html. Please none of this awful &amp; often buggy flash/ajax/java etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-446</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Wed, 27 Feb 2008 16:02:31 +0000</pubDate>
		<guid>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-446</guid>
		<description>Glad to hear that you are redesigning the UI.  On the Mac at least, this looks like a piece of software from the 90's - and having a good designer on board familiar with Mac apps would go a long way.</description>
		<content:encoded><![CDATA[<p>Glad to hear that you are redesigning the UI.  On the Mac at least, this looks like a piece of software from the 90&#8217;s - and having a good designer on board familiar with Mac apps would go a long way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jungle Dave</title>
		<link>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-440</link>
		<dc:creator>Jungle Dave</dc:creator>
		<pubDate>Mon, 25 Feb 2008 21:44:59 +0000</pubDate>
		<guid>http://blog.jungledisk.com/2008/02/25/ui-changes-in-jungle-disk-20/#comment-440</guid>
		<description>We're certainly mindful of the footprint and want to keep it light-weight as possible. A lot of the reworking of the UI is about allowing us to do that, while still being able to add highly requested features.</description>
		<content:encoded><![CDATA[<p>We&#8217;re certainly mindful of the footprint and want to keep it light-weight as possible. A lot of the reworking of the UI is about allowing us to do that, while still being able to add highly requested features.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.563 seconds -->
