Hi Mario, Sure, we all understand the basic need, I believe. ^_^
However, the differences arise when it comes to finding the most meaningful basic implementation. I believe the disadvantages to doing this in the tiddler body are enormous, not only because it makes it sooo much harder to change things later on / programatically but also in terms of being consistent and not accidentally changing things. To have consistent "enhanced" fields seems much more manageable. So, what you would define instead of a tiddler template were a number of SemanticBlockViewTemplate / SemanticBlockEditTemplate conditionally displayed when a tiddler matches a filter criteria, e.g. "is tagged xyz". Those templates would define which fields to display and where. However, these templates would only define the contents of the semantic block, *not* the entire View- or EditTemplate! Instead, the View- or EditTemplate would only define a placeholder for where to render semantic blocks, perhaps with attributes that allow to define the order in which to render them, if needed, i.e. for tiddlers that match the criteria of more than one semantic block. You could even skip *all* those extra templates and have the core render a generic semantic fields block depending on any semantic fields defined in some [[SemanticFieldsList]] or [[SemanticFieldsConfig]]. Cheers, Tobias. -- 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/groups/opt_out.
