This is what I have in my custom skin:

Edit:
 Wiki
 WYSIWYG
 Form
 Objects

Add:
 New comment
 New attachment
 New subpage
 New space

Show:
 Code
 Comments
 Attachments
 History

Print:
 PDF
 Preview

Admin:
 Delete
 Rename
 Edit class
 Page rights
 Space rights
 Space prefs

What you can see in each menu of course depends on mode
(basic/advanced) and access level, with the admin menu changing the
most if you don't have admin privileges.

I prefer the Admin link by the login, actually.. and the tabbed panels
on that page allow easy flipping between space & global prefs.

*shrug* this works, and was a happy medium between the old menus and
the 1.0 menus.  I'm not sure a "Space" menu makes a lot of sense from
an end user perspective.





On 10/9/07, Jean-Vincent Drean <[EMAIL PROTECTED]> wrote:
> 2007/10/9, Vincent Massol <[EMAIL PROTECTED]>:
> > Hi JV,
> >
> > Great that you're working on this.
> >
> > I've looked at the design page and I have some comment (BTW why is
> > the status set to dormant, looks active to me ;)):
>
> Yep.
>
> > * I'd put SPACE as a top level menu instead of WATCH so that there's
> > consistency on actions for Pages and Spaces
> > * I'd move Watch Page to the PAGE menu
> > * I'd move Print to the PAGE menu (since it's a Page action)
> >
> > Basically I'd move all page actions to the PAGE menu and all SPACE
> > actions to the SPACE menu. If we want one then we could add entries
> > like Rename, Delete, Copy, Export as PDF, Export as RTF, etc.
>
> +1, I've updated the proposal (proposal 2) :
>
> http://www.xwiki.org/xwiki/bin/view/Design/Topmenurefactoring
>
> > * We need to make the menus very simple in the simple mode so we need
> > 2 proposals: one for the simple mode and one for the advanced mode.
> > Also we should only display menu entries if the user has the right
> > for executing the action.
>
> Sure, basic vs. advanced will have to be discussed when we'll have
> found a consensus on the menu. Obviously we must keep the current
> behavior on righs check.
>
> > * I'm not sure about the Administration menu since it duplicates the
> > Administration button. I think I'd rather we modify the
> > Administration screen to add more stuff. In any case we need
> > something consistent for the admin part.
>
> The idea here was to remove the administration link in the header to
> keep it only in the top bar. It allow the user to chose in one click
> what he want's to administrate, current space or the entire wiki.
>
> > WDYT?
> >
> > Thanks
> > -Vincent
> >
> > On Oct 9, 2007, at 7:37 AM, Jean-Vincent Drean wrote:
> >
> > > Hi XWikiers!
> > >
> > > We currently have features planned for 1.2M2 with a common point : the
> > > xwiki top menu.
> > >
> > > Features :
> > > - New space admin UI : http://jira.xwiki.org/jira/browse/XWIKI-1780
> > > [incomplete jira issue]
> > > - Email notifications (aka watchlist) :
> > > http://jira.xwiki.org/jira/browse/XWIKI-268
> > > - RSS for spaces/pages : http://jira.xwiki.org/jira/browse/XWIKI-448
> > > - Improve Admin.WebHome : http://jira.xwiki.org/jira/browse/XE-14
> > > [I'll write later about this one]
> > >
> > > To address needs from those features we'll have to add entries in the
> > > top menu without breaking our "800x600 users" compatibility. We
> > > currently run out of place in this menu, I've made a proposal of
> > > refactoring here :
> > >
> > > http://www.xwiki.org/xwiki/bin/view/Design/Topmenurefactoring
> > >
> > > WDYT ?
> > >
> > > JV.
> > > _______________________________________________
> > > devs mailing list
> > > [email protected]
> > > http://lists.xwiki.org/mailman/listinfo/devs
> >
> > _______________________________________________
> > devs mailing list
> > [email protected]
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>


-- 
'Waste of a good apple' -Samwise Gamgee
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to