I hadn't run into the issue with duplicate names yet, but when I get to 
class archetypes I'm going to need dozens of duplicates so thank you! Saved 
me from a future headache. :)

On Thursday, 21 October 2021 at 09:20:36 UTC-4 [email protected] wrote:

> I use tiddlywiki's for a lot of rpg stuff and it can be a challenge to 
> come up with unique name for some of the tiddlers and fields. If you add a 
> caption field to a tiddler the table of contents macro will display it 
> instead. That can help clean things up.
>
> On Wednesday, October 20, 2021 at 10:09:45 PM UTC-4 [email protected] 
> wrote:
>
>> That's good stuff.
>>
>> If you like to tag content for a menu to be automatic reflect the 
>> content, the built-in stuff in TiddlyWiki is right awesome.
>>
>> Me, I tend to like control on my menus, adding menu items which then take 
>> me to the content.
>>
>> It is a bit like one approach is bottom up, and the other is top down.  
>> (Not sure which would be which.)  Either way equally good, probably a 
>> difference in right-brain versus left-brain thinking.  Maybe more so the 
>> purpose of the menu.  Meh ...
>>
>> That details thing I suggested, that was very rough around the edges, 
>> just to throw the quick thought together.  It could be oh-so-sweet with 
>> some proper design.  But only of value if you're of a 
>> "menu-first-towards-content" mindset versus "content-first-towards-menu" 
>> mindset.
>>
>> Either way, so much fun !
>>
>>
>>
>> On Wednesday, October 20, 2021 at 10:30:23 PM UTC-3 [email protected] 
>> wrote:
>>
>>> Thank you both so much! Either option seems like it'll do what I want 
>>> with a bit of adjusting! It's hard to believe I was overcomplicating this 
>>> so much, but I suppose it's as they say and all of the world really is just 
>>> a nail when all you have is a hammer. I guess now I just have to decide 
>>> between having the triangles that I want or having the list easily expanded 
>>> using the tags system.
>>> [image: AlternativeCapture.PNG]  [image: AlternativeCapture2.PNG]
>>> Using details has this quirk that the em2 margin applies to everything, 
>>> though I've fixed it by removing the * from .indent_details  *{
>>> [image: TOC.PNG]  [image: TOC2.PNG]
>>> Using Table of Contents gave me numbers that I thankfully already knew 
>>> how to remove from my past muddlings: 
>>> <style>ol {list-style-type: none;}</style>
>>> <<toc-selective-expandable "TableOfContents" "sort[tocpos]">>
>>> tocpos is just a value I made up so I can assign value 1 to Home and 2 
>>> to Character Advancement, a bit messy but it seems I can use decimals if I 
>>> need to jam something in the middle later. This way I get whatever 
>>> arbitrary sorting I want instead of going purely alphabetical (looks like 
>>> it uses the alphabet for tie breakers which is nice). Unlike with 
>>> [[Home|SQPFSRD]] that I can put in details I had to make a Home page to 
>>> contain {{SQPFSRD}} and add that to my table instead, but most of my pages 
>>> won't need this treatment (I could just rename the page, but having this 
>>> option as well is reassuring).
>>>
>>> Leaning towards Table of Contents purely for how much less work it is. I 
>>> suppose now my goal is figuring out how to style the ToC so that it doesn't 
>>> indent as far, and maybe getting it to use triangles somehow.
>>>
>>> On Wednesday, 20 October 2021 at 20:33:16 UTC-4 Eric Shulman wrote:
>>>
>>>> The TiddlyWiki standard distribution includes a set of macros to 
>>>> display a hierarchical "Table of Contents"
>>>> https://tiddlywiki.com/#Table-of-Contents%20Macros
>>>> https://tiddlywiki.com/#Table-of-Contents%20Macros%20(Examples)
>>>>
>>>> For your purposes, you probably want to use the 
>>>> `<<toc-selective-expandable ...>>` macro.
>>>>
>>>> enjoy,
>>>> -e
>>>>
>>>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a5a4e6e6-e150-482f-8e55-b04feb1f1c36n%40googlegroups.com.

Reply via email to