Setup for view template for species (solved)

[TerryTigre]

Due to the excellent suggestion of etardiff in an earlier thread, about using view templates:

Trying to find a way to list skills if they have the same tag as a job(Solved)

If this is code you’d like to reuse, I’d recommend moving it into a procedure (or macro; not a function, as those display plain text, not HTML) once you’ve finished tinkering so you don’t have to repeat the same code on multiple tiddlers. Alternatively (and this is usually my preferred approach), you could move it into a separate ViewTemplate tiddler. For instance: title: JobTemplate tags: $:/tags/ViewTemplate text: <% if [<currentTiddler>tag[Job]] %> your code goes here <% endif %> The conten…

I have started to build one for the species, and the first results look promising, as I can make checkboxes appear in the species tiddler without editing the species tiddler itself.

However the devil is in the details in this case.

What I want is to organise the info by species, so that every species has in order:

History

Preferred environment

Description

special rules

Abilities (may get renamed later)

… more species details to be added later

and finally

Because (that gives the reason to choose that species).

This should work with check boxes in the species tiddler to show the details when opened and only the checkbox when closed.

This part works already.

The other way to view the data would be by category, for example a list with a link to the descriptions and only the descriptions.

This should also be possible as I do something similar in the species chapter already, where there are links to every race.

All the data should be in separate tiddlers like BecauseAelfar for example, or HistoryAelfar.

As the exact names of the tiddlers are known, it should be possible to provide either a link or a transclusion to them.

I have tried both, and while it is possible to use {{BecauseAelfar}} hardcoded and get the results I want, that defeats the purpose, as I would need a long string of <% if %> etc that way. And the playable species might grow or shrink.

when trying to do it using links instead (not my preferred way as the new tiddler may be opened either above or below) I can get a link to Aelfar to appear, but not a link to BecauseAelfar. This might be because i strip the R- prefix and then try to make Because appear in front.

Now finally my Questions.

Is it possible to use the view template to transclude tiddlers based on the species name and a fixed prefix? If the stripping part is the problem then BecauseR-Aelfar would be fine too.

Or if the above is not possible, are links possible, maybe by using a field of the species tiddler like for example BecauseLink with as value [[BecauseAelfar]]?

Or should I abandon the whole view template idea and use the checkboxes in the species tiddlers itself? This would work for sure, but it is a lot of duplicate data, and it would make it harder to compare species.

here is the view template code:

<% if [<currentTiddler>tag[Species]] %>

<$checkbox field="Because" checked="yes" unchecked="no"> Show the reason to choose this Species </$checkbox>

<$reveal state="!!Because" type="match" text="yes"> 

Choose <$text text={{{ [{!!title}removeprefix[R-]] }}}/> because:

{{BecauseAelfar}}

</$reveal>

<% endif %>

Any help would be appreciated. And it is likely only a small problem of getting the right way to assemble the needed tiddler name.

[EricShulman]

Instead of the “short form” transclusion syntax ({{BecauseAelfar}}), use the <$transclude> widget which allows you to construct the desired tiddler title, like this:

<$transclude tiddler={{{ [{!!title}removeprefix[R-]addprefix[Because]] }}}/>

enjoy,
-e

[TerryTigre]

Thanks once again. That worked great. Do you mind if I list you as one of the contributors in the Designer Notes, as you have helped several times already?