Mat, I do understand the work in progress nature of this. I am just wondering if I can support the effort by commencing a parallel project that produces the content you need to feed into it later whist supporting a broader application.
I have being frustrated with poor and nonstandard syntax examples on Tiddlywiki.com and figure rather than build my own library of resources build a reusable one. Where I am thinking with the widgets is writing a set of widget template variations. These should be at home in tiddlywiki.com examples with a copy to clipboard as much as in your tool or someone instructional documentation. I am also keen to have a sidebar with such templates that I can drop in an editing session. To me I see that this is content that can be used in many ways. Thus I was proposing the development of such a database, with a view to you refactoring it if needed for editorMagic. I can see in the dictionary you have the name of the widget: widgetname and parameters including the widget close, I presume there is no multi-line widget layouts? So I wonder if I build a tiddler for each widget and one or more parameter variations, perhaps one with a multi-line layout and a field containing a single line layout then you could pick and choose what content you want to load into EditorMagic? Ideally you could just tap into a library of widgets that can be shared with other solutions and systematically improved by the community. Of course I can use all the tricks in the book to extract such widget content from tiddlywiki.com to build such a list. Yes, Saq is a machine of productivity. Regards Tony On Tuesday, July 21, 2020 at 9:37:22 AM UTC+10, Mat wrote: > > TonyM wrote: >> >> Perhaps you missed it, but I offered to start populating widget snipits >> for insertion with your instructions on how to. >> > > You did and that is excellent! There are two "angles" to that; one is the > construction of popup tools which can be somewhat intricate. But the other > is stuff like: > > http://editormagic2.tiddlyspot.com/#EditorMagic%2FWidgetPicker%2Fdic > > which clearly needs a lot of work. BUT it is too early to do this because > Saq (or even I) might come up with some approach that is better than using > such a dictionary. That specific dictionary is currently intended to stamp > a widget call with all parameters. A better approach might be to automate > what the parameters are, perhaps by scraping them from the widget > definitions. Or maybe that's a bad approach, I hope Saq can tell :-) > > Love your work, this is seriously exciting. >> > > Yes it certainly is! It is somewhat frustrating for me that it would be > totally impossible without Saq, but we're (all) really lucky he's both so > knowledgeable and so generous. > > <:-) > -- 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/c82df590-9e27-4eb4-88c6-c7f3cc21debfo%40googlegroups.com.
