js option: menu (shows a contextmenu) Proposal: default no contextmenu. But still add a contextmenu, maybe later.

[Klap-in]

Contextmenu

I wonder if I should readd the contextmenu again, but my impression is that there is a smaller group, that really appreciates this functionality. Give also your input with 👍 or 👎!

Here a first inventarisation, what was in the old contextmenu and ideas for the new one:

Default old structure (see /scripts/contextmenu.js, configurable per wiki via /scripts/contextmenu.local.js)

all 
	pg 
		view
		- <title>
		- revisions-link
		- ToC-preview

		edit  (only available if previewing in edit modus)
		- <title>
		- insert dw link
	ns
		view
		-<title>
		-search
if isadmin:
pg
	view
	-edit
	-create menu:
		- headpage
		- startpage
		- other page
	-more submenu:
		- acl manager
		- purge cache
		- exporthtml
		- exporttext
ns
	view 
	- new page
	- more submenu:
		- head page here
		- acl manager


if isauth
pg
	view
	- newpage here
	- edit page
	- more submenu:
		- headpage
		- purgecache
		- exporthtml

Proposals:

1. No default contextmenu. So if needed menu has to be added to options. (or globally added in the indexmenu config settings)
2. Remove contextmenu-entry for inserting links in preview during editing (I assume practical nobody knows this option)
3. Use a flat menustructure, no nested menu. (eventually only for export...)
4. no distinction between loggedin users and not-logged in users. (by adding the page/ns to the tree a basic auth check is already done so lot of options will work, and at the moment there is not yet a check for the remaining ones)
5. clean-up menu-entries

First suggestion for menu-entries, probably later much as possible options are removed.
e.g. no 'add start/headpages' anymore, as these can be added as 'normal' page.

Menu page (for e.g. current:pageid):

Editing modus (only if previewing during edit!!!!)

• Insert as DW link. (includes [[current:pageid]])

Pages

• Revisions (example.org/current:pageid?do=revisions)
• ToC example (create popup with ToC)
• Edit (example.org/current:pageid?do=edit)
• Create headpage (example.org/current:pageid:pageid?do=edit) (confusing?, maybe use headpage of indexmenu plugin?)
• Create startpage (example.org/current:pageid:start?do=edit)
• Create normal page (popup asks name: example.org/current:pageid:?do=edit)
• ACLs (example.org/current:pageid?do=admin&page=acl) Admin only
• Clear cache (example.org/current:pageid?purge=true)
• Export html (example.org/current:pageid?do=export_xhtml)
• Export text (example.org/current:pageid?do=export_raw)

Menu namespace (for e.g. current:)

Namespace

• Search... (popup asks search term, for seach in ns, example.org/searchterm_current?do=search&q=searchterm%20%40current)
• New page add... (popup asks name: example.org/current:?do=edit)
• Create headpage here (example.org/current:current?do=edit)
• ACLs (example.org/current?do=admin&page=acl) (wrong: focuses at 'page' current, not at ns!) Admin only

Note: if a node of namespace with a headpage (e.g. current:start), the old contextmenu showed page and namespace part of the menu

Please share your preference:
👍 thumbs up this post = keep the contextmenu feature
👎 thumb down this post = I do not use the contextmenu feature