Hi Mat > > Wouldn't Zurb and most others of these frameworks mean you must include > additional (and weighty) js libraries etc?
Yes, that’s one of the drawbacks that I mentioned. > 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?). Most frameworks are hard to use piecemeal, and a bit pointless, because their raison d’être is to enforce consistency. > 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, I don’t see anything much different in the philosophy of Skeleton from the others, but maybe I’m missing something. > 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. That’s a theoretical benefit that may or may not happen, but you’re ignoring much more serious obstacles: frameworks like Skeleton just don’t have the functionality that we need. Look through the Skeleton examples and you’ll see what I mean. I think it would be helpful to understand more what the problem is that you’re trying to solve? If it’s that the TW5 themes have some crufty and confusing CSS, then I think there’s easier ways to fix it than trying to reuse something that was designed for a totally different purpose. > 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). A TW theme is generally just CSS but it can include other components like any other plugin. One could indeed create a new theme without disturbing the underlying HTML generated by TW, but I suspect that in practice one would end up tweaking some things in the HTML. Best wishes Jeremy. > > <:-) > > -- > 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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywikidev > <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 > > <https://groups.google.com/d/msgid/tiddlywikidev/74bdf244-73b3-4659-a416-a51b154b31fe%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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/ADDCD75B-6116-4B02-85F1-2E7649D8F1E6%40gmail.com. For more options, visit https://groups.google.com/d/optout.
