> > 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. >
I meant it would would be a "html+css philosophy" for TW. Perhaps "rules of thumb" would be a btter term. The idea is simply to have an outline to stick to (or break if one insists). But, since you ask for it, Skeleton *does *seem philosophically different in that it aims to *only *use vanilla CSS. If any CSS framework was easy to post-introduce, then it would probably be this. Now, you point out that frameworks like Skeleton just don’t have the functionality that we need. > Look through the Skeleton examples and you’ll see what I mean. Is it fundamentally wrong or just incomplete? Since it's only vanilla CSS then it wouldn't prevent us from simply building on it but still get the benefits of it. Spontaneously I'd guess that "completing" it with local needs can't be uncommon... it's just CSS. If it's fundamentally wrong then that's another matter. 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. > Yes, the problem is complex; for one thing, while there current CSS of course is not without structure, it is not formalized so it is often tricky to find what one needs in the stylesheets and to know if something exists at all. And it's just overall difficult to design things so they work on e.g mobile without a framework or similar, not to mention the uncertainty of how it will look on other OS'es etc. I would think a particular lack for this is a "grid" to position things instead of the for me typical scene where I fiddle with padding, margins or even floats. Overall I think the [lack of] tools for changing the looks in TW is not up to par with TW itself. TW is super customizable in terms of features and application areas but when it comes to layout and style we're kind of stuck. I think a formal "base" for styling might open up for tools that will then build on, or deal with, such a base. Is a CSS framework the best way for this? I can't tell. I just figured Skeleton, with pure CSS, could be a "harmless" step in the right direction. <:-) -- 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/9437d237-d4ae-47f0-b372-146ef7480eab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
