Mohammad, Whatever my long term choice do share if you see any essential content missing from my Original Post.
Third flow seems a great long term investment in the life of a plugin developer. It however needs me to build on top of node, be familiar with file based organisation and more. I may still go that direction but I note my own work would be adding more within ThirdFlows *Plugin Boilerplate, and Adding template tiddlers for Plugin Field Details* which I do not yet know how customisable it is. I see in part how you manage to be so productive and generating plugins, with demo and release. My dilemma here is the the choice I need to make between continuing my own solution or investing the time to adopt Third Flow. In my case I have dozens of macros and wikitext based solutions, without javascript, that I currently store as bundles, that I would like to publish. As a result any productivity gains I can find will reduce the publishing effort. It feels that third flow requires an investment and despite it saying "all in the browser" it requires command line and file/folder structures outside the browser. The investment in third flow would be needed by future designers of simple plugins, yet should I develop and intermediate solution? Finally in the long run I see opportunities with my own tool to develop a concept where by a plugin is imported to serve a development function, during its use it can be customised, enhanced such that in each use it evolves more features, is regenerated and used in the next project. In this use the requirements of third flow are too disruptive. This is in keeping with my deep interest in rapid development, "set based" iterative design processes. Regards Tony On Monday, January 13, 2020 at 8:15:12 PM UTC+11, Mohammad wrote: > > 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/0ce9a0da-8fa1-4672-b145-c47bb905d2bd%40googlegroups.com.
