I must say: This is just so much fun! Right. This is actually the same bug as the one we discussed before [...] >
Good. > Regarding different trigger-end options: I have to admit I am not familiar > with your code beyond what was in the simplified demo at the beginning of > this thread. I think your approach should be OK though I am not clear on > workflow, do users get to choose which ending to use? Anyway, best way to > figure it out is to try it. > I'll detail my various findings below, but yes; one of the main ideas is that users should fairly easily be able to create their own popup tools. Having now tried it I'm finding it is not an issue. But I'm curious: even for pre-made popup tools, the system will still have to know if <$widget foo> is closed or not. So how is the fragment end detected? In the EditorMagic/_Popup it is defined to be the "whole string" after the trigger until a trigger-end... but it seems your code defines the fragment as after trigger until caret. Is that correct? ...in which case I should remove the trigger-end check... but then, "until caret" can mean the *rest of the whole tiddler text*...? > Personally I think autocompletion makes sense for some things, like links. > For others, like widgets, just detecting which widget the user is trying to > type and showing the relevant docs in the popup might be a better approach. > IMO widgets are so very ubiquitous so their use should be simplified as much as possible. Plus they look scary for newcomers so a popup could be a kind of wizard. I also think it were better if I could make a popup tool where there isn't such separation between docs and picking - i.e, the current popup docs approach is an iframed tw.com but this is just a compromise and it brings with it a lot of redundant/distracting stuff and it is not ideally presented. A more useful popup would perhaps show pickable parameters for each widget and info about the parameter. E.g each listed widget title could be a revealwidget to show further stuff. (Of course how to extract or rewrite the docs to fit that is a totally different matter.) I could also imagine a popup triggered by a specific character, say "|" > that lets you choose to insert a transclusion, link or image etc.... though > this might be more on my mind because of the work on the floating editor > toolbar and the non-selection related buttons. > Definitely a great idea. In the (full) EditorMagic demo <http://editormagic.tiddlyspot.com/> I use "??tr" and "??dr" for transclusions where the latter opens a drawing canvas which I think is pretty neat. (In native TW, to spontaneously create and insert a sketch in the middle of a tiddler is totally impractical.) But your idea to use a common trigger, possibly even a single character as you say, is more elegant than my cryptic abbreviations. BTW, is there something more that can be done to align EditorMagic with your floating editor toolbar? There's obvious conceptual overlap so it makes sense if they harmonize where possible. If I understand your floating editor toolbar right it is currently only triggered by selecting text. It would be cool if, for example, the user can select text which, if it is some particular string, triggers docs or something else for it that string. For example if the user, in the middle of a listwidget, selects the string $list he gets info about this, or selecting a word in some arbitrary text gives e.g a translation. (BTW, needless to say, if there's anything in what I've created that you can use for your things I'd be incredibly flattered.) ... OK, here's the current status: http://editormagic2.tiddlyspot.com/ (never mind the mini "quicklinks" popup unless you use the SideEditor) It is a joy to see things pop up :-) One problem is for EditorMagi/WidgetDocs - wich uses a selectwidget - and for EditorMagic/TransINclude - which shows an editor - the popup *loses focus* as soon as the selectwidget or editor is touched. Any ideas for this? (There are still more tools I did not yet adapt.) Thank you Saq!!! <:-) -- 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/2e69e4ea-9aaa-405e-9046-1308e60433fao%40googlegroups.com.
