> > I would propose the ability for either of a message / tooltip to be > displayed or a css class that indicates whatever needs to be respected for > a given field. There could be a dedicated namespace which the template > would look up so as to fetch that tooltip or class from a plugin-defined > shadow or user-defined tiddler. >
These could even follow the system-tagging paradigm, whereas instead of actually placing these tiddlers into that namespace, all that is required was to tag those tiddlers with the necessary namespace... which doesn't have to ship with the core, but can be assigned anyways. It could also be a *$:/tags/Fields* namespace, whereas each tiddler tagging to it would have to define these fields... - fieldname - tooltip - class - ... whatever else the field handling widgetry requires or can be extended with 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 tiddlywikidev+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywikidev@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
