Using tiddlywiki documentation when contained in a plugin

@jeremyruston thanks that plugin $:/plugins/tiddlywiki/tw5.com-docs is a useful step to what I need.

  • However there are a few tiddlers I don’t want within that package such as $:/StoryList $:/DefaultTiddlers $:/favicon.ico $:/SiteSubtitle $:/SiteTitle $:/SplashScreen etc…

Re your notes:

  • By the way I have already investigated many of the ideas in your notes of my own accord, and have working solutions. I can provide more information if you are proceeding with some of this, or interested.
  • However it does not introduce the mechanism I am looking for which would;
    • Allow us to avoid editing the existing documentation tiddlers.
    • Let us leverage the mechanism in other use cases, content sharing and plugins.
  • This would solve the documents issue, but then changes may be quite comprehensive given we need to add [all[shadows+tiddlers]tag[... on all lists.
  • My called for mechanism, would eliminate this requirement.

I can see from your notes, you are thinking about placing documentation “to one side as a reference”. For me I want to keep them visible in the user namespace, in fact I want to treat all the subtiddlers in a plugin as if they were tiddlers, without overriding them.

Can you envisage a mechanism that could allow us to nominate plugin(s) by filter and have its subtiddlers appear as tiddlers?

  • perhaps a method by which a filter can include shadows in the group we would call tiddlers?

A way to make such a mechanism?

On reflection it may be possible to achieve what I am after by changing the is, all and default filter operators, to include these shadows as tiddlers.

  • With the help of others, I recently successfully hacked tiddlywiki, to classify other title prefixes as is[system] which is similar. Effectively to create new system namespaces.
  • The mechanism I am now looking for, is possibly it’s complement, to bring selected shadow tiddlers into the non-shadow “tiddlers” set.

Actually I would love to discuss what I have found in this exploration. We could for example use a separate namespace for documentation tiddlers and flick a switch to toggle them between being system, or non-system tiddlers, thus which lists there appear in etc…

  • If we had a way to also switch a set of titles from belonging “in the shadows” to being “in the tiddlers set”, it could be very useful, for example;
    • to make plugins and their subtiddlers instantly searchable in the standard search.
    • To nominate system tiddlers such as $:/ControlPanel and $:/AdvancedSearch to come forward into the group of “tiddlers”.
  • If we do this we can use the project name “Out of the shadows” :nerd_face: