Ah ic. Yup these are reasonable assumptions. We can certainly do this
for admins. But how will we tell the difference between file-sharing
users versus Casual Collaborator users?
On Nov 21, 2006, at 3:43 PM, Matthew Eernisse wrote:
See inline, below.
Mimi Yin wrote:
By dropdown menus, do you mean the File/Edit menus? I wasn't aware
that we were doing that.
Maybe not File/Edit, since those are sitting in the browser window
already, but a menubar and menus with similar behavior/functionality.
I had just assumed if the endpoint is feature parity with Chandler,
eventually we'll have enough pieces of functionality that we'll
need to implement menus. It's a pretty low-cost piece of UI to
build, and if we can solve some other issues by building it sooner
rather than later, I think it's something worth thinking about.
This also applies to the idea of asking people to choose which UI
they want before they log in seems kind of clunky and
unnecessarily complicated. Why not just add/remove items in a
drop-down menu?
I think I'm not following 'add/remove' items in a drop-down menu.
Could you elaborate on that more? By items, do you mean shared
collections? Or do you mean, add and remove views from view
selector widget.
Ah, sorry for not explaining myself very clearly there. I mean
adding some admin-specific items into the menu for users logged in
with admin accounts, and removing those items for ordinary users.
So admin-level users would have items available in their menus that
give them access to the special admin sections of the app.
Hope that is clearer.
Thanks.
Matthew
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
