Hi PMario & Kosmaton, Well, why not create a HijackEventsPlugin? It could provide general bindings via some global HijackConfig tiddler like so...
!OnBeforeOpen run.this.function and.that.too $runTiddlerAsCode !OnAfterOpen how.about.something.after.the.tiddler.was.displayed $RunCodeFromSomeTiddler##Section etc... Using config sections, one could thus declare multiple bindings to the same events bound by a single, generic core hijack. Note, that any HijackEventsPlugin of course would not parse HijackConfig everytime an event fires. Instead those bindings were stored in memory, loaded into some global "bindings" object, to which plugins could register as well, without any need to mess with any tiddler called HijackConfig. I think such a plugin would provide a very flexible framework for something like a TW-IDE... if only to test code by having it entered into some tiddler and hooked up to default events. I don't even think that this plugin would be utterly difficult as most of these hijacks are already in use at some place and it would make sense if there were a central, dependable solution to them ...again, if only as a programming environment rather than something which Eric might call a core hack. Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki?hl=en.
