*Problem:* Yes, you can make almost anything with TW - it is *made* for hacking! > What's that? - sidebar on left side? ... ehm.. that's a bit beyond of TW > itself.... you must know CSS.
I think we all agree that a TW user should *ideally* not have to learn CSS to shape TW into what he wants. How can we get away from this? Or does it have to be this way? Another problem, even when you know CSS: There is a big "workflow differences" between wikitext / html and css - Wikitext and html is where the user is ...but CSS is somewhere else: If you want to modify wikitext/html, you "click edit and then edit". CSS is often way more intricate. You must figure out where the style is defined, open that stylesheet and then often the most difficult part to locate the place(s!) what it is defined. And then go back - i.e if you don't want to overwrite the stylesheet, you must copy-paste by creating a new stylesheet, tag it, type it, close the original stylesheet. Et cetera. With html we have (some) wikitext "elements" presumably so the user won't have to know html. E.g pipe for tables and several of the widgets. With CSS we have some predefined classes but as someone pointed out; the more properties a class has the less reusable it is! How can TW deal with this problem in a good way? *How much CSS should a TW user need to know?* Maybe even: Who does TW cater for and therefore who does the CSS solution cater for? P.S Worthwhile article on CSS and Scalability <http://mrmrs.cc/writing/scalable-css/>. <:-) -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev/851a6ac9-3f70-4d1e-b384-a86cf64815a7%40googlegroups.com.
