I have long sought to find easy to use ways to handle tiddlers having many roles, types and uses.
- Here I outline a design approach / code pattern, I am working on, at the end I seek ideas and input.
- I will publish a demo shortly.
I have designed a card system where multiple cards are displayed on tiddlers if they meet various criteria, using a display-filter, and these cards provide information pertaining to that criteria. A simple example may be on a tiddler that is also a tag, where the card provides a tag pill and optionally lists all tiddlers with that tag. For now my cards include;
- Field Tiddler
- Flag Tiddler
- JSON-data tiddler
- System tiddler
- Tag Tiddler
- Tiddler card
- Configuration Tiddler
- has-non-standard-fields card
- May apply a form here
- Missing Tiddler
- Shadow tiddler
- Tags as fields
You can see how these are tiddlywiki and system oriented.
Well in recent discussions about allowing tiddlers to have one or more roles, a list as opposed to a single role, it seems a similar mechanism or included in the above would be ideal for roles as well. Simple examples include some of the above;
- A contact tiddler
- A country or city tiddler
- A webpage tiddler
- A report tiddler
- A to do item
- A Project or project item
- A question tiddler with an answer card
and many many more.
For any tiddler, most likely only one or a few of these roles will apply, but along with the cards above you can see that the number of items (Cards and Roles) to display on any given tiddler can quickly grow.
Questions then arise;
- What order should they appear in, across different combinations of roles/cards
- When and how do we show/hide some cards/roles via local or global settings
- How to we show there are hidden roles or cards the user can select to view
- When and how do we switch to cards/roles with less whitespace, ie make the display more compact.
One reason this cards and roles idea has credence is as a designer I control the way this works without needing to use the standard cascades, I can embed all the logic I want without needing to leverage the view cascade beyond including the roles or cards handling.
- I do hope one day to share these methods with the community.
- I want to use it to support some of the solutions I have being discussing lately
- No touch flags
- No touch Notes
- Field and field-type handling
- etc…
Please tell me what you think about this approach
Please tell me if you have any strategies for handling multiple blocks of content on a single tiddler
An initial demo of cards is here https://field-handling.tiddlyhost.com/