Tiddler Context Menu Plugin

[ahanniga]

I’ve created a plugin that adds some handy options in an extendable context menu. Hope it’s useful: https://context-menu-plugin.tiddlyhost.com/

[Mohammad]

WOW
This is amazing! Love it!

[saqimtiaz]

Very neat.

I would suggest deriving the menu content from tiddlers with a specific tag, where fields in the tiddlers provide the text (and potentially icon) and the text field of the tiddlers provides the actions to invoke. This makes it easier to customize without overriding plugin tiddlers, and allows users to easily share individual menu items as separate tiddlers.

The Links Context Menu plugin takes this approach for a context menu for tiddler links, so the two plugins could share menu entries.

Other suggestions: don’t trigger the context menu when there is an active selection to allow selecting text and using the default browser context menu, and/or allowing to override the activation of the contextmenu by holding a key (e.g. Ctrl).

[ahanniga]

Thank you Saq. Good suggestions. Showing the menu when text selected will be a bug … will fix.

[CodaCoder]

Very VERY nice. Kudos.

Saq’s suggestions are certainly worth applying.

Consider yourself “watched”

[Yaisog]

Both of these context menu plugins are really nice. That right mouse button is significantly underused in TW.

Do you think this could be done entirely in WikiText by using an $eventcatcher?

Have a nice day
Yaisog

[ahanniga]

Still learning - will checkout $eventcatcher. For sure an alternative menu configuration is needed… wikitext/tiddlers would be a better fit than JSON

[saqimtiaz]

@ahanniga

For sure an alternative menu configuration is needed… wikitext/tiddlers would be a better fit than JSON

You should be able to use the same approach as my plugin, which is to set a state tiddler in the context menu handler. The state tiddler is tied to a reveal widget which creates a popup for the menu. This popup transcludes tiddlers with a given tag.

The code is here. If you have any questions please do feel free to ask.

Another eventual improvement might be to look for a parent DOM node with a given CSS selector to which the event listener is added, rather than adding it to the parent DOM node, which might fail with view template customizations.

[StS]

Hello @ahanniga,
very nice

I tried to adapt “$:/plugins/ahanniga/context-menu/options” for my use:

{
	"context-menu": [ 
		  {
			  "name": "bearbeiten",
			  "icon": "$:/core/images/edit-button",
			  "action": "tm-edit-tiddler"
		  },
		  {
			  "name": "Toggle Fold",
			  "icon": "$:/core/images/fold-button",
			  "action": "tm-fold-tiddler"
		  },
		  {
			  "name": "Copy to Clipboard",
			  "icon": "$:/core/images/copy-clipboard",
			  "action": "tm-copy-to-clipboard"
		  },
			{
			  "name": "drucken",
			  "icon": "$:/core/images/print-button",
			  "action": "tm-print"
		  },
		{
			  "name": "schließen",
			  "icon": "$:/core/images/close-button",
			  "action": "tm-close-tiddler"
		  }
	  ]
  }
		

What did I wrong?

Thanks
Stefan

[ahanniga]

Hi Stefan,

This message requires an event object. I have got it working by adding an additional case statement to $:/plugins/ahanniga/context-menu/ContextListener.js

 case "tm-print":
	this.dispatchEvent({ type: "tm-print", event: event });
 break;

This is not ideal. I’m currently working on changing the configuration from JSON to tiddlers, so adding new options will be much more conventional and in-keeping with other plugins.

[StS]

@ahanniga

This is not ideal. I’m currently working on changing the configuration from JSON to tiddlers, so adding new options will be much more conventional and in-keeping with other plugins.

Thanks - I’m looking forward to the new plugin.

Regards
Stefan

[saqimtiaz]

To keep this thread focused on the plugin in question, I have moved discussion of alternative implementations with wikitext to a new thread:

Implementing a contextmenu with wikitext

I made a proof-of-concept for a flexible context menu that uses the $eventcatcher. It’s probably not (easily) doable as a plug-in as it touches a few templates. But not everything must be a plug-in and the templates that were changed are all custom in my wikis anyway. So, take it or leave it, but it can be done (and I will definitely use it to clean up all the buttons that litter my wikis). First, place the $eventcatcher. I tried to put it in the ViewTemplate, but there it was difficult to mak…

[ahanniga]

Thanks everyone for the feedback! I’ve updated the plugin so that:

• Configuration is now tiddler-based
• More menu options
• Sanitize inputs
• Optional separators
• If text is currently selected, thre default context menu is shown

https://context-menu-plugin.tiddlyhost.com/

Cheers, Aidan

[HistoryBuff]

Hi Aidan,

I think you context menu is a great idea. I was wondering if it might be possible to add custom commands to the menu such as open a certain tiddler, etc.

[ahanniga]

Hi HistoryBuff,

The context menu provides access to commands for the current tiddler. To open often-used tiddlers I’d recommend Mohammad’s favourites plugin which does exactly what you need.

[HistoryBuff]

Thanks. One more question: can this be made to work in edit mode with, say, formatting commands?

[StS]

Hello Aidan,

thanks for the new plugin - very nice

I activated the print option and saw, that all open tiddler are in the print-preview and will be printed with icons outside of the tiddler:

I’m using PrintRiver.

This is a very powerful tool and printing is, how it should be…

What configuration is needed to have this tool by default, when printing with context-menu?

Thanks
Stefan

[ahanniga]

Hi, will take a look.

[ahanniga]

In edit mode I think this will depend on the editor used and the type of content. There are dedicated buttons depending on whether you’re editing Wikitext or Markdown and these can be configured in the Control Panel (toolbars). There could be a use for a context menu but I can only think of save, delete and cancel being necessary (?)

Aidan