(it should say "slugify" not "slugifytag")

<:-)

On Thursday, February 25, 2021 at 5:52:14 PM UTC+1 Mat wrote:

> You can "connect" a string like "Windows 10" with a field name by doing 
> slugify[Windows 
> 10] to get "windows-10".
>
> So if you have a tiddler per command you could do e.g 
>
> <$list filter="[tag[OS]]">
>    <$link/>
>    <$vars os={{{ [all[current]slugifytag[]] }}} >
>       <$list filter="[all[tiddlers]has<os>]">
> etc
>
> (not that I have tried this but I think this should work
>
> <:-)
> On Thursday, February 25, 2021 at 2:15:53 PM UTC+1 si wrote:
>
>> Hi all.
>>
>> I'm working on a mini-project for myself that involves representing 
>> tiddlers within a table, and I'm hoping to get some advice on exactly how 
>> to manage the data in TiddlyWiki.
>>
>> The goal of the project is to create a table that lists what certain 
>> keyboard shortcuts do for particular programs that I use. Then I will 
>> automatically generate flashcards from the table so that I can memorise the 
>> shortcuts.
>>
>> A simplified example of the table might look something like this:
>>
>> |          |Windows 10              |Chrome               |
>> |Ctrl + F4 |Close the current window|                     |
>> |Ctrl + W  |                        |Close the current tab|
>> |Ctrl + Z  |Undo                    |                     |
>>
>> I think I will be able to generate the table and flashcards, but I am 
>> undecided on exactly how to store this data in TiddlyWiki. I can't just use 
>> regular table syntax, because this will make it tricky to generate the 
>> flashcards, so its obvious that the data should be stored in separate 
>> tiddlers in some way.
>>
>> My first thought was to create tiddlers for each shortcut (e.g. "Ctrl + 
>> Z"), and add fields named after each program where the value of the field 
>> is the effect of the shortcut (e.g. "windows_10:Undo"). I don't like this 
>> idea because, for example, I also want the field "windows_10" to be related 
>> back to a tiddler called "Windows 10". But this is difficult to do because 
>> of the character restrictions on field names.
>>
>> Anyway just wondering if anyone has any advice here? What's a good way to 
>> represent this type of data in TiddlyWiki?
>>
>> Thanks in advance for you help.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6bb37594-26be-4c89-a3c6-dc9a4aeb4ef4n%40googlegroups.com.

Reply via email to