Mohammad, Slightly off topic but related.
>From what you said I have tried to create a library via the single file wiki. I have however identified more to it than The upgrade library is formatted as an ordinary plugin tiddler with the > plugin type library. It contains a copy of each of the plugins, themes and > language packs available within the TiddlyWiki5 repository. I believe once the "library" (payload) tiddler (containing plugins) is created it needs to be exported and placed at a url, then you need a tiddler (link to payload url) containing that url into the wiki, that wants access to the library. I am still working on it, but there are quite a few tiddlers involved in this. I have being hacking existing import and plugin mechanisms and have come up with a number of new and helpful workflows, and have not publish much yet because this area can be a little "verbose". Libraries are a key part of this plugin and distribution process. Regards Tony On Monday, March 30, 2020 at 11:53:20 PM UTC+11, Mohammad wrote: > > In https://tiddlywiki.com/prerelease/#MakeLibraryCommand > > It syas: > > The upgrade library is formatted as an ordinary plugin tiddler with the >> plugin type library. It contains a copy of each of the plugins, themes and >> language packs available within the TiddlyWiki5 repository. > > > > Regarding the third party plugin can be put in other path using > TIDDLYWIKI_PLUGIN_PATH > > How one can make the library from those located in TIDDLYWIKI_PLUGIN_PATH > > --Mohammad > > > On Friday, March 27, 2020 at 7:04:23 PM UTC+4:30, PMario wrote: >> >> On Friday, March 27, 2020 at 2:19:18 PM UTC+1, Mohammad wrote: >>> >>> My question is setting TIDDLYWIKI_PLUGIN_PATH global variable (for >>> example in Windows 10) means Tiddlywiki will load all plugins from this path >>> or this is extra to plugins/tiddlywiki folder? >>> >>> For example I have installed >>> >>> - Tiddlywiki prerelease in D:\Tiddlywiki5.1.22p >>> - So, I have D:\Tiddlywiki5.1.22p\plugins folder >>> - Then TIDDLYWIKI_PLUGIN_PATH=D:\Tiddlywiki\Custom_Plugins >>> >>> This variable make it easy, that TW will find 3rd party plugins. eg: >> >> I don my plugins in a completely different structure as TWs directory >> structure. >> >> My TIDDLYWIKI_PLUGIN_PATH=D:\path\to\my\plugins ... >> >> The whole structure is: D:\path\to\my\plugins\wikilabs\<plugin-name> >> >> This makes it possible to add one of my plugins into tiddlywik.info like >> so: >> >> My link-to-tabs-server edition tiddlywiki.info >> <https://github.com/wikilabs/editions/tree/master/link-to-tabs-server> >> looks like this. >> >> { >> "description": "Server configuration of the wikilabs edition", >> "plugins": [ >> "tiddlywiki/tiddlyweb", >> "tiddlywiki/filesystem", >> "wikilabs/link-to-tabs", >> "wikilabs/info-session", >> "wikilabs/advanced-search-plus" >> ], >> "themes": [ >> ], >> "includeWikis": [ >> "../link-to-tabs" >> ], >> "config": { >> "default-tiddler-location": "../link-to-tabs/tiddlers" >> } >> } >> >> This makes development much easier, since I don't need to add the full >> directory name. >> >> The environment variables can have several paths, with are separated by >> a semicolon ";" in windows and a colon ":" for unix-like systems >> >> have fun! >> mario >> >> -- 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/f7ddd142-f747-4ced-accf-f51399e36531%40googlegroups.com.
