Hi Mario, > You could, but you may find out, that you may want to create custom > messages in the future too. so imo tb-m-xxx may be the right move. > tbc- using your initials, would be possible too, but I think it's too > similar to tc-... so I added the additional "-".. > pmc would work for my initials, but in favour of consistency I'd use pm-c > :) >
I think this level of complexity is mildly over-engineering, but perhaps that's short sighted. It would be relevant if I wanted to have all classes and messages and other things as tiddler titles in my documentation... but then there are other ways to go about it. This is literally why I prefer to keep the core prefixes, because then their meaning is clear... to anyone not just me... that we're dealing with a certain type of functional construct. But then this would require some verbose naming that goes something like this: *tc-tb-rating* That does not look like something I want. In fact, there is always a chance that existing code and components will at some point clash with new core modules / macros / widgets and what not. Sure, I can avoid that by prefixing everything I do with some shorthand: *<$tb-appear/>* Let me just say: I am going to do that, not going to change any of the classes in the appear widget. If we want consistency, you probably should. ... Only the future will tell, > if your plugins cause naming clashes with user content. Which is why *tobibeer/rate* allows you to specify your own rating field. Honestly, atm, I think I do not want any more or different prefixes. Whomever already has such a field with different content will have to chose another "rating" field anyway... or decide on one rating implementation or another, but not both. Best wishes, 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f2f29f69-1fac-4acc-8a15-c0407584bafb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
