On Tue, Aug 11, 2009 at 6:18 PM, Ecaterina Valica<valicac(a)gmail.com> wrote:
I think we
should rename "Actions" back to "More Actions" since the
second is more common (I can think of gmail for example).
i'm ok with that.
I would also like to have "Create" instead of the "Add" action. You
can *add
* comments and tags, but I think it's more appropriate to *create* pages.
Yes create is better than "Add".
1. We need to decide the way we handle the actions we
are able to do
(depending on the rights we have): enable/disable them or hide them.
Why do we keep the "view" entry ?
I personally use "edit" to see the source of a page, may be others do the
same.
Anyway it's still useful to people without edit rights, in this case
we could keep "edit" activated and display the source with a message
saying something like "You need to login to edit this page, etc" or
"You're not allowed to edit this page" depending on the situation.
I was thinking with Marta and G, would it be ok to add "History" and
"Information" to the "View" submenu? Something like
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Skin20Menu/vie…
Information in this case has been rename in "Related Pages".
2. You can select to have an simple or advanced
menu (View and Edit
submenus
affected)
I wouldn't like that we use a tab layout for buttons that are actually
not tabs, for example "view" and "edit" in simple mode.
In simple mode "view" and "edit" are not buttons, but actually tabs,
you
change the view (tab) from one action to another, they aren't form buttons.
Right they aren't form buttons, they are links. They aren't actually
tabs since the view and edit layouts are different.
If I imagine the menu proposal in the skin 2.0 proposal I can get that
using the same layout for content actions (view, edit) and
meta-actions (comments, attachments) would look nice but IMO it's not
logical. For example "Export" and "More Action" are not only about
the
content of the page, but that's how it would look like.
The menu must
be revamped but I'd prefer that we stick to the dropdown
layout since it allows:
- to mix single buttons and dropdown lists
in my opinion is the same thing, just the aligment (horizontally,
vertically) is different. The problems with dropdowns I understood that it's
not well supported if you don't have JS activated, and also dropdowns can
block some of the page content.
Would your proposal be working without JS ?
The advantage of the dropdown is when you have many
items in the menu - but
it's not really the case and anyway menus that are very crowded are hard to
use.
With icons and categories I don't find that having a lot of items is a
problem, I also think that "More actions" could end up quite crowded.
Another thing is that using this kind of menu, you
integrate the tabs in
Edit (Wiki, WYSYWIG, Objects ...) with the menu, instead of having the
panel. This way you give an unique access point to the editing.
- to use icons more easily
in the mockups icons are not presented, but I don't see how the dropdown
menu can have a better support for icons than then horizontal menu. it's the
same thing, we could have also icons in this kind of menu.
- to create categories more easily (for example
in "Actions")
you can have categories also in horizontal menus.
I'm not saying that you can't, I'm saying that being able to use more
space (at least AFAICS) with a vertical layout makes things easier.
Thanks,
JV.