Hi Jeremy On Thursday, July 10, 2014 12:23:24 PM UTC+2, Jeremy Ruston wrote:
The list mechanism could be used to order the tiddlers identified by their > layout field, but I'm not sure that all of this is worth it. What's the > advantage over using tags? > In my case, the system tags I used unnecessarily cluttered the UI with meaningless tagpills. This is not usually a problem for layout tiddlers, as the tagpill swarm is not visible in the UI (other than when the layout tiddler is shown in the main story river.) In my application I set out to reserve all tags for the user, so that all tags displayed in the main story river had semantic meaning to the user. An alternative would be to remove system tags from the standard tagpill swarm and tag editor, and move them into a tab in the 'info' button. My original concern about a proliferation of system tags applies also if we > use the layout field: we'd have a proliferation of possible values for the > layout field. > My idea was to reserve system tiddlers for a reduced and less confusing list by moving the more specialised settings into a field. This, however, introduces problems for the ordering of the standard layout. I think that ordering and manipulation of lists of tiddler titles other than in the 'tags' field would be of general utility. Ideally, any field should be capable of being used like the 'tags' field i.e. a facility for alternative and multiple 'tags' fields. regards -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
