Yes. Yes-ish. Meaning that the discussion about it is VERY complex.
TBH, at the end of it I’m no wiser than before.
SO I’ll trust you and @pmario and @jeremyruston to do whatever THEY think is best.
TT
Yes. Yes-ish. Meaning that the discussion about it is VERY complex.
TBH, at the end of it I’m no wiser than before.
SO I’ll trust you and @pmario and @jeremyruston to do whatever THEY think is best.
TT
Get your idea bigger.
As a Front-End TW is very well situated.
Why? Because it is all but only the “browser side”.
With minor clarifications (already working in cases) the “browser side” can eat infinite
external data.
SO in 2025 …
1 … munch data more easily
2 … master prompts to AI
TT
Very pertinent post! Why?
Because 2025 is a crossroad. Something new happened in '24 … belligerent AI.
I do think that TW is IDEAL as a quick-front-end-builder for AI, Regex etc.
TT
I’ve spent some time searching the web for TiddlyWiki chess stuff and I didn’t find anything.
TW itself is INcapable of chess play.
As usual there are windows to the White Queen from TW …
See: Create Custom Lucide Icon Sets - #5 by pmario
The Lucide icons sets are basically finished. – There is only one thing left: Handling of Line Thickness using height and weight parameters. That’s the main reason, why I did not publish it till now.
Right. And I doubt there could ever be an exactly “right” answer to that outside of use cases.
In the context of TW I would/will accept as right (enough) your volition.
Getting this done, over, finished, will be useful IMO.
TT
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
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.
i would also get a lot of value from this!
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.
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.
Let me just link a topic that I posted in October:
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
Something else WANTED is fields with multiple lines as native implementation.
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:
[[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 disambiguationPersonally 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.