I believe my suggestion was not much about css at all but about the
functional bit that renders fields and how to store field-meta-data. Easily
hinding unused fields via css on definition lists is but one aspect of that.
As said, there could be field-definition tiddlers that define...
- field-name
- caption
- to have two fields displayed as "author", only just that one would,
in-fact be "plugin.foo.author" under the hood
- which should also be indicated somewhere
- tooltip / help
- data type (!!!)
- etc...
And then widgetry could construct it's logic around that.
Also, certain system-tags, e.g. *$:/tags/Field* could globally enable or
disable fields. On top of that, there could even be two fields at each
field-definition-tiddler that specify via filters for which tiddlers a
field is to be displayed in either view-mode or edit-mode... and all the
list-before and list-after handling, etc.
Best wishes, Tobias.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.
