On Sep 12, 8:43 pm, Yakov <[email protected]> wrote: > Second, an avalanche small notes: > * in the CodeMirror2PluginInfo there's a typo: "Supported MIMEs: > {{{<<cmMIMIEs>>}}} <<cmMIMEs>>". There's an extra "I". will fix this
> * esc for exit edit mode and ctrl+enter for save and exit don't work > (through HTTP, with Opera) This behaviour is defined within ToolbarCommand: Just use: +cmSave and -cancelTiddler .. see + and - It should work then. > * in advanced options: I think "Guess syntax: <<option > chkGuessSyntax>> -- If activated" would look clearer than "Guess > syntax: <<option chkGuessSyntax>> .. If activated" hmmm > * a dialog "Are you sure you want to abandon your changes to > 'CodeMirror2PluginInfo'?" appears even if no changes were applied and > then "cancel" was pushed Jup. Since whenever you press any button the first time, I define the "hidden background editor" as "dirty". Which isn't true, I know :) I would have to create some sha fingerprint and compare ... , which needs some more code. :)) > * you can avoid making the space in "< <list filter [tag[syntax]]>>" This macro will be executed when documentation is more finished. At the moment, I don't want to have that tag assigned :) It should create a list of all tiddlers, you need to import if you want to include the editor into your own TW. Since it's not for production, it's hidden :) > in ToDo section: just wrap it with <html>...</html> and use html- > entities. Although, this looks bulky. And actually I don't understand > what this section is about. Just a reminder, to activate the macro. > * auto-indent is cool :) jup > * I feel like the first 4 global parameters need some better > description :) may be a second linkt to the original CM manual. I don't want to duplicate it. > * CodeMirror Info seems to belong to CodeMirror2PluginInfo (except the > last item) Nope, the link to the original manual is the reason, why it is there. > * the content-type button is catchy; but ideally it should be define > for the toolbar (and hense one can even put this option into the > "more" part of the ViewToolbar slice). This seem to be also better > because you don't have to change the EditTemplate which is evil > actually. I'll consider this. Toolbar commands, are not able to take configuration parameters. (see ToolbarCommands) The config-type button is a macro, that can be called in edit mode _only_. EditTemplate, to be exact. Actually I'd need 2 Toolbar buttons, to access "content-type" and "server.content-type", which is not exposed at the moment. Will be needed if used with TiddlySpace. It would be possible, to create an edit template, that integrates the button into the toolbar. But it won't be compatible with TiddlySpace toolbar icon handling. That's why it got a different position. > I think, I'll stop at this point, there's already enough to discuss/ > work on. no problem, just go on :) -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
