Re: GtkFileChooser API work [getting OT]

On Wed, 2003-09-03 at 11:09, iain wrote:
> if given the chance I'd think .gnome-cd is much more understandable than
> .etc/gnome-cd, given that I first of all have to go through the process
> of thinking "What the buck does .etc mean?"[1]

I think most users would understand a .settings/gnome-cd too.  That sure
would clean up the home directory, especially for users who view their
home directories over samble.

> >  If the user wants to look at them, its a far sight better than
> > filling the home directory with hundreds of individual hidden files
> > which are equally incomprehensible to people who dont know what "etc"
> > means.
> Then why don't we name them .a, .b, .c, .d, and so on?
> Afterall, people aren't supposed to see them, so why waste valuable
> diskspace on multiple letter names when one character will do?

Whatever.  The original poster is still correct in this point.

> iain
> [1] Incidently what the buck does /etc mean? And /var for that
> matter...oh yeah, and /usr

What does C:\Windows\System mean?  C:\windows\ini?  None of that really
matters because users learn the basic meaning of these folders as they
user the computer.  Granted Program Files makes somewhat more sense to a
user than /bin.  However, as we progress in user interfaces, in many
respects the underlying file system should not matter to most users. 
Take Mac OS users, for example. They have /usr, /etc, and /dev.  But
users most of the time (except for those that wish it) never deal with
that.  Instead they deal with /Applications.  Similarly in Linux with
vfolders on the desktop, many users need not ever deal with these
things.  for these users, taking away a lot of the .files in the home
directory would be a real improvement.

Michael L Torrie <torriem chem byu edu>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]