In deed, Responsive Web Design. Jeremy wrote
where we are now the choices are pretty stark: > * Tweak the existing themes (eg introducing something like the Zurb > Foundation side menu for small screens) Wouldn't Zurb and most others of these frameworks mean you must include additional (and weighty) js libraries etc? And using only pieces of a framework (such as for a side menu) might be useful - but you don't get the consistency which is the point with a framework (right?). The idea with bringing up specfically Skeleton was that is seems to be almost more about a consistent "html+css philosophy" that we could stick to. Yes, there's the Skeleton grid and some bits that do mean including stuff, but overall it would be valuable so that TW users can predict behaviour (e.g positioning) for when their plugins etc are used by others. Like Mario, I´d think introducing a new framework would mean reverse engineering and creating a new UI from scratch based on the framework principles. So when Jeremy suggests * Create a completely brand new theme, based on one of the frameworks ..I must ask, is a "TW theme" more than just CSS? Or wow could a new theme work properly without tweaking around in the rest of the code to make it fit into that theme?(Interestingly, I just noted there is very little on themes in the docs). <:-) -- 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/74bdf244-73b3-4659-a416-a51b154b31fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
