Suggestion for Progress Bar

by **mollodp** on Sat Sep 22, 2007 5:18 pm

I think a better UI design would be to move the status bar for upload/downloads to take the entire bottom of the program window.
Yes you can resize the left hand pane and see your whole filename, but this is a mess. Go with what filezilla has, all the way across the bottom, and showing what is queued in either directrion.

I just started using this today, overall looks very good.

Seems like some long lag for bucket explorer to show my local directory structures.
I also reccomend the add of some sort of refresh button for the local directory structure for when folders are renamedi n explorer during a filebucket session.

nice work.

by **brian** on Sat Sep 22, 2007 5:41 pm

From what I've been reading, I think a lot of great changes are going to be made already in this September release. Hopefully the queue organization improvements are released soon. Perhaps if you want to better promote your app you should start an opt-in mailing list so you can mail out whenever updates are made.

Personally, I haven't experienced any lag with my local directories and I have 7 drives hooked into my setup.

Brian

by **saurabh** on Sat Sep 22, 2007 10:15 pm

mollodp & Brian,

Thanks for the feedback. The "queue" & "progress indicator" are not changing in Sept release.

mollodp, the status bar is "clickable". That should show you the history, and FULL NAMES of the files without changing the left hand pane. Check that status bar and let us know if you still think we need file zilla style progress indicator? We want to add the "queue" features in Oct/Nov release and we can add the new style's progress indicator if you strongly feel that clickable status history is not good enough.

What's changing in Sept version for uploads is the following:

In the current prod release, when you try to upload new files, we don't create a collection of the local files and start uploading the files as soon as we read the first file, but we do create a list of all the files which are already present in a bucket and check their hash to prevent uploading same file again. This takes some time before the first file is uploaded if the bucket has too many files. So, we are changing this behaviour in Sept release and we will not create a collection on either side (local or what's available on s3). This should avoid the delays when a new transfer request is initiated.

Again, thanks for the feedback.

Saurabh