Welcome back @BurningTreeC I value your contribution to the community and tiddlywiki immensely.
- This is tricky one, because I belive it is an importiant solution that allows tiddlywiki to operate in a particularly useful way. I like that is is available in the stable of solutions, but beyond learning how to use it, I have not yet needed what it does, for myself or posible clients, but then I work a lot in the possible, rather than the practical.
- This may be similar to mentat, streams, kanban and other inspired solutions.
- I would however be sad if it were not available.
I think I raised it before, but provisioning it with some css that better scales the titles out of the box and by number of columns, so it scales is my only desire from memory.
- Unless you just want an excercise to learn these new features I would not bother reengneering the multi-column layout just to use the new features. If you did it would no longer be compatible with earlier versions (not that importiant).
- I suspect as you learn about the TW 5.3.x improvments you will start to see new oportunities, but until then it may not be profitable use of your time. Why do I say this?, because, to me, the key advantages of 5.3.x is the opening of new development and code patterns in TiddlyWiki script going forwards, since you have built multi-columns already, there is less value reengineering it.
- I and a few others have already posted extencivly since the release of 5.3.0 so have some search and browse time in talk.tiddlywiki and dont hesitate to ask the community.
- I could write something for you but it would be quite a tome.
- Some quick tips
- Functions and custom operators from them, are fantastic for modularising, reusing and naming filters, and have a nice benifit that when used as a
<<variable>>output plain text. - Procedures to me so far are just macros with less parameter substitution.
- I recently discovered a gap here
but the old macros remain of course.
- I recently discovered a gap here
- The parameters widget is useful inside tiddlers, macros and custom widgets.
- and the new $params=varname is revolutionary because you can retrieve all parameters named or otherwise, but I want to take this further Further use of $params with $parameters widget
- The ability to write new custom widgets or intercept existing widgets has immence value, along with the $fill and $slot widgets (although they look verbose).
- Functions and custom operators from them, are fantastic for modularising, reusing and naming filters, and have a nice benifit that when used as a
- Others with a more detailed understanding will have a technical view on this. I would say not specificaly “more performant” but there are more opportunities going forward to improve performance, but we need only do this if we face an intractable performance issue and I have not yet seen one.
- As I alluded to earlier I think the value of 5.3.x is it breaks many barriers, and introduces the possibility of new and better code patterns. Its about the future rather than the past.
Welcome back and I hope this is a kick start.