TT
It would be nice to understand why you would do this?
I imagine its only practical with a limited wiki size.
To me all tiddlers are waiting for your use anyway, so why open them to
then reduce them? When you can just open what you want when you want?
Would it help you if you could specify a search on the URL that opens the
Wiki?
Or as suggested use the defaultTiddlers, which can contain quite
sophisticated filters including a search filter. However it may be nice to
be able to bypass this sometimes when loading the wiki, because it
increases startup time.
I have taken to using a compound default tiddlers "[[Home]]
[list[$:/StoryList]]" to always open home then all previously open tiddlers.
If you want something specific to show on opening a wiki you can use
startup actions, the plugin is more powerful than the built in startup
actions, or you can use the $:/config/EmptyStoryMessage which when the
story is empty says emptyMessage={{$:/config/EmptyStoryMessage}}. In a way
this is like placing something on tiddlywikis background/desktop.
Regards
Tony
On Sunday, January 19, 2020 at 1:15:30 AM UTC+11, TiddlyTweeter wrote:
>
> A long, long time ago in Dos I used InfoSelect (it still exists now in a
> different form for Windows).
> The Dos version was rather like TW. It was wholly made of fragments.
>
> A GREAT thing about it was on open ALL fragments were loaded and
> displayed.
> Search (on text) filtered them so you would see only what you wanted.
>
> Could we replicate this with TW? ALL Tiddlers are open on start and search
> auto-reduces them?
>
> Question
> TT
>
>
>
--
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/bb789230-136f-4f90-b213-f82fc4874325%40googlegroups.com.
