Hi Tobias, A $:/type tiddler, which will be used as tag. This tiddler defines the >> caption and the icon. >> > > I find it rather confusing that this would be a tag. > Is that just a design choice or would it be a necessity? > All in all, there would only ever be one *mt.type* to a single tiddler, > or not? > > Or is it a tag to simplyify assigning it, to assure the user selects a > valid value ...if he ever does so, manually. >
Its a design choice. And I have several reasons for that. Previously, in http://tesis.tiddlyspot.com/, I used the field *catégorie* for the same purpose, but it was a pain in the neck. Tags are much easier to use, for instance in list filters; they are easier to assign, as you point out, and other reasons… We could do the same with field instead of tags, or have both, but do not consider going that way until the plugin is stable enough. The macro <<tabContents>> uses the tag caption and icon to create the >> heading of the tab, so it's imperative to fill the contents.tag with the >> type tiddler you created. >> > > I think it would be helpful if all these components would come prefixed, > e.g. > > <<mt-tab-contents>> > >> 1. Tabs fields: fields like *filter* and *template* have changed to >> *list.filter* and *list.template*, and other fields have been added. >> >> Perhaps use a more specific *mt* prefix, e.g. *mt.filter*? > > Yes, it might be a good thing to avoid interferences with other macros. Regards, Alberto -- 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.
