Refactoring of Menus

[vmassol]

@surli

Usage of “shortcuts” terminology

I think the idea was that it was shortcut link to the extradoc tabs. The shortcuts.vm file says:

## Build the list of documents extras to display, if it does not exist (default).
## List format : ["ExtraAnchor",  "ExtraTabText", numberOfItems]

@surli

Here I’m just wondering if we want to keep that terminology in the future, or if we want to put everything in menus_content.vm.

Note that shortcuts.vm is used by 6-7 other templates (without using menus_content.vm), so it seems there’s a need for something more fine-grained than menus_content.vm.

Second note: Removing a vm is like breaking an API. Anyone who had a custom skin overriding it will get broken.

@surli

So to sum up:

1. Are you ok if we stop using “shortcuts” for talking about viewers, and to discard the shortcuts.vm unless we keep using it only for handling keyboard shortcuts?
2. Are you ok if we’re going to a solution with all menu items defined as UIX, meaning that an empty wiki wouldn’t have them?

For 1:

• I don’t think we can remove it but we could introduce a new vm and have shortcuts.vm call it.
• Indeed this template also defines the keyboard shortcuts which probably need to stay there or be moved to a keyboard_shortcuts.vm file.

For 2:

• I agree it would be nice to only have UIXPs and UIXs.
• We need XWiki to be usable for its basic features in the minimal distribution. If we have the docextra in the minimal distribution then the menu links to them should also be there IMO.
• One idea is to have UIXs which are implemented as templates (they can currently be implemented as wiki page or java components).
• Another idea is to introduce a feature we discussed in the past which is to have a special directory in xwiki (under WEB-INF probably) and if there are extensions there (in the form of XIP files probably), then XWiki would install them at first run. This would mean bundling minimal App extensions (extensions contributing wiki pages) in the minimal distribution.