As I mentioned in a thread over the weekend [1], I've been engaged in a relatively major refactoring of the TiddlyWiki5 code to bring in a new plugin module mechanism. It's a more sophisticated version of the systemConfig mechanism in classic TiddlyWiki.
It's turned out that I could implement something that has been discussed a few times here in the group: the idea of a TiddlyWiki micro-kernel that is as small as possible, and dynamically loads everything else as plugins. The new challenge is to have it working properly in the browser and on the server under node.js. You can see the results at http://tiddlywiki.com/tiddlywiki5, or inspect the code at: https://github.com/Jermolene/TiddlyWiki5/tree/master/rabbithole (Be sure to scroll down to the readme file). The end result is that plugins will become bundles of related tiddlers, that can incorporate code, translations and other resources. Users will be able to manage plugins as a unit, and soon be able to download them from a central repository on tiddlywiki.com. The goal for plugin writers is to make it much simpler to create plugins, without so much of the brittle overriding that characterises plugins in classic TiddlyWiki. For sophisticated users, the plugin mechanism will make it possible to perform deep customisation of the TiddlyWiki app. Please fire any questions, raise tickets, or use GitHub to apply comments and questions to the code. Best wishes Jeremy [1] https://groups.google.com/d/msg/tiddlywikidev/7Q07wDOeNIk/KucLG_oSEusJ -- Jeremy Ruston mailto:[email protected] -- 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.
