Folks Thanks for the feedback. I have a set of standards I use to build all my projects, only one ever became plugin, but I have dozens using the following method, which made sense for non plugin macros.
To illustrate; The set of project tiddlers look something like this; $:/PSaT/focus-tiddler <file:///C:/Data/TW5/!Smart%20Documents/BlogToSelf.html#%24%3A%2FPSaT%2Ffocus-tiddler> $:/PSaT/focus-tiddler/button <file:///C:/Data/TW5/!Smart%20Documents/BlogToSelf.html#%24%3A%2FPSaT%2Ffocus-tiddler%2Fbutton> $:/PSaT/focus-tiddler/dev-notes <file:///C:/Data/TW5/!Smart%20Documents/BlogToSelf.html#%24%3A%2FPSaT%2Ffocus-tiddler%2Fdev-notes> $:/PSaT/focus-tiddler/image/focused-button <file:///C:/Data/TW5/!Smart%20Documents/BlogToSelf.html#%24%3A%2FPSaT%2Ffocus-tiddler%2Fimage%2Ffocused-button> $:/PSaT/focus-tiddler/image/unfocused-button $:/PSaT/focus-tiddler/images/save <file:///C:/Data/TW5/!Smart%20Documents/BlogToSelf.html#%24%3A%2FPSaT%2Ffocus-tiddler%2Fimages%2Fsave> $:/PSaT/focus-tiddler/jumplist <file:///C:/Data/TW5/!Smart%20Documents/BlogToSelf.html#%24%3A%2FPSaT%2Ffocus-tiddler%2Fjumplist> $:/PSaT/focus-tiddler/macros <file:///C:/Data/TW5/!Smart%20Documents/BlogToSelf.html#%24%3A%2FPSaT%2Ffocus-tiddler%2Fmacros> $:/PSaT/focus-tiddler/sideBar <file:///C:/Data/TW5/!Smart%20Documents/BlogToSelf.html#%24%3A%2FPSaT%2Ffocus-tiddler%2FsideBar> $:/PSaT/focus-tiddler/sideBarSegment <file:///C:/Data/TW5/!Smart%20Documents/BlogToSelf.html#%24%3A%2FPSaT%2Ffocus-tiddler%2FsideBarSegment> $:/config/number-of-jump-tiddlers <file:///C:/Data/TW5/!Smart%20Documents/BlogToSelf.html#%24%3A%2Fconfig%2Fnumber-of-jump-tiddlers> To make a plugin I was hopping I can add something like $:/PSaT/focus-tiddler/readme $:/PSaT/focus-tiddler/plugin $:/PSaT/focus-tiddler/license $:/PSaT/focus-tiddler/history Then make a tool to rename and pack the essential $:/plugin tiddlers from above $:/plugin/<publisher>/<plugin-name>/<dir>/<file-name> $:/plugin/PSaT/focus-tiddler/readme $:/plugin/PSaT/focus-tiddler/plugin $:/plugin/PSaT/focus-tiddler/license $:/plugin/PSaT/focus-tiddler/history *But, can the balance of tiddlers remain in my $:/PSaT/projectname/[folder/]tiddlername namespace?* Then references in the code to $:/PSaT/projectname name tiddlers will not need rewriting I expect some changes may be needed to access shadow tiddlers that were not shadows before packing into the plugin - Can any one guide me on the differences between tiddler and shadow in this circumstance (if any)? I have not detailed it here, but I have a project tool that has the template for tiddlers to include in a project, but with the plugin also the for the the licence etc.., so I write it once For me the question is can I accommodate these tiddlers in the alternate name space or *must I pivot *and change the whole process to live in the $:/plugin/PSaT/project namespace? Which I really do not want to do. Regards and thanks for you rime TW Tones On Friday, July 10, 2020 at 12:29:27 PM UTC+10, TonyM wrote: > > Folks, > > I build a lot of macros I do not publish as plugins yet, However > eventually I will publish a library. > > Because of this I create tiddlers of the form $:/PSaT/*projectname* and > tiddlers below that. > > I hope to automate the movement of a project into a plugin, so this is an > important question I must answer now. > > *My Question is If I start publishing plugins can I keep the majority of > the tiddlers in this namespace or must they all become > $:/plugin/PSaT/projectname and tiddlers below that?* > > Thanks in advance > Tony > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/556e42f6-ff86-43f7-92f3-15da6b53d225o%40googlegroups.com.
