tiddlywiki 5.2.0 → 5.2.3

package/editions/tw5.com/tiddlers/mechanisms/PluginMechanism.tid

@@ -1,5 +1,5 @@
 created: 20130826122000000
-modified: 20190928082000464
+modified: 20220613124446953
 tags: Mechanisms
 title: PluginMechanism
 type: text/vnd.tiddlywiki

package/editions/tw5.com/tiddlers/mechanisms/RefreshThrottling.tid

@@ -1,6 +1,6 @@
 created: 20191013095916159
-modified: 20210203231820284
-tags: RefreshMechanism
+modified: 20211117232644028
+tags: RefreshMechanism Mechanisms
 title: RefreshThrottling
 type: text/vnd.tiddlywiki
 

package/editions/tw5.com/tiddlers/mechanisms/StateMechanism.tid

@@ -1,5 +1,5 @@
 created: 20131228164411884
-modified: 20150221225557000
+modified: 20211127033939415
 tags: Mechanisms
 title: StateMechanism
 type: text/vnd.tiddlywiki
@@ -17,7 +17,7 @@ The stack of templates that make up the TiddlyWiki display are complex but we'll
 Breaking down the attributes applied to the list widget:
 
 * ''filter'': selects the list of tiddlers in the `list` field of the tiddler [[$:/StoryList]]. If a tiddler is added or removed from that list then it is automatically reflected in the displayed list
-* ''history'': references the tiddler to be used to store the history stack (see the NavigationMechanism)
+* ''history'': references the tiddler to be used to store the history stack (see the HistoryMechanism)
 * ''template'': identifies a template tiddler to be used for rendering each tiddler in the list
 * ''editTemplate'': identifies a different template tiddler to be used for rendering tiddlers that are in [[draft mode|DraftMechanism]]
 * ''storyview'': specifies the story view to be used (eg classic, or zoomin)

package/editions/tw5.com/tiddlers/messages/SampleModal.tid

@@ -1,7 +1,8 @@
 created: 20140912145537860
 footer: <$button message="tm-close-tiddler">Close</$button>
-modified: 20140912145537861
+modified: 20211117224341543
 subtitle: This is a modal created especially for <<yourName>>
+tags: [[Message Examples]]
 title: SampleModal
 type: text/vnd.tiddlywiki
 

package/editions/tw5.com/tiddlers/messages/SampleWindowTemplate.tid

@@ -0,0 +1,10 @@
+created: 20211109165213041
+modified: 20220227211343988
+tags: [[Message Examples]]
+title: SampleWindowTemplate
+
+
+| ''Name:'' |<$edit field=name tag="input" />|
+|''Rank:'' |<$edit field=rank tag="input" />|
+
+''Variable 'something' contains:'' <<something>>

package/editions/tw5.com/tiddlers/messages/WidgetMessage_ tm-close-all-windows.tid

@@ -0,0 +1,20 @@
+created: 20220301162305764
+modified: 20220301180818011
+tags: Messages
+title: WidgetMessage: tm-close-all-windows
+type: text/vnd.tiddlywiki
+
+<<.from-version 5.2.2>>
+The `tm-close-all-windows` [[message|Messages]] closes all additional //browser// window that were opened with [[tm-open-window|WidgetMessage: tm-open-window]]. 
+
+The `tm-close-window` message is best generated with the ActionSendMessageWidget, which in turn is triggered by a widget such as the ButtonWidget. It is handled by the core itself.
+
+<$macrocall $name='wikitext-example-without-html'
+src="""
+<$button>Close All Windows
+<$action-sendmessage 
+  $message="tm-close-all-windows" 
+/>
+</$button>
+""" />
+

package/editions/tw5.com/tiddlers/messages/WidgetMessage_ tm-close-window.tid

@@ -0,0 +1,41 @@
+caption: tm-open-window
+created: 20220228140417116
+modified: 20220409092811188
+tags: Messages
+title: WidgetMessage: tm-close-window
+type: text/vnd.tiddlywiki
+
+<<.from-version 5.2.2>>
+The `tm-close-window` [[message|Messages]] closes an additional //browser// window that was opened with [[tm-open-window|WidgetMessage: tm-open-window]]. Specify which window to close by setting the value of <<.param param>> to the string used as <<.param windowID>> when opening the window.
+
+|!Name |!Description |
+|param //{default param}//  |String used as <<.param windowID>> when opening the window |
+
+The `tm-close-window` message is best generated with the ActionSendMessageWidget, which in turn is triggered by a widget such as the ButtonWidget. It is handled by the core itself.
+
+<<.tip """When used with the ActionSendMessageWidget, <<.param 'param'>> becomes <<.param '$param'>> """>>
+<<.tip """To close all additional browser windows that were opened with [[tm-open-window|WidgetMessage: tm-open-window]] use [[WidgetMessage: tm-close-all-windows]]""">>
+<<.tip """If the <<.param windowID>> parameter was used with [[tm-open-window|WidgetMessage: tm-open-window]] when opening a new window,  the value of <<.param windowID>> is available within that window in the variable <<.var tv-window-id>>""">>
+
+
+<$macrocall $name='wikitext-example-without-html'
+src="""
+<$button>Open Window
+<$action-sendmessage 
+  $message="tm-open-window" 
+  $param="$:/temp/openme" 
+  template="SampleWindowTemplate" 
+  windowTitle="My Window Title"
+  width="400"
+  height="500"
+  windowID="window1"
+  something="I just in over in a variable, and boy is my Hashmap tired." />
+</$button>
+<$button>Close Window
+<$action-sendmessage 
+  $message="tm-close-window" 
+  $param="window1" 
+/>
+</$button>
+""" />
+

package/editions/tw5.com/tiddlers/messages/WidgetMessage_ tm-download-file.tid

@@ -1,5 +1,5 @@
 created: 20140811112201235
-modified: 20141110133723696
+modified: 20220123141646321
 tags: Messages
 title: WidgetMessage: tm-download-file
 type: text/vnd.tiddlywiki
@@ -11,6 +11,11 @@ The download file message causes the current saver module to prompt the user to
 |param |Title of a tiddler to use as a template for the new tiddler |
 |paramObject |Optional hashmap of variable values to use for the rendering |
 
+The following variable names have special behaviour:
+
+|!Name |!Description |
+|filename |Filename for the downloaded file (note that this is a hint to the browser, and the actual filename used may be different) |
+
 The download file message is usually generated with the ButtonWidget.
 
 The download file message is handled by the TiddlyWiki core SyncMechanism which invokes the current [[SaverModule|SaverModules]].

package/editions/tw5.com/tiddlers/messages/WidgetMessage_ tm-edit-text-operation.tid

@@ -115,6 +115,8 @@ Inserts the text specified in <<.param "text">> at the caret position. If there
 </div>
 \end
 
+\define focusEditorDescription() Simply focuses the Text Editor
+
 A `tm-edit-text-operation` invokes one of the available operations on a __surrounding__ text editor. Therefore the message has to be dispatched within the editor in order for it to catch it. The following properties on the `event` object are required:
 
 |!Name |!Description |
@@ -137,6 +139,7 @@ At this point the following text operations have been implemented:
 |<<.def "save-selection">>|<<saveSelectionDescription>> |
 |<<.def "make-link">>|<<makeLinkDescription>> |
 |<<.def "insert-text">>|<<insertTextDescription>>|
+|<<.def "focus-editor">>|<<.from-version 5.2.0>> <<focusEditorDescription>> |
 
 
 !Example

package/editions/tw5.com/tiddlers/messages/WidgetMessage_ tm-new-tiddler.tid

@@ -1,6 +1,6 @@
 caption: tm-new-tiddler
 created: 20140226194405353
-modified: 20141107132122081
+modified: 20220521143507491
 tags: Messages navigator-message
 title: WidgetMessage: tm-new-tiddler
 type: text/vnd.tiddlywiki
@@ -28,7 +28,7 @@ To make a button that creates new tiddlers tagged "task", create a tiddler calle
 <$button message="tm-new-tiddler" param="TaskTemplate">New Task</$button>
 ```
 
-To create a new tiddler with given attributes rather than from a template:
+To create a new tiddler with explicit parameters rather than by cloning a template tiddler:
 
 ```
 <$button>
@@ -36,3 +36,12 @@ To create a new tiddler with given attributes rather than from a template:
 New Tiddler
 </$button>
 ```
+
+ To create a new tiddler from a template with additional parameters:
+
+```
+ <$button>
+ <$action-sendmessage $message="tm-new-tiddler" $param=<<currentTiddler>> fieldname="field value"/>
+ New Tiddler
+ </$button>
+ ```

package/editions/tw5.com/tiddlers/messages/WidgetMessage_ tm-open-window.tid

@@ -1,19 +1,41 @@
 caption: tm-open-window
 created: 20160424181447704
-modified: 20190704145627537
+modified: 20220301162140993
 tags: Messages
 title: WidgetMessage: tm-open-window
 type: text/vnd.tiddlywiki
 
-The `tm-open-window` message opens a tiddler in a new //browser// window. If no parameters are specified, the current tiddler is opened in a new window. Similiar to `tm-modal` any additional parameters passed via the <<.param "paramObject">> are being provided as variables to the new window.
+The `tm-open-window` [[message|Messages]] opens a tiddler in a new //browser// window. If no parameters are specified, the current tiddler is opened in a new window. Similiar to `tm-modal` any additional parameters passed via the <<.param "paramObject">> are provided as variables to the new window.
 
 |!Name |!Description |
-|param |Title of the tiddler to be opened in a new browser window, defaults to <<.var "currentTiddler">> if empty |
-|template |Template in which the tiddler will be rendered in |
+|param //{default param}//  |Title of the tiddler to be opened in a new browser window, defaults to <<.var "currentTiddler">> if empty |
+|template |Template in which the tiddler will be rendered |
 |windowTitle |Title string for the opened window |
 |width |Width of the new browser window |
 |height |Height of the new browser window |
-|paramObject |Hashmap of variables that will be provided to the window  |
+|left|<<.from-version "5.2.2">> Optional, left position of new browser window|
+|top|<<.from-version "5.2.2">> Optional, top position of new browser window|
+|windowID|<<.from-version "5.2.2">> Optional, unique string used to identify the widow. Can be used with [[WidgetMessage: tm-close-window]] to close the window. Defaults to the value of <<.param param>> |
+|//{any other params}// |Any other parameters are made available as variables within the new window |
 
+The `tm-open-window` message is best generated with the ActionSendMessageWidget, which in turn is triggered by a widget such as the ButtonWidget. The message is handled by the core itself.
+
+<<.tip """When used with the ActionSendMessageWidget, <<.param 'param'>> becomes <<.param '$param'>> """>>
+<<.tip """Parameters <<.param template>>, <<.param windowTitle>>, <<.param width>>, <<.param height>>, <<.param left>> and <<.param top>> require the ActionSendMessageWidget.""">>
+<<.tip """<<.from-version 5.2.2>> To close a window opened with tm-open-window use [[WidgetMessage: tm-close-window]]""">>
+<<.tip """<<.from-version 5.2.2>> To open a tiddler in more than one new window, use a unique value for <<.param windowID>>""">>
+
+<$macrocall $name='wikitext-example-without-html'
+src="""
+<$button>Open Window
+<$action-sendmessage 
+  $message="tm-open-window" 
+  $param="$:/temp/openme" 
+  template="SampleWindowTemplate" 
+  windowTitle="My Window Title"
+  width="640"
+  height="480"
+  something="This is my new window. There are many like it, but this one is mine." />
+</$button>
+""" />
 
-The `tm-open-window` message is usually generated with the ButtonWidget and is handled by the core itself.

package/editions/tw5.com/tiddlers/messages/WidgetMessage_ tm-relink-tiddler.tid

@@ -0,0 +1,26 @@
+caption: tm-relink-tiddler
+created: 20220219093748993
+modified: 20220219093748993
+tags: Messages navigator-message
+title: WidgetMessage: tm-relink-tiddler
+type: text/vnd.tiddlywiki
+
+<<.from-version "5.2.2">> The `tm-relink-tiddler` message relinks a tiddler by deleting it and recreating it with a new title. Unlike the [[WidgetMessage: tm-rename-tiddler]] message, this message does not rename the tiddler, it just relinks the references to it.
+
+The relink tiddler message requires the following properties on the `event` object:
+
+|!Name |!Description |
+|from |Current title of tiddler  |
+|to |New title of tiddler  |
+|renameInTags |Optional value "no" to disable renaming in tags fields of other tiddlers (defaults to "yes") |
+|renameInLists |Optional value "no" to disable renaming in list fields of other tiddlers (defaults to "yes") |
+
+The relink tiddler message is usually generated with the ButtonWidget and is handled by the core.
+
+! Examples
+
+To relink Tiddler1 to Tiddler2 in tags and list fields of other tiddlers:
+
+```
+<$action-sendmessage $message="tm-relink-tiddler" from="Tiddler1" to="Tiddler2" />
+```

package/editions/tw5.com/tiddlers/messages/WidgetMessage_ tm-rename-tiddler.tid

@@ -1,6 +1,6 @@
 caption: tm-rename-tiddler
 created: 20190909133618113
-modified: 20190909133618113
+modified: 20220219093748993
 tags: Messages navigator-message
 title: WidgetMessage: tm-rename-tiddler
 type: text/vnd.tiddlywiki
@@ -13,7 +13,9 @@ The `tm-rename-tiddler` message renames a tiddler by deleting it and recreating
 |renameInTags |<<.from-version "5.1.23">> Optional value "no" to disable renaming in tags fields of other tiddlers (defaults to "yes") |
 |renameInLists |<<.from-version "5.1.23">> Optional value "no" to disable renaming in list fields of other tiddlers (defaults to "yes") |
 
-The rename tiddler message is usually generated with the ButtonWidget and is handled by the NavigatorWidget.
+The very similar [[WidgetMessage: tm-relink-tiddler]] message does not rename the tiddler, it just relinks the references to it.
+
+The rename tiddler message is usually generated with the ButtonWidget and is handled by the core.
 
 ! Examples
 

package/editions/tw5.com/tiddlers/messages/WidgetMessage_ tm-scroll.tid

@@ -10,3 +10,6 @@ The `tm-scroll` message causes the surrounding scrollable container to scroll to
 |!Name |!Description |
 |target |Target DOM node the scrollable container should scroll to (note that this parameter can only be set via JavaScript code) |
 |selector |<<.from-version "5.1.23">> Optional string [[CSS selector|https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Selectors]] as an alternate means of identifying the target DOM node |
+|animationDuration |<<.from-version "5.2.2">> Optional number specifying the animation duration in milliseconds for the scrolling. Defaults to the [[global animation duration|$:/config/AnimationDuration]]. |
+
+<<.tip "Set `animationDuration` to `0` to scroll without animation">>

package/editions/tw5.com/tiddlers/nodejs/Environment Variables on Node.js.tid

@@ -1,5 +1,5 @@
 created: 20140617211749290
-modified: 20140912141809800
+modified: 20220613114121229
 tags: [[TiddlyWiki on Node.js]]
 title: Environment Variables on Node.js
 type: text/vnd.tiddlywiki
@@ -11,13 +11,15 @@ type: text/vnd.tiddlywiki
 * `TIDDLYWIKI_LANGUAGE_PATH` - Search path for languages
 * `TIDDLYWIKI_EDITION_PATH` - Search path for editions (used by the InitCommand)
 
-''Note'': The delimiter may vary between operating systems. While on Windows a semicolon `;` is used, Linux implements a colon `:`.
 
-The additional paths should each point to folders structured like the equivalent directories in the TiddlyWiki5 GitHub repository: the plugin, theme and language directories contain `publisher/pluginname/<files>` while the edition directories contain `editionname/<files>`
+<$macrocall $name=".note" _="""''1.'' The delimiter may vary between operating systems. While on Windows a semicolon `;` is used, Linux implements a colon `:`.<br><br>''2.'' On Linux systems, it may be necessary to //''export''// the variable as well as to define it.
+"""/> 
+
+The additional paths should each point to folders structured like the equivalent directories in the ~TiddlyWiki5 GitHub repository: the plugin, theme and language directories contain `publisher/pluginname/<files>` while the edition directories contain `editionname/<files>`
 
 For example:
 
 ```
-TIDDLYWIKI_PLUGIN_PATH=~/MyPluginStore
+export TIDDLYWIKI_PLUGIN_PATH=~/MyPluginStore
 tiddlywiki mywiki --build index
 ```

package/editions/tw5.com/tiddlers/nodejs/Installing TiddlyWiki on Node.js.tid

@@ -4,21 +4,28 @@ created: 20131219100608529
 delivery: DIY
 description: Flexible hosting on your own machine or in the cloud
 method: sync
-modified: 20200507110222866
+modified: 20211003230831173
 tags: Saving [[TiddlyWiki on Node.js]] Windows Mac Linux
 title: Installing TiddlyWiki on Node.js
 type: text/vnd.tiddlywiki
 
 # Install [[Node.js]]
-#* either from your favourite package manager: typically `apt-get install nodejs` on Debian/Ubuntu Linux or [[Termux for Android|Serving TW5 from Android]], or `brew install node` on a Mac
-#* or directly from http://nodejs.org
+#* Linux: 
+#*> //Debian/Ubuntu//:<br/>`apt install nodejs`<br/>May need to be followed up by:<br/>`apt install npm`
+#*> //Arch Linux//<br/>`pacman -S tiddlywiki` <br/>(installs node and tiddlywiki)
+#* Mac
+#*> `brew install node`
+#* Android
+#*> [[Termux for Android|Serving TW5 from Android]]
+#* Other 
+#*> See http://nodejs.org
 # Open a command line terminal and type:
 #> `npm install -g tiddlywiki`
 #> If it fails with an error you may need to re-run the command as an administrator:
 #> `sudo npm install -g tiddlywiki` (Mac/Linux)
-# Check TiddlyWiki is installed by typing:
+# Ensure ~TiddlyWiki is installed by typing:
 #> `tiddlywiki --version`
-# In response, you should see TiddlyWiki report its current version (eg "<<version>>"; you may also see other debugging information reported)
+#* In response, you should see TiddlyWiki report its current version (eg "<<version>>". You may also see other debugging information reported.)
 # Try it out:
 ## `tiddlywiki mynewwiki --init server` to create a folder for a new wiki that includes server-related components
 ## `tiddlywiki mynewwiki --listen` to start TiddlyWiki
@@ -30,11 +37,6 @@ type: text/vnd.tiddlywiki
 
 The `-g` flag causes TiddlyWiki to be installed globally. Without it, TiddlyWiki will only be available in the directory where you installed it.
 
-If you are using Debian or Debian-based Linux and you are receiving a `node: command not found` error though node.js package is installed, you may need to create a symbolic link between `nodejs` and `node`. Consult your distro's manual and `whereis` to correctly create a link. See github [[issue 1434|http://github.com/Jermolene/TiddlyWiki5/issues/1434]]
-
-Example Debian v8.0: `sudo ln -s /usr/bin/nodejs /usr/bin/node`
-
-You can also install prior versions like this:
-
-> npm install -g tiddlywiki@5.1.13
-
+<<.warning "If you are using Debian or Debian-based Linux and you are receiving a `node: command not found` error though node.js package is installed, you may need to create a symbolic link between `nodejs` and `node`. Consult your distro's manual and `whereis` to correctly create a link. See github [[issue 1434|http://github.com/Jermolene/TiddlyWiki5/issues/1434]]. <br><br>Example Debian v8.0: `sudo ln -s /usr/bin/nodejs /usr/bin/node`">>
+<br>
+<<.tip "You can also install prior versions like this: <br><code> npm install -g tiddlywiki@5.1.13</code>">>

package/editions/tw5.com/tiddlers/nodejs/Installing custom plugins on Node.js.tid

@@ -1,27 +1,19 @@
 created: 20191022095653896
-modified: 20191102131824766
-tags: [[TiddlyWiki on Node.js]]
+modified: 20220617130125173
+tags: [[TiddlyWiki on Node.js]] PluginsCS
 title: Installing custom plugins on Node.js
 type: text/vnd.tiddlywiki
 
-There are several ways in which custom plugins that are not part of TiddlyWiki's plugin library can be installed when using TiddlyWiki under Node.js. (See [[Installing a plugin from the plugin library]] for instructions on installing plugins from the library).
+\rules except wikilink
 
-* Arrange the PluginFolders containing the plugins in a convenient shared location and then use [[environment variables|Environment Variables on Node.js]] to tell TiddlyWiki to search those folders. The plugins can be referenced in `tiddlywiki.info` by their name (e.g. `tiddlytools/magic`)
-* Place the PluginFolders containing the plugins in a `plugins` folder within the [[wiki folder|TiddlyWikiFolders]]. TiddlyWiki will attempt to include every subfolder as a plugin. Do not add the plugin names to `tiddlywiki.info`. Do not add the PluginFolders under a specific namespace:<br><pre>.
-├── plugins
-│   ├── relink
-│   │   ├── js
-│   │   ├── plugin.info
-│   │   └── tiddlers
-│   └── relink-markdown
-│       ├── js
-│       ├── plugin.info
-│       └── readme.tid
-├── tiddlers
-└── tiddlywiki.info
-</pre>
-* Depending on how TiddlyWiki itself has been installed, plugins can also be installed by copying the plugin folders into the `plugins` folder of the repository. This is only recommended if working with a forked copy of the repo. It is not recommended if TiddlyWiki has been installed with npm because npm is liable to overwrite the installation when performing an update
+! Introduction
 
-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.
+There are several ways in which official plugins and custom plugins can be installed when using TiddlyWiki with a Node.js client-server configuration.
 
+<$macrocall $name=".note" _="""For instructions on installing plugins from libraries to ''single-file'' wikis learn more at [[Plugins]].
+"""/> 
+
+!! Plugin Load Order
+
+{{Plugin Ordering}}
 

package/editions/tw5.com/tiddlers/nodejs/Installing official plugins on Node.js.tid

@@ -0,0 +1,40 @@
+created: 20220611123344385
+modified: 20220617132351460
+tags: [[TiddlyWiki on Node.js]] PluginsCS
+title: Installing official plugins on Node.js
+type: text/vnd.tiddlywiki
+
+Follow these instructions when using TiddlyWiki with a client-server Node.js configuration:
+
+# Identify the plugins you want to install using the ''Plugins'' tab of <<controlPanel-plugin-link>> (''don't'' install the plugins from here, though)
+#* Plugins are identified by their type (ie language, theme or plugin) and their publisher and title. For example, the plugin `$:/plugins/tiddlywiki/internals` is referred to as ''tiddlywiki/internals''
+
+# Quit the server if it is running
+
+# Edit the `tiddlywiki.info` file (it is in JSON format) and locate the `plugins`, `themes` or `languages` section (see below)
+
+# Add entries corresponding to the plugins you wish to add
+#* Take care to retain ''commas ''to separate items
+#* Do ''not'' terminate the last item in a list with a comma
+
+# Restart the server
+
+```
+{
+	"plugins": [
+		"tiddlywiki/codemirror"
+	],
+	"themes": [
+		"tiddlywiki/vanilla",
+		"tiddlywiki/snowwhite"
+	],
+    "languages": [
+        "es-ES",
+        "fr-FR",
+        "en-EN"
+    ]
+}
+```
+
+<$macrocall $name=".note" _="An overview of working with plugins can be found at [[Plugins]].<br>Also see: [[Installing custom plugins on Node.js]]."/>
+

package/editions/tw5.com/tiddlers/nodejs/PluginsCS.tid

@@ -0,0 +1,9 @@
+created: 20220612082924589
+list: [[Installing custom plugins on Node.js]] [[Installing official plugins on Node.js]] [[Uninstalling a plugin with Node.js]]
+modified: 20220617124533352
+title: PluginsCS
+type: text/vnd.tiddlywiki
+
+This tiddler is used as a tag in the [[Plugins]] tiddler to create a sorted list
+
+<<list-links-draggable>>

package/editions/tw5.com/tiddlers/nodejs/TiddlyWiki on Node.js.tid

@@ -1,15 +1,20 @@
 created: 20131129094353704
-modified: 20200318115527226
+modified: 20220617114433107
 tags: Platforms
 title: TiddlyWiki on Node.js
 type: text/vnd.tiddlywiki
 
+\rules except wikilink
+
 Running TiddlyWiki on [[Node.js]] brings several important benefits over and above the single file version:
 
-* You can edit your content on any suitably compatible HTML5 browser, including smartphones and tablets
 * Individual tiddlers are stored in separate files, which you can organise as you wish
+
 * The ability to build multiple wikis that blend different combinations of shared and unique content
 
+* You can edit your content on any modern browser, including smartphones and tablets
+
+
 <<.warning """Note that TiddlyWiki on Node.js doesn't currently support directly modifying the tiddler files via the file system while it is running. The server must be restarted in order to for changes to take effect. The recommended way to interact with a running wiki is via the HTTP or JavaScript APIs.""">>
 
 For more information see:

package/editions/tw5.com/tiddlers/nodejs/Uninstalling a plugin with Node.js.tid

@@ -0,0 +1,31 @@
+created: 20220611125113040
+modified: 20220617133704286
+tags: [[TiddlyWiki on Node.js]] PluginsCS
+title: Uninstalling a plugin with Node.js
+type: text/vnd.tiddlywiki
+
+Follow these instructions when using TiddlyWiki with client-server Node.js configuration:
+
+# Quit the server if it is running
+
+# Edit the `tiddlywiki.info` file (it is in JSON format) and locate the `plugins` and `themes` section (see below)
+
+# Remove the entries corresponding to the plugins you wish to remove
+#* Take care to retain ''commas'' to separate items
+#* Do ''not'' terminate the last item in a list with a comma
+
+# Restart the server
+
+```
+{
+	"plugins": [
+		"tiddlywiki/codemirror"
+	],
+	"themes": [
+		"tiddlywiki/vanilla",
+		"tiddlywiki/snowwhite"
+	]
+}
+```
+
+<$macrocall $name=".note" _="An overview of working with plugins can be found at [[Plugins]]"/>

package/editions/tw5.com/tiddlers/nodejs/Using TiddlyWiki on Node.js.tid

@@ -1,18 +1,18 @@
 created: 20131219100520659
-modified: 20200523092939199
+modified: 20220613172345723
 tags: [[TiddlyWiki on Node.js]]
 title: Using TiddlyWiki on Node.js
 type: text/vnd.tiddlywiki
 
-TiddlyWiki5 includes a set of [[Commands]] for use on the command line to perform an extensive set of operations based on TiddlyWikiFolders, TiddlerFiles and TiddlyWikiFiles.
+~TiddlyWiki5 includes a set of commands for use on the command line to perform an extensive set of operations based on TiddlyWikiFolders, TiddlerFiles.
 
-For example, the following command loads the tiddlers from a TiddlyWiki HTML file and then saves one of them in static HTML:
+For example, the following command loads the tiddlers from a ~TiddlyWiki HTML file and then saves one of them in static HTML:
 
 ```
 tiddlywiki --verbose --load mywiki.html --rendertiddler ReadMe ./readme.html
 ```
 
-Running `tiddlywiki` from the command line boots the TiddlyWiki kernel, loads the core plugins and establishes an empty wiki store. It then sequentially processes the command line arguments from left to right. The arguments are separated with spaces.
+Running `tiddlywiki` from the command line boots the ~TiddlyWiki kernel, loads the core plugins and establishes an empty wiki store. It then sequentially processes the command line arguments from left to right. The arguments are separated with spaces.
 
 <<.from-version "5.1.20">> First, there can be zero or more plugin references identified by the prefix `+` for plugin names or `++` for a path to a plugin folder. These plugins are loaded in addition to any specified in the  [[TiddlyWikiFolder|TiddlyWikiFolders]].
 

package/editions/tw5.com/tiddlers/nodejs/tiddlywiki.files_Files.tid

@@ -1,6 +1,6 @@
 created: 20161015114118243
-modified: 20201201000000000
-tags: TiddlyWikiFolders
+modified: 20211114101256212
+tags: TiddlyWikiFolders [[TiddlyWiki on Node.js]]
 title: tiddlywiki.files Files
 type: text/vnd.tiddlywiki
 
@@ -48,13 +48,14 @@ Directory specifications in the `directories` array may take the following forms
 
 * a ''string'' literal, specifying the absolute or relative path to the directory containing the tiddler files (relative paths are interpreted relative to the path of the `tiddlywiki.files` file). The directory is recursively searched for tiddler files
 * <<.from-version "5.1.14">> an ''object'' with the following properties:
-** ''path'' - (required) the absolute or relative path to the directory containing the tiddler files (relative paths are interpreted relative to the path of the `tiddlywiki.files` file). Note that the directory is not recursively searched; sub-directories are ignored
+** ''path'' - (required) the absolute or relative path to the directory containing the tiddler files (relative paths are interpreted relative to the path of the `tiddlywiki.files` file). Note that by default the directory is not recursively searched; sub-directories are ignored unless the //searchSubdirectories// flag is set to `true` (see below).
 ** ''filesRegExp'' - (optional) a [[regular expression|https://developer.mozilla.org/en/docs/Web/JavaScript/Guide/Regular_Expressions]] that matches the filenames of the files that should be processed within the directory
 ** ''isTiddlerFile'' - (required) if `true`, the file will be treated as a [[tiddler file|TiddlerFiles]] and deserialised to extract the tiddlers. Otherwise, the raw content of the file is assigned to the `text` field without any parsing
-** ''isEditableFile'' - (optional) if `true`, changes to the tiddler be saved back to the original file. The tiddler will be saved back to the original filepath as long as it does not generate a result from the $:/config/FileSystemPath filters, which will override the final filepath generated if a result is returned from a filter. <<.from-version "5.1.23">>
+** ''isEditableFile'' - <<.from-version "5.1.23">> (optional) if `true`, changes to the tiddler be saved back to the original file. The tiddler will be saved back to the original filepath as long as it does not generate a result from the $:/config/FileSystemPath filters, which will override the final filepath generated if a result is returned from a filter.
+** ''searchSubdirectories'' - <<.from-version "5.1.23">> (optional) if `true`, all subdirectories of the //path// are searched recursively for files that match the (optional) //filesRegExp//. If no //filesRegExp// is provided, all files in all subdirectoies of the //path// are loaded. Tiddler titles generated via a //source// attribute (see above) will only include the filename, not any of the subdirectories of the path. If this results in multiple files with loaded with the same tiddler title, then only the last file loaded under that tiddler title will be in memory. In order to prevent this, you must have multiple directory objects listed and customize the title field with a //prefix// or //suffix// alongside the //source// attribute.
 ** ''fields'' - (required) an object containing values that override or customise the fields provided in the tiddler file (see above)
 
-Fields can be overridden for particular files by creating a file with the same name plus the suffix `.meta` -- see TiddlerFiles.
+Fields can also be overridden for particular files by creating a file with the same name plus the suffix `.meta` -- see TiddlerFiles.
 
 ! Examples
 

package/editions/tw5.com/tiddlers/nodejs/tiddlywiki.info_Files.tid

@@ -1,6 +1,6 @@
 created: 20161015114042793
-modified: 20161015121622327
-tags: TiddlyWikiFolders
+modified: 20211114101249016
+tags: TiddlyWikiFolders [[TiddlyWiki on Node.js]]
 title: tiddlywiki.info Files
 type: text/vnd.tiddlywiki
 

package/editions/tw5.com/tiddlers/platforms/TiddlyFox Apocalypse.tid

@@ -1,6 +1,6 @@
 created: 20171109170823847
-modified: 20171113161750857
-tags: Platforms
+modified: 20211124214943222
+tags: TiddlyFox
 title: TiddlyFox Apocalypse
 type: text/vnd.tiddlywiki
 

package/editions/tw5.com/tiddlers/platforms/TiddlyWiki in the Sky for TiddlyWeb.tid

@@ -1,12 +1,8 @@
 created: 20131129100250644
-modified: 20150412185535373
-tags: [[Hosting your TiddlyWiki on the web]] Platforms
+modified: 20211124214855770
+tags: $:/deprecated
 title: TiddlyWiki in the Sky for TiddlyWeb
 type: text/vnd.tiddlywiki
+caption: {{!!title}} - ^^deprecated^^
 
-TiddlyWiki in the Sky for TiddlyWeb allows content to be synchronised between TiddlyWiki running in the browser and a TiddlyWeb server. Features include:
-
-* Lazy loading
-* Two way synchronisation between the browser and the server
-** Synchronising from the server is accomplished by polling (currently every 60 seconds)
-* Throttling so that rapidly changing tiddlers don't overwhelm the server
+The term "TiddlyWiki in the Sky for TiddlyWeb" was used to refer to the ability for content to be synchronised between TiddlyWiki running in the browser and a TiddlyWeb server. This configuration should still work but is no longer commonly used.

package/editions/tw5.com/tiddlers/plugins/Highlight Plugin.tid

@@ -1,6 +1,6 @@
 created: 20160107223417655
 list: 
-modified: 20170228102525208
+modified: 20220222094354907
 tags: OfficialPlugins [[Plugin Editions]]
 title: Highlight Plugin
 type: text/vnd.tiddlywiki
@@ -8,3 +8,5 @@ type: text/vnd.tiddlywiki
 The Highlight plugin provides the ability to apply syntax colouring to text.
 
 See [ext[https://tiddlywiki.com/plugins/tiddlywiki/highlight|plugins/tiddlywiki/highlight]]
+
+<<.warning """The latest version of the [[Highlight Plugin]] requires a modern browser that fully supports JavaScript ES6 (released in 2015). The older version is still available as the ''highlight-legacy'' plugin for users who need to use an older browser.""">>