@Saq http://editormagic2.tiddlyspot.com/
First, unless you object, I will hereon refer to the end user popup content templates as "popup tools" or, if the context allows, just "tools". And we can now call the /_Popup tiddler simply "the popup". The popup is now fully reworked. It has two groups of variables. See if you think any of them should be moved upstreams into /body/editor. It feels like the popup ought not have anything to do with the state tiddler. BTW, the editedTiddler variable refers to the viewtemplate tiddler of a tiddler being edited; in our case it'd be "RikerIpsum", and this variable is used in e.g transclude tools. Changing variable names is not as obvious as I thought: The system variables should be prefixed with em-. But IMO variables that the user is in direct contact with should be as friendly as possible. For example, when he creates a popup tool I think it is better if he creates the "trigger" field as opposed to the "em-trigger" field. Yes/no? And "fragment"... I guess it could be changed into "nameprefix" or "em-nameprefix" but I'm not sure that is more informative. It must not be "titleprefix" because it is not always titles.) 3) The "false fragment problem" i.e that <$xxxx or <<xxxx triggers the popup: > [...] leave it alone for now, but be prepared to have to deal with it. > OK. .... Q's for you 1) The styling you've put in $:/plugins/EditorMagic/styles - mess up e.g buttons inside the popup (e.g the 100% width). Were these styles added to e.g harmonize with your floating editor tools, or why were they added? 2) Merely stepping with the arrows is not sufficient to trigger anything. Eg, if it says <$ it is not merely enough to arrow ones way to after to $ to fire popup. It would be nice if it were, because currently one needs to e.g insert some character and delete it to trigger the popup. Do arrow keys not fire actions like other keys? 3) The recursive macro and what it solves: > We want to test all definition tiddlers for matches, and at the end decide > what to do. > I have this nagging feeling it could be made simpler than with the recursive macro by using some kind of external state value that is changed for each match. Maybe each match could append the title to a list. At the end we just extract the first title? I actually like recursions (except their binary behaviour to fully work or absolutely not ;-) but because it is part of the wikitext I feel it is advantageous to keep it as simple as possible for others reading it. <:-) -- 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/73bebfb6-bf22-4fd0-8119-470a51ce2dafo%40googlegroups.com.
