Calling it an "algo" was a bit pretentious of me. Upon inspection, the macros are just extracted by:
[tag[$:/tags/Macro]search[\define]get[text]splitregexp[\n]removeprefix[\define]trim[]prefix<em-fragment>] and the widgets were indeed a static list. I did some experiments earlier to generate them dynamically from the core (which is preferable) but they are currently a plain list. Anyway, are you saying filters like the above should be in a separate field? <:-) On Saturday, July 18, 2020 at 7:11:05 PM UTC+2, Mat wrote: > > Aha, a field, that's an interesting idea. So this should be used both in > the tools local code and in the /body/editor? > > Do consider that [all[tiddlers]prefix<fragment>.. is not relevant for > anything but tiddler titles though. For e.g macros, at least in the current > macro picker incarnation, the macro names are "calculated" in the tool (i.e > extracted by going through all $:/tags/Macro tiddlers). Basically the same > for widget names. My point is that at detection code stage (presumably in > /body/editor) these things are unknown, except for tiddler titles and > unless we calculate everything already there or have the macro and widget > lists hard coded. > > ...possibly the full algo to generate "the list of whatever items" could > be put in a field? > > <:-) > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/191c267d-9768-4299-8d7d-cd9486c435e7o%40googlegroups.com.
