I’m trying to create a new version of the TW Mathcell project, including scalable tables (up to 26×100, for this i want to use data dictionary tiddlers vs fields as i find it annoying having 2600 possible field values added to the drop-down every time I add a field, the issue is the indexOf() call only works for fields not for indexes/dictionaries the dev site shows an example of getting tags and titles and fields https://tiddlywiki.com/dev/static/TiddlyWiki%20Architecture.html but no way to look through a dictionary, is this even possible? Any ideas? Having a potential tiddler with 2,600 field values seems a little insane to me.
1 Like
Generally it’s better in the long term to use wikitext than to use JS.
So if you had a data dictionary called “Data” with the following items:
house: huis
dog: hond
cat: kat
Then you could do the reverse look-up (indexOf equivalent) with
<$let value="kat">
<$list filter="[[Data]indexes[]]:filter[[Data]getindex<currentTiddler>compare:string:eq<value>]">
</$list>
</$let>
There could be complications, of course, if a value is associated with more than one index.
Of no help whatsoever, but YAY! Can you make it Evans formula compatable? Pleeeeeeaaasseee?
Either way. Looking forward to whatever you cook up.
I think it’s worthwhile designing such a solution to permit the use of a data dictionary, CSV, JSON or fields on toddlers as the data source.
if you have a problem with too many items in a dropdown fix that, such as use system fields or exclude fields from the dropdown. perhaps provide a custom dropdown.
1 Like
I think this may be my best solution but it will sorta break my existing framework i could exclude anything with my custom prefix and maybe provide a way to view the fields (perhaps in tiddler body) or create a new tiddler type all-together to accomplish this. Thanks for the idea on hiding select fields, not ideal but if memory serves they parse faster than dictionaries anyways