Can we access the 'selection' in the WidgetMessage: tm-edit-text-operation

[telumire]

Yes it’s possible, there is one in the example that comes with the plugin. It’s a bit complex tho, that’s why I used a simple button for the demo

EDIT: @Mark_S’s plugin does exactly that : https://talk.tiddlywiki.org/uploads/short-url/ws8eDb61s3eOmFxQ2VN68o31PzV.json

[fastfreddy]

Thanks for all the great suggestions everyone! I was able to use most of them to grab bits and pieces of code (like the plumber I am) and now have solution that is simple and works really well, from view mode. In the end, I found Dynannotate to be a bit of and overkill, and I instead based the solution off the context menu plugin.

I have modified a few things:
1- disable the check for selection (initially, the plugin deliberately does not work if there is text selected);
2- inserted a with a check for the control key (inspired by @saqimtiaz 's link context menu plugin). This way, you can still access the browser’s context menu for selections, if you wish, by pressing the control key. I may choose to inverse the logic, but for now, this is my preference;
3- added an option on the context menu that 1) creates a new tiddler from the text selection and 2) replaces the selection (text search and replace) with a link to the new tiddler, from view mode (this I thought would be much harded than it ended up being, inspired by this search and replace plugin)

(this code goes in $:/plugins/ahanniga/context-menu/ContextListener.js, but you need one more simple tiddler for the new menu item.)

            case "tm-new-tiddler":
                this.dispatchEvent({ type: "tm-new-tiddler", paramObject: {title: ""+selection+""}});
$tw.wiki.setText(targ,"text",null,text.replace(selection,"[["+selection+"]]"));
                break;

I’ll continue to play around but this seems to fit my needs.
One shortcoming noted so far is if the raw text has a line break that is not visible in view mode (or any other fancy wikitext rendering), the search&replace function will not find the selection in the text. I can probably live with that.

before:

after:

[TW_Tones]

Please share a working example if possible.

[fastfreddy]

on it; will do this evening; tried to package twice with Tinka and lost the plugin both times. Will try with @Mohammad packager.

[fastfreddy]

try this @TW_Tones (you will also need this plugin: https://context-menu-plugin.tiddlyhost.com)

plugin_fastfreddy_new-from-selection_v0.0.0_20220922.json (7.9 KB)

[TW_Tones]

Thanks it works well @fastfreddy, I had not used the context menu plugin before, its great. Such a menu could be the solution here Has anyone found a solution to title and button overflow on tiddlers? and expect it may work well with MCL Multi-column layout whose weakness in my view is titles/button competition for space.

Now also the answer to this topic is included. Thanks.

[Mohammad]

If you can manipulate the selection, then I think you can manipulate the text of target tiddler (the one from it you open context menu)

For example highlight selection!

[TW_Tones]

Yes also using freelink plugin as soon as you create the tiddler it will become a highlighted link, but it would be nice to have a operation, like edit-text-operations applied in the text field.

[arunnbabu81]

@Mohammad

If you can manipulate the selection, then I think you can manipulate the text of target tiddler (the one from it you open context menu)

For example highlight selection

@fastfreddy Can we then insert macros around selected text using this context menu. For example can we add sticky todos (stobot 's plug in) if we select a text and add the todo macro via context menu

[Mohammad]

@arunnbabu81

@fastfreddy Can we then insert macros around selected text using this context menu. For example can we add sticky todos (stobot 's plug in) if we select a text and add the todo macro via context menu

I believe this is possible then! So you can have an annotation tool!

[TW_Tones]

Of course dynannoate plugin does some of this already.

[arunnbabu81]

If it’s an yes, we could do many operations like that from the view mode itself

[fastfreddy]

absolutely @arunnbabu81, the code I pasted as you will see is quite simple (and only adds the wikitext characters for a link to the selection). You can mangle the selection above you wish as @Mohammad suggested, with the one caveat:

One shortcoming noted so far is if the raw text has a line break that is not visible in view mode (or any other fancy wikitext rendering), the search&replace function will not find the selection in the text. I can probably live with that.

Re: Sticky plugin, I think that would be almost trivial, yes, and a great idea

I also find @saqimtiaz approach to the link context menu to be a bit more modular for these kinds of enhancements, but the : https://context-menu-plugin.tiddlyhost.com plugin isn’t bad either if you are comfortable with javascript.

[fastfreddy]

@arunnbabu81 : here’s a minor update which provides two options (create new tiddler from selection, and make todo from selection).

I have added some error checking, type conversion, and the selected words are TitleCased for the new tiddler (using the [[selection|Selection]] text replacement).

You will also need the Stickies — lightweight todo system plugin for the new option.

same caveat: the selected text is from the rendered WikiText; the search-replace is done on the raw WikiText; if the two aren’t identical, the source tiddler replacement will not work.

plugin_fastfreddy_ContextMenuAddin_v0.0.1_20220922.json (9.7 KB)

[arunnbabu81]

@fastfreddy I tried to modify the code.

<<sticky "">>

This is the sticky todo macro.

• I was able to insert the macro only when I changed double-quotes to single quotes in the macro.
  But then the todo macro won’t work then. Is there any way solve this ?
• Also can we use a widget other than tm-new-tiddler because everytime I tried to insert the macro from the context menu, a new tiddler gets created which is not needed.

This was the mesage I had typed yesterday night before I slept off (was really busy at work yesterday) …when I woke up today , I saw that you have updated it…will check and message today when time permits. Thank you for the fast update.

[Mohammad]

@fastfreddy

with the one caveat:

Yes, this is very true, and it gets even worse if the content are produced from transclusion or some computation like a the output of $list widgets, macros, etc…

I just wondering if dynanotate has the same issues (@Mark_S).

[TW_Tones]

@fastfreddy

if the two aren’t identical, the source tiddler replacement will not work.

True, but if the selection is not found in the raw tiddler, this tells us it is sourced elsewhere.

• We could indicate somehow the selection is not in the raw tiddler?, and allow some actions, only if it is found, otherwise open a title or search?
  • Perhaps also consider when found more than once in the raw tiddler or elsewhere.
• In reality I think such a matter of fact, that what you select is not in the raw tiddler is something a regular user of tiddlywiki would be aware of. Often all they need to do is open a link and rename the tiddler to achieve the equivalent.
• We could get tricky and wrap code in a var that tells the context menu the official source tiddler if available, thus enabling search and replace in additional cases other than just when in the underlying raw tiddler.
• I have previously worked out a way to identify the “code tiddler” in which some wiki code exists, which may also help.
  • So a heading “that is in view”, that is in raw text of a transclude/code/macro we would use the code tiddler variable to find the source tiddler on which a search and replace can take place.
  • This would also be helpful to designers, highlight some text on screen and gain a link to the source tiddler.

[fastfreddy]

@Mohammad

I just wondering if dynanotate has the same issues (@Mark_S).

Out of the box, dynannotate seems to be able to highlight (either through annotation or the search result feature) regardless of origin (raw Wikitext or fancy macro/transclusions). It seems to capture the rendered wikitext and adds position-based overlays to the DOM as follows:

It does not seem to make changes/replacements to the underlying tiddler, but instead creates CSS class-based overlays based on relative position within the DOM object !?!

Interesting…and surprisingly capable… Will continue to investigate, but it may not provide insights if one wishes to change the underlying tiddler with a search/replace functionality…

[arunnbabu81]

@fastfreddy have you seen this context menu using wiki text by @Yaisog

Implementing a contextmenu with wikitext

Alrighty, after spending a few days fiddling with context menus (and definitely too much time playing around with CSS transition effects that were ultimately scrapped), I’m in a spot where I’m quite happy with how they turned out. After some refactoring there is not much code to it, and I even got submenus to work. [image] The $eventcatcher and macro are pretty much as above. The template for the popup also is not very complicated and mostly sets all the passed variables: \whitespace trim <…

[arunnbabu81]

Can it be modified to work with macro made by JanJo.

<<ToDo "" "" "">>

Will it by possible to do all basic wiki text formatting using like bold, underline, headings, code blocks with this menu.