TW Tones wrote:
>
> I was just reviewing your EditorMagic again and see how it can look up the 
> documentation on widgets, what a fantastic feature.
>

In deed! I think once people get the power of a (well working) EditorMagic, 
they'll wonder how they survived before it.
 

> When it comes to EditorMagic insertions;
>
>    - I can see that there is a bit of work to be done to populate it with 
>    useful insertions, kind of a sample and generalised syntax's for each 
>    widget. 
>
> I raise this because I would like to help, and wonder if they would be 
> better as separate tiddlers or an interface to read and edit them were 
> available to simplify.
>

Since you started by commenting on the *widget docs* tool, I'm guessing 
you're referrign to the *widget picker 
<http://editormagic.tiddlyspot.com/#EditorMagic%2FWidgetPicker>* tool that 
inserts the widget and its various parameters, and which currently fetches 
that data from a dictionary tiddler 
<http://editormagic.tiddlyspot.com/#EditorMagic%2FWidgetPicker%2Fdic>. Yes, 
I appreciate all the help I can get - thank you! - and, yeah, maybe it's 
better to have each "widget info" in a separate tiddler, I don't know. As 
you probably note, I've only sloppily filled in the parameter list for a 
few of them because it turns out to be... quite a lot of work.


>    - Lets call this the "syntax library" for tiddlywiki widgets and macros
>
> Sure! 

>
>    - I have long desired Tiddlywiki.com to have more generic full syntax 
>    examples I can copy to clipboard and use, a single syntax, you delete the 
>    parameters you don't need, or a few different ones when they are 
>    substantially different forms.
>
> Yes but for some I feel there are so many parameters that it might be more 
work to erase them than to type in the few you need (e.g the ButtonWidget 
<https://tiddlywiki.com/prerelease/#ButtonWidget>- mama mia!) 

>
>    - If we can agree on a standard that works with editor magic and on 
>    tiddlywiki.com the community could build them for the community. Then 
>    the latest up to date general syntax could be accessed from a plugin and 
>    feed into other solutions including learning editions of tiddlywiki and 
>    Editor Magic.
>
> A main idea with EditorMagic is that people can fill the popup with 
whatever they want, so the "standard" you refer to would rather be one that 
works with the/a widget picker tool :-) The current implementation for the 
widget picker is just a proposal, mostly to demo what EditorMagic can be 
used for.


Practical approach
>
> If we had an easy way to generate standalone syntax tiddlers that could be 
> submitted for addition to tiddlywiki.com by anyone, and a method on the 
> widget documentation to list any such syntax tiddlers inside the 
> documentation tiddler (perhaps a tag or equivalent field. This method allow 
> more rapid inclusion in to tiddlywiki.com with less oversight needed. A 
> simple export to json for all syntax widgets would allow you or anyone else 
> to harvest the syntax's.
>

I'm not sure I follow fully but it did strike me that it would be neat if 
the tiddlywiki.com docs had a defined format for e.g the parameters of 
widgets or other stuff, so one could automate this. A kind of docs api. E.g 
so one could fetch data by means of e.g a filter ( 
[fetch:fields[ButtonWidget]] ). I wouldn't hold my breath for this though 
;-)

I did experiment and discuss 
<https://groups.google.com/forum/#!topic/tiddlywiki/E6i2vu2Ht4c> a few ways 
to generate the widgets list because it is a shame to hard code this. It is 
currently generated based on the widgets found in the core code but there 
are inconsistencies.

A major thing for working with tiddlywiki.com is of course that any changes 
to that place is up to Jeremy.

<:-)

>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" 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/tiddlywiki/840f88fc-008f-4611-bb4d-939aace030b6o%40googlegroups.com.

Reply via email to