Clarification needed for the difference between drag n' drop and folder installation

60 views
Skip to first unread message

Tejasvi S Tomar

unread,
Sep 11, 2020, 1:17:37 AM9/11/20
to TiddlyWiki
Note that including a plugin as an ordinary tiddler (e.g. by dragging and dropping a plugin into the browser) will result in the plugin only being active in the browser, and not available under Node.js.

Why the plugin being "available under Node.js" is relevant as long as it works in the browser?

TW Tones

unread,
Sep 11, 2020, 4:01:24 AM9/11/20
to TiddlyWiki
Tejasvi,

If you use a node wiki, dropping a plugin is only installed in the current wiki. Installing it behind the scenes makes it available to all wikis within the node implementation. I only know this as a fact for the bob implementation and by what others have told me.


Regards
Tones

Saq Imtiaz

unread,
Sep 11, 2020, 4:35:25 AM9/11/20
to TiddlyWiki
When you use TiddlyWiki on node.js, you essentially have two copies of TiddlyWiki running.
One in the browser, one in node.js (server component), and the two synchronize with each other. The browser copy is responsible for the UI/UX and the node.js copy handles the API and saving and loading the tiddlers from disk. This is a very simplified explanation but hopefully it gets the point across.

Most plugins only involve the UI/UX in the browser and therefore do not need to run under node.js. 
However, plugins that need to tweak the behaviour of the wiki running under node.js (the server component) can need to be executed under node.js to ensure they operate properly and are executed in the correct order, and therefore need to be installed as a plugin folder.

Cheers,
Saq
Reply all
Reply to author
Forward
0 new messages