@TiddlyTweeter wrote: > > > IMO the cascade in TW can get quite complex to figure out if you hit a > problem. Part of that is slack practice--i.e. overdoing add-on styling via > too many tiddlers rather than adding to a "mother" sheet where you can > better control it. >
IMO, a single monolithic mother stylesheet goes against all that TW stands for and we should go in the exact opposite direction; We should split up the current theme(?) stylesheets into meaningful chunks - BUT then use the usual filter techniques to assemble them into some kind of overviewable aggregation that also sets the cascading order of them. (Crazy idea: Maybe tiddlers could themselves be style definitions? The title is the selector and the text is the declarations. Maybe fields for sub selectors. This way it'd be very simple to reuse declarations. And it would be super simple to try out stuff; just overwrite such shadow style tids and delete if you regret. And we could tag styles or add other meta data.) IMO, CSS hackability is one of the weaker areas in TW if you consider that hackability is a main objective and how powerful CSS is in TW. <:-) -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/748f4e86-dd81-474d-a7ca-b9b69b9fd79b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
