Most Wanted 2025

, ,
#19

TW itself is INcapable of chess play.

Just like my posts in the thread you’re linking to show, I’m not interested in playing chess in TiddlyWiki. Just in storing chess games recorded in PGN format, being able to visualize, navigate, annotate and search them. This is chess database stuff rather than chess client (as in either frontend to an engine, like Stockfish, or an online chess server like FICS or Lichess) functionality. Think something a la Scid.

Of course, such a wiki would have to make use of a library that “understands” the rules of the game and can process PGN and FEN, like the aforementioned chessboard.js

1 Like
#20

Right.

IMO all of this is about Interface … TW is likely the best suited start-up to cope with this.

We need, maybe, better understanding how TW can control anything controllable.

#21

i would also get a lot of value from this!

1 Like
#22

I would like to see a well documented path for other open source projects to bring their tools into tiddlywiki as a platform to both demonstrate, use and prototype.

Many projects are designed to integrate with website, html and/or JavaScript environments. For good reason they need to behave with TiddlyWiki especialy when interacting with TiddlyWiki in the scope of a tiddler or across tiddlers. This work is done time and time again bringing in different tools and libraries of features, some of which have become part of or near the core such as Codemirror, fonts and a lot more.

  • With appropriate documentation to allow intergration without needing to be a TiddlyWiki core wizzard many different projects may see TiddlyWiki as a flexible front end or platform for their project and be motivated to put in the work for their own benifit and to extend the posibilities with TiddlyWiki.
  • Lessons need to be learned and documented so newer versions can be introduced and updated in line with each projects own development time line, with minimal intervention.
  • This could result in some tooling in the TiddlyWiki core to facilitate this reducing redundancy and bloat (Eg introducing almost identical libraries for say date handling)
2 Likes
#23

This one:

If merged, this will allow us to make plugins translatable. I would like to make TiddlyDesktop translatable after it was merged.

And this one:

Which improves tiddlywiki’s dark mode switching.

5 Likes
#24

Let me just link a topic that I posted in October:

1 Like
#25

I have another wish, which should not be too difficult to accomplish:

Modals should also be set to close when clicking anywhere outside them.

#26

Isn’t it already available…https://tiddlywiki.com/prerelease/#Modals

check the mask-closable option

2 Likes
#27

Something else WANTED is fields with multiple lines as native implementation.

2 Likes
#28

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 ?

#29

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)

#30

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.

#31

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
#33

I will give those a try, thanks!

#34

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.

How to disable all lists update on every click to make Tiddlywiki work fast with 10000+ tiddlers?
#35

I want to have all fields possible to use with multiple lines.
The solution from @telumire should be available to all fields :wink:

#36

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.

#37

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.
WhiteBoard plugin
#39

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
#40

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:

image
image816×255 11.4 KB

“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. :wink: But I don’t intend to stop.

1 Like