CodaCoder/Russ - thanks for your input and recommendations. I've actually gained some basic proficiency with CSS over the past years (thanks to fiddling in TW) but it is definitely still too much of a hassle. Consider that themes, and tools for these, are a HUGE, HUGE deal in e.g publishing platforms like Wordpress. But it's barely even a discussion topic in the TW project. Of course, TW is not a publishing platform but it definitely has potential to be used as one (blogs, books, papers, or just websites for that matter).
I'd think themes are a HUGE deal for those other actors because people need to customize and control the appearence of what they show to others. To say that people should "just tweak the CSS manually" is missing the point. It's a bit like saying we don't need wikitext because you can do it with html and js. On the other hand, maybe TW people just aren't interested in "looks" and that's why themes are not a big deal here? TWs are typically not public so there is probably some truth to this but I also think the lack of styling tools hampers innovation and development of themes. gain, Skeleton might not at all be a step in the right direction, I don't know. And I think there are other routes than eventual CSS frameworks that would be much more powerful for style matters, that take advantage of TW powers and that could be used instead of explicit CSS hacking. I have some ideas myself so we'll see what comes up ;-) <:-) -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/ad9ca3e6-f395-4a25-a9db-eb8d85af51f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
