Let me just link a topic that I posted in October:
1 Like
I have another wish, which should not be too difficult to accomplish:
Modals should also be set to close when clicking anywhere outside them.
Isn’t it already available…https://tiddlywiki.com/prerelease/#Modals
check the mask-closable option
2 Likes
Something else WANTED is fields with multiple lines as native implementation.
1 Like
What do you mean ?
Being able to write a field with multiple lines without writing it manually in a text area ?
Or something else completely ?
I think he mean displaying textarea instead of input for editing a tiddler. This is already possible: https://tiddlywiki.com/#Customizing%20EditTemplate%20field%20rendering (demo)
Aliases have long been something I have wanted. The best I see is to create a tiddler with the “alternate” name and link to the “main” one, but I would rather some seamless symlink-like experience.
You may already be aware, but I just wanted to note that while there’s no core mechanism for aliases (yet?) we do have at least two plugins that tackle the issue in slightly different ways:
- @mklauber’s Aliases: uses normal link syntax; generates automatic disambiguation pages as needed
-
@pmario’s uni-link: uses
[[alias|?]]syntax; greater flexibility in terms of choosing the field displayed as an alias link; includes some additional filter operators for working with alias links; no disambiguation
Personally I can’t live without some of the secondary features offered by uni-link, but the Aliases plugin may be closer to the sort of seamless integration you’re looking for.
1 Like
I will give those a try, thanks!
Another one occurred to me - it would be nice to be able to take a block of dynamic wikitext (with widgets, macros, etc.) and replace it with a static version. So <$list ..></$list> would be come Tiddler1 Tiddler2 ...
My main use case is that there are times where I built up something from a dynamic view and want to snapshot it and I don’t want the snapshot to keep updating. It would also save on computation cost by “downgrading” when the dynamicisim is no longer needed.
I want to have all fields possible to use with multiple lines.
The solution from @telumire should be available to all fields 
Chopping of dynamic lists would mean amputating the legs to loose weight. The list widget is one of tw’s superpowers, and for me dynamic organization saves weight.
If a developper wanted to do, he sould he should try to add wings and add an entire featherwiki export tool to shrink the wikistrucure to 58kbit.
I do not know a usecase where a wiki has to be that small. TW easily fits into an email. The only limit I could think of is the size of a qr…which is much smaller.
But perhaps this size would be the chunk that could be used to hide critical information in a steganographic way. But again here you’d need an unwrapper on the other side to do the work.
I think one of my dearest wishes would be three xtra feature’s for the whiteboard plugin - or anything that brings us closer to a canvass.
Since there is much talk about obsidian - obsidian’s whiteboard would be the only thing that makes me look enviously to the dark side.
So far the ability to really work with Tiddler-Content is too limited in the whiteboard. @linonetwo -if you find the time:
Could you please add
- an Add Tiddler Button that opens a searchfield to choose a tiddler to add or to write the title of a new Tidddler if nothing is found in the search.
- The ability to open a tiddler as a modal above the Board in order to edit the content, best together with the ability to change the style.
- The ability to switch between Titleview and Bodyview (or perhaps even a customizable viewtemplate for each tiddler - with the Titleview being able to show the content as a modal on click.
- The ability to zoom to a tiddler by clicking.
I think this could transform the whiteboart into the absolute TiddlyWiki Supertool.
I’d love for the Zoom Story View bug to be fixed. I tried looking into it a while ago but I couldn’t determine why it wouldn’t zoom to the top of a new tiddler.
It seems to occur if you’ve scrolled down on the current tiddler, then click on a link to a new one, and the new one appears scrolled down midway instead of loading with the title at the top of the storyriver.
2 Likes
This is perhaps a bit niche, but I’d love an easier way to set a particular tab configuration when navigating to a tiddler. I think it could be particularly useful when writing documentation/demos, as we currently see tab paths like this even in the official docs:
“You can use an $action-setfield widget to set the tab states to the appropriate values!”
Yes… but the <<tabs>> macro stores its state in a <<qualified>> system tiddler by default, so unless you’ve set a custom state parameter for each tabset you want to manipulate, you have to find the appropriate state tiddler before you can do anything with it — and there’s no human-discernible pattern to the titles. I end up using custom state tiddlers for most of the tabsets I build myself, but it’s not practical to change $:/core tabs this way.
“You could just link directly to the tiddler in question…”
Sometimes! The example above could indeed be simplified with a direct link to $:/core/ui/ControlPanel/Parsing. (Thank you, Link to Tabs! How I wish you were pre-installed on TW-com.)
But I use a lot of templates, and a lot of my tabs don’t correspond to any extant tiddler; they’re just a view template providing a particular view.
“If you weren’t overusing tabs so much, you wouldn’t have this problem…”
Possible — nay, likely. But I don’t intend to stop.
1 Like
You are welcome – Since Link-to-tabs and Trails do not need to restart they are easy to install from the browser’s “Bookmarks Toolbar”
My TW-com looks like this. I drag & drop import the plugins.
I did create an experimental PR which tried to make the existing ControlPanel tab-states more accessible. They main problem is “backwards compatibility”.
To make it compatible it has to be complex. More complex than “allowed”. Tabs qualified states need 3 different ways to evaluate them, which makes the needed filters complex.
2 Likes
Thanks for the PR link! I should have guessed that you would have considered this before. I thought it was quite a clever approach, though Jeremy’s observation
it only works for a single tabset within a tiddler.
does mean it probably wouldn’t have covered all my needs. I suppose there isn’t any neat solution, really.
Are you using bookmarklets there? I should really set some up… I find myself going to grab one of your plugins at least once or twice a week.
Here’s a start:
This is the macro I use in https://plm.tiddlyhost.com, this make it easier to locate where the settings for my plugins are.
1 Like
Its not broken, its the way it works, and its not always nice. The title will be at the top if the tiddler is longer than the screen. It does not scroll all the way to allow visibility of what comes before it.
There are a few ways to change this, the simplest being extra white space in a tiddler tagged below story.
I had to think on this idea of @Mohammad first… and it took me some time to understand the idea is great. I think Tiddlywiki is a great prototyping tool, and the expanded features made it better in this. It is a Swiss-army knife, but sometimes I only need the tweezers.
In most of my wikis, three times more functions than I need.
Here a “coreshrinker” could be very helpful. Of course there is already @Flibbles uglify but the coreshrinker could go farther. As I understand, the process should be reversible. Just drag your shrunken wiki on the current updater and get back your Swiss-army-knife.
1 Like