The so called filebrowser...
Posted: Sun Mar 06, 2011 5:16 pm
Hi,
Changing the filebrowser from a "file carussel" to a "file page" was a big step forward in useability.
But this filebrowser still has potential of improvement:
* it cannot handle directories -- only the contents of a single, job bound directory
* it cannot handle more than one screen full of files -- and not everyone uses a 16:9/ 24" widescreen monitor
* it shows icons, which costs a lot of screen space and does not provide more than the difference between
man and woman as information about the files contents.
* If one creates "too much" versions of a model, s/he has to move older files into an subdirectory, which in
turn cannot be seen or visited with the filebrowser.
Or in other words: _You have to move files out of the way of the filebrowser to keep it useable_ .
My suggestion would be: Why to invent the wheel a 12th time?
Just implement (or even use a ready-to-use example or library) old fashioned fileselector box for that job?
And as long as one either has to use a low resolution screeen to recognize the barely visible differences in
the icons of the models and only be able to handle a handful of files OR to use a high resolution screen,
which offers more space for the files of the "filebrowser page" but renders the icons beyond any visible
difference more subtle as the difference between the genders I would think of stop using icons at all.
Nameing the files with speaking name is up to the user than.
Only my two cent....your filebrowser may vary...
Best regards,
mcc
Changing the filebrowser from a "file carussel" to a "file page" was a big step forward in useability.
But this filebrowser still has potential of improvement:
* it cannot handle directories -- only the contents of a single, job bound directory
* it cannot handle more than one screen full of files -- and not everyone uses a 16:9/ 24" widescreen monitor
* it shows icons, which costs a lot of screen space and does not provide more than the difference between
man and woman as information about the files contents.
* If one creates "too much" versions of a model, s/he has to move older files into an subdirectory, which in
turn cannot be seen or visited with the filebrowser.
Or in other words: _You have to move files out of the way of the filebrowser to keep it useable_ .
My suggestion would be: Why to invent the wheel a 12th time?
Just implement (or even use a ready-to-use example or library) old fashioned fileselector box for that job?
And as long as one either has to use a low resolution screeen to recognize the barely visible differences in
the icons of the models and only be able to handle a handful of files OR to use a high resolution screen,
which offers more space for the files of the "filebrowser page" but renders the icons beyond any visible
difference more subtle as the difference between the genders I would think of stop using icons at all.
Nameing the files with speaking name is up to the user than.
Only my two cent....your filebrowser may vary...
Best regards,
mcc