Hi PMario,
This was one of the possible solutions I was considering. I went with this
method to prototype out stuff. It worked well, thanks for the suggestion.
I'm going to combine it with Mat's solution (down thread) for some neat
dynamics.
Best,
Joshua
On Tuesday, June 27, 2017 at 8:58:54 P
Hi Mat,
That is a really neat solution!
I am doing something similar with tagging to allow a centralized View and
Edit Template tiddler to dynamically transclude the appropriate View and
Edit templates for each of my "CampaignWiki Tiddler Types" : Player,
Character, Company, Faction, Location,
@Joshua, you may peek at my answer (which I believe is exactly what you
want) only if you first promise that you'll share something from your final
creation that is of joy or benefit to others here ;-)
http://hidefields.tiddlyspot.com/
<:-)
--
You received this message because you are subscri
This isn't directly related to your question, but in my experience it is
better to separate the visualisation and data parts. I normally have many
data tiddler that have as many fields or indexes as needed and then have
one viewer tiddler where you select what you want to view. It lets you
deci
Hi Joshua,
IMO you just need to place your custom fields: contact.*, character.*,
ruleset.* into your own namespace.
eg: rpg.character.something, rpg.ruleset.*, rpg.* ... Can you see it?
Now your filter can be: [all[current]fields[]!prefix[rpg.]] +[sort[title]]
short test: <>
you can have / h
5 matches
Mail list logo
