On Wednesday, November 19, 2014 1:25:06 PM UTC+1, Tobias Beer wrote: > > Hi Mario, > > >> But the need to "completely" re-design an element, instead of just >> applying changes, is much more complicated, if you want to do it right and >> consistent. >> > > That's simply not right. A button is first and foremost a functionality > rather than a mere ui element, a thing you click to trigger an action. >
No problem. I hate the browser default styling. It's ugly^3. Tell the browser vendors. If they remove standard styles from all html elements, there is no need to use reset.css or now normalize.css to make sites compatible to different browser implementations. It would make the web much easier for today's designers. But that's not the web we have atm. TWs base CSS can be changed, using themes. > > > Especially that won't help me in overriding my button css, seeing as how > the core button css may change with any upgrade. > The base theme is the core theme. It starts from scratch with normalize.css. If you define your own base theme, you are the designer and have all the freedom you need. ... There are some dependencies, that come from the default Page-, View- and EditTemplates. All tc-xxx classes are defined there. You can change these class names, if you want but imo that's not needed. You just have to have a closer look to the tx-xxx names and use them. So if you don't want the "Cascading" in CSS you need to start from scratch. But your users still need to use tiddlers tagged. $:/tags/Stylesheet to apply there changes. So what do you win? -m -- 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.
