TiddlyWiki opportunities for unlimited potential

[TW_Tones]

This Topic is intended to be a cumulative resource for inspiration

Since I, and many of you are besotted with TiddlyWiki and its apparently unlimited potential I thought I would start this thread so we can submit examples for others to consider and share them with the community.

What is a “TiddlyWiki opportunity for unlimited potential”.
Basically its any feature or fact you find which introduces so many possibilities of what can be done with TiddlyWiki it provides yet another branch of possibilities.

Here are some examples already evident in TiddlyWiki

• Since tiddlywiki provides out of the box advanced ways to manipulate the User Interface and has selectable layouts a TiddlyWiki could be made to “look like” almost any webpage or application if desired.
• Since the final result of rendering wikitext and widgets is HTML (this is how browsers work) tiddlywiki can generate HTML that can be used anywhere HTML can be used, which is almost anywhere on the internet.
• Since CSS is available in tiddlywiki though stylesheets and the <style> tags, most CSS methods are available to TiddlyWiki designers and this includes CSS calculations and data tags.
• Using cookies on file wikis to get Shared storage across TiddlyWikis. see reply

Please create a new Topic/thread to discuss any one of these in more detail. At most please restrict replying here to “New Opportunities” or “Questions of clarification” about an opportunity posted here".

Later we may curate the answers and update this lead post.

[TW_Tones]

An opportunity of unlimited potential

Shared storage across TiddlyWikis.

Very often when you stumble upon an apparent limitation it proves to be otherwise. As is common in modern parlance “Constraint’s often lead to innovation”;

Eric’s cookie tools allows you to find, read set and delete cookies in the bowser. Cookies are associated with a domain address.

The constraint: If we open Single file TiddlyWikis in a browser using a file:// address, I use Timimi as my preferred saver for local wikis; There is a limitation imposed on cookies; As @pmario told me;

A file:// URL is seen as 1 origin by browsers. So the cookie-store accessed from file://path/myWiki1 and file://path/myWiki2 will return the same cookies. … The cookie names have to be different. Otherwise you will get problems

However this apparent limitation can be turned on its head into a An opportunity of unlimited potential.

All wikis in tabs of the same browser (at file://address) share the same “cookie storage”, this allows us to build tools to communicate between wikis in the same browser.

The potential of this depends on your imagination here is examples;

• All file based wikis could share a common multiple entry clipboard, so any thing copied to this clipboard can be pasted into any other tiddlywiki in the same browser.
• Any trigger in one wiki can also copy or paste content into another via the cookies.
• We could build a system of (in browser) interwiki messaging.
• A single file wiki could detect if it is already opened in another tab to avoid contention (but not in another browser)
• We could introduce browser “global” variables in cookies. such as allow the same user ID to be set across all open file wikis.

Please create a new Topic/thread to discuss this in more detail (I will link it here). At most please restrict replying here to “New Opportunities” or “Questions of clarification” about an opportunity posted here".

[Edited] A quick note that if you youse local storage via the Local storage plugin the contents will not be visible between file: sessions allowing private or unique values to be stored. In this case the way you address the local/session storage is as tiddlers, and you can chose tiddler names that will not be saved back to the wiki, but will be saved in local storage.

It may be possible in future to use another storage area called “session storage” to implement something similar to ‘session private cookies’. However I do not yet have the skills to do this.