On Thursday, September 26, 2019 at 10:21:14 AM UTC+2, TonyM wrote: ... > but just as tiddlywiki already has the type field for its own tiddler > types the best way for a designer to handle the example of classifying a > large number of tiddlers as words/Vorto is with a field be it containing a > tiddler-type value or just an if exist "word" field. Why because it does > not use a heavily flexible mechanism for tags to do a simpler job, and in > large quantities this makes a difference. >
I think using the tiddler-type field would be a solution here, since it wouldn't need to use the <$list filter="[all[current]tag[xxx]]"> .... *hack*, to create a custom ViewTemplate or / and EditTemplate. So the "WordTemplate" could be much simpler. The TW tiddler-type field is used to specify a MIME-type <https://en.wikipedia.org/wiki/Media_type>. It is possible to create your own "vendor specific" (like text/vnd.tiddlywiki) or "personal" (text/prs.dictionary) types, but you need to follow some rules. Personal or vanity tree > > The personal or vanity tree includes media types associated with non > publicly available products or experimental media types. It uses the prs. > tree prefix: > type "/" "prs." subtype ["+" suffix] *[";" parameter] > > Examples: audio/prs.sid, image/prs.btif. > > from Wikipedia > So a text/prs.dict.word;language=en-EN or something similar, would be a possibility to work with a specification as described in the OP. The problem is, that we don't have good end-user support for content like this in TW at the moment. just some thoughts. -mario -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/18bfb65f-8267-4ba3-acfc-a2aa4e86251d%40googlegroups.com.
