I like your thinking here @Justin_H and will look at your idea further, a few quick notes;
- As discussed here RFC: Conditional UI elements Tabs/buttons and more and illustrated here https://conditional-elements.tiddlyhost.com/ I have recently poroposed extending the tabs macro and others UI elements to allow an optional condition field in tabs.
- Just drag the $:/core/macros/tabs to your wiki (Be backup safe),
- Thus your notes tab would have a condition of
[all[current]has[notes]]and it would be displayed if the current tiddler has the notes field and it is “not blank”.
- I recomend you always have some kind of condition or indicator to show tiddlers that will have these tabs, it is importiant to be able to enable or disable it (any additional feature) on a given tiddler, because there will inevitably be tiddlers on which you need to.
One thing I realised is what you are doing is not dissimilar to the tabs in the info button drop down.
- So I was thinking what if your tabs (with conditions) had the tag $:/tags/TiddlerInfo then they would be available in the info dropdown. I know this is not yet what you are after, but then consider;
- What if we then had a tool info dropdown to select any one or more of these tabs on the tiddler itself, as you are doing?
- They will be available in the info drop down and you can add them to the tiddler selectivly.
- To achive this we would have a list field eg; tabs-here containing the tiddler titles of all selected tabs (also a filter), that can be reordered and other methods could be used to add tabs to this list. eg [tags[standard-tabs]]
If you are interested in this idea, let me know and I will work on it sooner rather than later.
[Edited] and we would leverage the body cascade as @Springer suggests.
I have found this is a good mechanisium to implement many of my solutions so are going ahead now.