Most Wanted 2025

TW_Tones · January 11, 2025, 6:17am

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.

Mario · February 9, 2025, 12:50pm

8 posts were split to a new topic: Prune TW Core Functions in a Reversable Way (Most Wanted 2025)

XLBilly · January 17, 2025, 11:14pm

I think this one is worth to be implemented. This would replace the awkward way of using the wikify widget to pass indirect parameters to macros in filters.

github.com/TiddlyWiki/TiddlyWiki5

[IDEA] Add macro operator

opened 12:01PM - 08 Nov 24 UTC

Leilei332

The current implementation of using macros in filters isn't good enough: ``` … <$list filter="[<mymacro param:'value'>]"> ... </$list> ``` It isn't able to use variables or textreference as a parameter of the macro. I think we had better introduce a macro operator so that variables and textreference can be used as parameter (like the function operator). For example ``` <$list filter="[macro[mymacro],[value]]"> ... </$list> <$let template="DDth MMM YYYY"> {{{ [macro[now],<template>] }}} {{{ [macro[now],{$:/config/NewJournal/Title}] }}} </$let> ```

chaosweaver · January 18, 2025, 8:12am

Personally, I wish for some added filter operators to handle JSON array manipulation (like push and pop, for instance)…

(An idea proposed in GitHub issue #7840…)

github.com/TiddlyWiki/TiddlyWiki5

[IDEA] json operators for array manipulation: insert, remove, push, pop

opened 09:30AM - 15 Nov 23 UTC

rmunn

**Is your feature request related to a problem? Please describe.** The new [jso…nset operator](https://github.com/Jermolene/TiddlyWiki5/pull/7742) allows modifying an array at a specific index, but doesn't easily allow operations that would change the length of the array: adding or removing an item, for example. In order to insert an item into a JSON array, you'd first have to turn it into a TW-style title list with `jsonget`, then manipulate the list, then do a rather complicated operation to turn that list back into JSON format, then finally use `jsonset:json` to put it back in place. **Describe the solution you'd like** It would be far nicer to have the following operators available: - `jsoninsert` - takes a series of indexes (like `jsonset` does), which must lead to an array and a specific index `i` within that array. The item to be inserted is then placed *before* `i`. (If `i` is equal to the length of the array, then the item gets appended to the end of the array, just like what `jsonpush` below does). Returns the new JSON value with the item inserted. - `jsonpush` - takes a series of indexes which must lead to an array. The item to be inserted is appended to the end of the array. Returns the new JSON value with the item inserted. - `jsonremove` - like `jsoninsert`, but *removes* the item at index `i`. Returns the new JSON array with the item removed. If you need the value of the item, do `jsonget` or `jsonextract` first before doing `jsonremove`. - `jsonpop` - like `jsonpush`, but *removes* the last item of the array. Returns the new JSON array with the item removed. If you need the value of the item, do `jsonget` or `jsonextract` first before doing `jsonremove`. Note that negative indexes (as per https://github.com/Jermolene/TiddlyWiki5/issues/7839) should help here: `[<jsonarray>jsonget[-1]]` would fetch the last item. **Describe alternatives you've considered** Technically all of these can be done already using `jsonget` and `jsonset`, but the filter operations to achieve that result would be quite tedious to write, and rather inefficient to boot. **Additional context** In https://github.com/Jermolene/TiddlyWiki5/pull/7742#issuecomment-1740722105 there was some discussion about whether `jsonpop` should return two results: the removed value, and the resulting list. I think it's best to have `jsonpop` just return a single value, which is the list minus its last item; getting the value of the last item would be done with `jsonget[-1]` first, and the `jsonpop` operation would be a separate step. That would avoid the complication of handling the two return values in a filter run. (You could get at one of them with `nth`, but what would you do with the other one? You'd end up having to store the result in a variable anyway).

Mario · February 9, 2025, 1:15pm

2 posts were split to a new topic: Encrypt Single Tiddlers (Most Wanted 2025)

Mario · February 9, 2025, 12:57pm

5 posts were split to a new topic: Spreadsheet Like Functionality for TW (Most Wanted 2025)

stefan_from_germany · January 23, 2025, 10:17pm

Database functionality

@Scott_Sauyet provided in this post Multi level depending tags? a solution of simple database functions.

It would be a great idea to develop it further and to integrate it as plugin or native function.

Mario · February 9, 2025, 12:58pm

15 posts were split to a new topic: MindMap Functionality for TW (Most Wanted 2025)

tomzheng · January 27, 2025, 6:51am

In addition to making modules more decoupled from each other like @Mohammad said, making each module a common js library that can be used by all js software developers. Also want tiddlywiki to be front-end headless software. Only provide api on the browser side. no involvement in interface design.

Except ui stripped out. I also hope that the data storage side is also stripped out.

BTW, a question. Why is the data storage format [] and why not {}? Is it because of performance reasons?

Mario · February 9, 2025, 1:02pm

7 posts were split to a new topic: Create Interactive Checkboxes Using Wikitext Syntax (Most Wanted 2025)

Mario · February 9, 2025, 11:52am

3 posts were split to a new topic: TestCase Widget Used as Unit-Test - (Most Wanted 2025)

Mario · February 9, 2025, 1:18pm

I did move posts with several replies or partial solutions into their own threads, to make this thread easier to read.