rejetto forum

Software => HFS ~ HTTP File Server => Topic started by: rejetto on July 27, 2007, 08:36:14 PM

Title: usability proposal: vfs with no name
Post by: rejetto on July 27, 2007, 08:36:14 PM
I noticed many people don't understand why HFS saves automatically options but not the file system (vfs).
I also thought over a lot of people who don't need to play with more than 1 file systems.

What i consider doing in next version is
the first time
- you quit with an unsaved vfs
- hfs asks you if you want to see your files next time
- if you say yes, it doesn't ask for a file name, but automatically save the vfs to an hfs.vfs file (or in the registry if you save options to registry)

other times
- if you answered yes, it continues to automatically save vfs at quit without asking

You can always stop this madness by using "save file system". ;)

giving a name to a file is a job many people consider boring.
i think this should improve usability for basic users.
Title: Re: usability proposal: vfs with no name
Post by: radd on July 27, 2007, 09:44:03 PM
i agree with this suggestion.
i just want share, i have experienced my saved vfs broken, which i believed happen if i press cancel when hfs loading during start. it happens more than twice and that time i use build 108, but i couldnt test whether the same thing still happens now because hfs load too fast now..
what i like to highlight here, if the problem persist, user might find their saved vfs corrupt which will cause disappointments as they need to rearrange file, add comment and etc. what i do are by having to vfs and save it alternately as backup in case 1 of them corrupt. do u think necessary to have backup file?

--i will check whether vfs really broken because what i said earlier--
Title: Re: usability proposal: vfs with no name
Post by: Giant Eagle on July 27, 2007, 09:44:52 PM
Nice!
i think this should improve usability for basic users.

Thats for sure.

i agree with this suggestion.
i just want share, i have experienced my saved vfs broken, which i believed happen if i press cancel when hfs loading during start. it happens more than twice and that time i use build 108, but i couldnt test whether the same thing still happens now because hfs load too fast now..
what i like to highlight here, if the problem persist, user might find their saved vfs corrupt which will cause disappointments as they need to rearrange file, add comment and etc. what i do are by having to vfs and save it alternately as backup in case 1 of them corrupt. do u think necessary to have backup file?

--i will check whether vfs really broken because what i said earlier--

Hasnt that been fixed already?
Title: Re: usability proposal: vfs with no name
Post by: radd on July 27, 2007, 09:52:14 PM
heh? since when? no wonder i couldnt reproduced it. hehe.. sorry very much
Title: Re: usability proposal: vfs with no name
Post by: rejetto on July 28, 2007, 01:03:38 AM
please stay in topic :P
Title: Re: usability proposal: vfs with no name
Post by: MarkV on July 28, 2007, 02:58:21 AM
Agreed. 99% of the users have only one VFS and don't care for the name anyway.