[Cosmo] UI/Design Issues for Cosmo
priscilla at osafoundation.org
Tue Feb 7 11:08:29 PST 2006
Here are some current UI/Design issues for Cosmo:
(Note: Most items on this list a is probably not going to make the
next release, but we will work through some solutions for the
upcoming 0.3 release)
+ Need a confirm on deleting users.
person?' or need to come up with a message if people are using a
+ 'About' links should open to a new window, not replace the console.
* If you're going to open a new window, open a new window.
*Is there a browser issues with this request? For people
accessing the UI purely through terminal, is it possible to have a
warning message that tells the user you are about to delete a user,
such as, "Are you sure you want to delete this person? (Y/N)
+ Language used in creating passwords need to be more clear when
creating new user.
* I think there's a bug when the error appears
* Does it check for a valid email address–future release?
* 'Your password must be x characters long and include blah.'
* Feedback for required fields?
* Do we want more error checking feedback?
* For regular users creating an account: Do we want to tell
people that they need to enter home/username into the path field of
their accounts dialog in Chandler in order for sharing to work? (ie.
copy and paste this text into the path field of your accounts dialog)
+ Welcome message when you first log in.
*Do you need the 'Welcome' message? Why not just go to 'Users'
console when you first log in, have the 'Welcome' message at the top.
Then after clicking around, eliminate the 'Welcome' message when you
click back to the 'Users' console page?
Eliminate the page when clicking on the logo, and send it back to the
first page you seen when you're logged in.
* There's a link that doesn't link? 'Welcome to the Cosmo
sharing server installed at cosmo-test.osafoundation.org!' didn't
they just install it? Why do you need to have them link back?
* What about linking to the Cosmo landing page instead??
+ Non Administrator
* State 'no' in the Admin field?
* Should we provide more visual feedback for the root user? just
to indicate that it's different (ie. can't delete it and doesn't have
a home directory). I'm wondering if it belongs in that table at all.
* Perhaps the a different background color for Non Administrator
* Consistent breadcrumb trail. Either 'HomeDirectories' is in the
bold or add to the bread-crumb trial.
* I think there were also some problems with the "selection
state" of users/home directories/server status. (I think only Users
worked). Will there there be subdirectories ie. HomeDirectories?
* It's especially confusing when navigating to Home
Directories...because the top-level Home Directories page looks
+ Ticket & Properties
* Home Directory pages for each User account...So one question
is: Are Tickets and Properties children of each account? OR Do they
exist independently of each account? And if so, what does that mean?
* Actually should Tickets and Properties be attached to a
particular sub-directory/collection of content?
* We can also maybe tweak the spacing between the Contents/
Tickets and Properties...so that the titles are more clearly
associated with the tables below.
+ Should New Ticket can be in the body of the table, as the first row?
* Can you create new Properties? And new Content directories as
* Perhaps there should be a [new] link in the far right to the
heading 'Tickets'. – Creating new ticket should be in a new dialogue
+ Log in User Name & Password should be consistent for all applications.
* Scooby currently is ID: root and PW: password
* Cosmo currently is ID: root and PW: cosmo
* Let's just keep things consistent and keep a professional front
+ May want to have the 'Create New User' on a separate pane.
*As the list may become longer, you don't want the admin to
scroll down below the list of current users just to add a new user.
* Perhaps an expandable box at the top? Or a dialogue box. Let's
revisit this issue for a later release.
+ Creating new user
* Need to check for valid email address
+ Is Home Directories a file like system?
* We may want to reformat the directory browser to behave either
like an OS file manager – or at least be similar to an apache
directory listing, if its hierarchal in nature. I also do not know
what use the directory browser has, but this may more have to do with
understanding the purpose of tickets and properties.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cosmo