I would absolutely recommend Thirflow --
Use the *Third Flow* plugin in your Node.js-based TiddlyWikis to develop your customization plugins inside TiddlyWiki but with support for well-structured source code repository layouts. The *Third Flow* plugin supports your plugin development in that it organizes all your tiddler source files into a clear hierarchical folder structure based on tiddler titles. An additional plugin creation command module makes it easy to create the package plugin itself as well as a demonstration TiddlyWiki without the hassle of having to maintain separate and even multiple tiddlers/ and plugin/ folders. Also, the *Third Flow* relieves you from shuffling tiddler source code files around in your source code repository. There's only a single tiddler source code tree and it is synchronized to your tiddler's title-based structure. Thus, no more need for external editing sessions and source file shuffling. Simply install this plugin into your TiddlyWiki in which you are developing your customizations. For more information, please go to the Third Flow project website <http://thediveo.github.io/ThirdFlow>. You can use the new File Storage <http://127.0.0.1:9010/#%24%3A%2Fplugins%2FTheDiveO%2FThirdFlow%2Fui%2FControlPanel%2FFileStorage> control panel tab to configure how your tiddlers get organized into folders and subfolders in your source code repository. Enjoy the *Third Flow*! --- On Monday, January 13, 2020 at 10:39:11 AM UTC+3:30, TonyM wrote: > > Folks, > > Request for Comment from plugin builders. > > I am building a generator to create all related tiddlers when building a > plugin. I am doing this because I will be migrating dozens of macro > solutions to plugins. > > This post is seeking input, the result will be shared. > > The basic functionality is as follows; > > - Designer provides a > - plugin prefix "$:/plugins/*brand*/" > - and Project name "myproject/" > - Then a set of tiddler titles will be generated as follows > $:/plugins/brand/myproject > > readme $:/plugins/brand/myproject/readme Standard > usage $:/plugins/brand/myproject/usage Standard > docs $:/plugins/brand/myproject/docs Optional for more complex > macros $:/plugins/brand/myproject/macros $:/tags/Macro > config $:/plugins/brand/myproject/config connect to config tiddlers > examples $:/plugins/brand/myproject/examples Example documentation + > settings $:/plugins/brand/myproject/settings alternative to config > license $:/plugins/brand/myproject/license MIT default > styles $:/plugins/brand/myproject/styles $:/tags/Stylesheet > data $:/plugins/brand/myproject/data Dictionary tiddler of config values > etc... > keyboard $:/plugins/brand/myproject/keyboard (Document any keys defined) > history $:/plugins/brand/myproject/history (version release history) > > > - There will be a set of tiddlers to use or configure as the source > for each of these tiddlers. > - You can exclude any tiddler you do not want > - Each tiddler can be created one at a time or generated from a source > tiddler > - Other tiddlers can be added to the list including config tiddlers > $:/config/tiddlername > - Tiddlers can then be customised with standard edit > - A filter will be generated for use in the Tinka Plugin > - Where possible I will populate the tinka values > - You then generate the plugin using Tinka > > Any thoughts additions or deletions, templates etc.. please share. > > Regards > Tony > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki/b71bc7a1-1c28-4952-bfd4-49c3d9e2d3b4%40googlegroups.com.
