PLUGIN OF PLUGINS -- For Managing Multiple Tiddlywiki? Possible?

[prog...@assays.tv]

I do hold back slightly, but on this I kinda think its a thought, maybe others have thunk?

That the best plugins one combines into ONE plugin to EASILY transport TW to TW.

HOW can one do  that?

Is there an ethic for it?

AND A METHOD?

Josiah

[Tobias Beer]

No solution, just a +1.

[Matthew Lauber]

I don't have a good solution.  What I ended up doing was creating my own plugin library on github, and then I only need to copy that tiddler to new files.  From there, I can install everything via the plugin library mechanism.  This had the added benefit that only any given tiddler, I can check to see if I've updated any of the plugins easily, and easily install the updates.  But it doesn't help with other people's plugins unless I keep up with copying and pasting them.  

Matt

[prog...@assays.tv]

i really like we share the same headache.

On Wednesday, 11 May 2016 22:33:30 UTC+2, Tobias Beer wrote:

No solution, just a +1.

[Greg Davis]

If I understand correctly, you have several plugins that you would like to have included each time you start a new TiddlyWiki. I had a similar question which applies to plugins as well. [TW5] use JSON as alternative to plugin I tagged the tiddlers I wanted to include and using Advanced Search saved them all as a JSON that could be imported to a new TW. This also has worked with my favorite plugins. Tag the plugins you want, with a unique tag, and then using Advanced Search save them as a JSON. You could also create different groups of favorite plugins by using tags and saving appropriate JSONs.

Of course this wold not take care of updating for new versions but once a new version is installed just save as JSON again and ready to go.

See Example tiddlers at: Custom Left Menu

Hope that helps,
Greg

[prog...@assays.tv]

Greg.

Yes. It would make life easier. Thanks  for the tip. I will try that, also saved as a list via Tobias Beers excellent saveable "Stories" so I don't have to find them again.

Basically I use MANY Plugins that I add to an new TW, mainly for preparing data, and then delete them when that phase is over. It would be easier to be able to wrap them as one group.

Best wishes
Josiah

[Mark S.]

I haven't tried this, but it should work. Open up your plugins, and give each of the internal tiddlers a common tag. This will override them as shadow tiddlers.

Then repack them using the tinka plugin, using the new tag as the gathering identifier. Tinka is available here:

http://twguides.org/wiki/tinka.html

Now everything you want will be in one giant plugin which you can drag and drop and later delete.

Mark

[Mat]

On Friday, May 13, 2016 at 9:11:08 PM UTC+2, Mark S. wrote:

I haven't tried this, but it should work. [...]

Also untried but couldn't one just do it right away with the specific plugins rather than having to first manually tag them (which splits them). Plugins are basically big tiddler, no? And I'd say they can be rather easily found in Tinka by filtering on [plugin-type[plugin]] etc.

...or better yet; TiddlerBundles - have also not tried to bundle up plugins but, again, I think they're just big tiddlers

<:-)

[prog...@assays.tv]

Mat

TX. TiddlerBundles looks interesting. i will try it. the point is NOT, for me, they are shadows, per se. its that I can identify them. Shift them easily between TWs en bulk. Use them. Delete them.

i did NOT make as clear as i should that my question was as much about easy DELETING as transport. later.

Josiah

[wimm]

hi, 

just a suggestion, italics steps you have to do when set of tiddlers changes.

1. (once) export all required tiddlers as separate JSON files into a single folder (on memory stick)
   
2. in your file manager select all exported JSON files, drag onto to the open (target) wiki in your browser
   
3. (once) create tiddler with tiddler text as shown below to verify_delete_imported tiddlers easily
4. press the import button
   
5. (once) edit the $:/import tiddler, remove the # signs,  
6. (once) copy the links like [[xxx]] [[yyy]] from text area 
7. (once) paste links over [[title1]] [[title2]] [[title3]] in the extra tiddler  (inside the quotes)
8. (once) export this tiddler as json for later re use in same folder as other tiddlers
9. save your new wiki and reload wiki (plugins are now active)
10. use the imported tiddlers .....
    
11. search and open the delete_imported tiddlers press on the waste basket icons to delete some or all the tiddlers

If you only import the SAVED verify_delete_imported tiddler you can check if all required tiddlers are present.

tiddler body for verify_delete_imported tiddlers:

<$list filter="[[title1]] [[title2]] [[title3]]">
<div class="tc-menu-list-item">
<$link to={{!!title}}><$view field="title"/> <small>  [ <$view field="modifier"/>  <$view field="modified" format="date" template=" YYYY0MM0DD"/>] </small></$link><span title="delete tiddler"><$button message="tm-delete-tiddler" class="tc-btn-invisible">{{$:/core/images/delete-button}}</$button></span>
</div>
</$list>

output of verify_delete_imported (when tiddler 2 is not present):

title1  modifier modify_date_yyyymmdd waste_basket_icon

title2

title3  modifier modify_date_yyyymmdd waste_basket_icon

WiM

[Jed Carty]

It should be possible to create groupings of plugins that you install form their normal sources with a single button. This may require some updates to the plugin library code, but any changes would be part of what we want to do anyway.
I am mostly interested in this because the same solution could be applied to how twederation works and the plugin library and twederation should use the same mechanisms. Jetlag is giving me some troubles but as of next tuesday I will be finished with all my current contracts and I will hopefully be putting more time into tiddlywiki.

[prog...@assays.tv]

Ciao Jed Carty

One of things it could help me with is ALSO easier prepping of online read-only versions. Whilst one can hide, via CSS, unneeded interface, I prefer to delete EVERYTHING not essential. It can improve performance.

Josiah