As you sai Mario, I try to use as many core classes as I can. But sometimes, this is not possible (for example , radio buttons in the advanced search are "deformed" due to the input core class), that's why I'm asking how should we manage this. I'm very very bad at establishing procedures and naming conventions, that's why I prefer to ask.
The plugin name seems too long to me, but if it is common (and clear) maybe I could stick to it, but I would like some kind of "official naming convention". Regards. El lunes, 29 de septiembre de 2014 13:47:01 UTC+2, PMario escribió: > > On Monday, September 29, 2014 10:56:51 AM UTC+2, Danielo Rodríguez wrote: >> >> El domingo, 28 de septiembre de 2014 10:58:24 UTC+2, PMario escribió: >>> >>> I think instead of using tc-three-columns we should use uc-three-columns >>> The reason is: tc- means TiddlyWiki Class ... so it suggests, to be a >>> core class. But it isn't. This will cause support problems in the future. >>> uc .. User Class. >>> >> >> Following this logic... should we then use pc- for plugin classes? >> > > You basically can use, what you want, as long as it is different to the > core classes. > > Plugins should try to use existing core CSS as much as possible. So that > no additional stylesheet is needed. and plugins can work with different > themes. > > If you really need your own styles, you can skip the "pc-" prefix and use > your plugin-name instead. This was common practice in TWc and it worked > well. > > eg: TagSearch plugin used ".tagsearch ...." classes for the wrapper > element. So there are no side effects to the rest of the UI. > > -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 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.
