> Where we are back, to the point, that we should be able to switch themes > and languages, at startup, depending on some information about the TW > context :) >
Well, I'm suggesting that we should also be able to switch configuration tiddlers at startup as well. > Does the module mechanism have something like an export.init() mechanism. > Where init() is activated, when eg: theme is switched. ... > So the startup module only needs to detect the mode and the plugins, > themes, languages can implement the init() and may be a teardown() methods > for cleaning up. > What are the other modes you'd be thinking of? I'm still not seeing the use case for being able to create a tiddlywiki file that displays in a different language according to the components of the path from which it is served. I'd propose a new "readonly" plugin that replaces the current "readonly" theme. It would use the new configuration mechanism to suppress the toolbar buttons that don't apply to readonly mode. Best wishes Jeremy > > -mario > > > -- Jeremy Ruston mailto:[email protected] -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
