h a l f b a k e r yI think, therefore I am thinking.
add, search, annotate, link, view, overview, recent, by name, best, random
news, help, about, links, report a problem
browse anonymously,
or get an account
and write.
register,
|
|
|
When working with Cascading Style Sheets (CSS) it can quite easily mushroom into an unmanageable haystack behind your back right under your nose.
Most slightly complex sites these days are also working with a persistence layer - for example, a database.
My idea is to put the CSS rules into that
database.
This way, some bright spark can develop a front end that resembles something like what I imagine a spreadsheet to be like, if I'd ever sat in front of one in my life. A way of collating different views of the data groupings, which can be switched on the fly.
Thus, one can view and edit the CSS rules as 'which selectors share this rule' type of formatting, and at a moments notice, the quickness of the mouse deceives the hand, and lo! you're now working with your CSS in 'which rules are pertinent to this selector' kind of arrangement. Or even more esoteric views, if you want.
[link]
|
| |
// mushroom into an unmanageable haystack behind your back right under your nose // |
|
| |
[marked-for-mixed-metaphor] |
|
| |
Since the CSS section can form a part of the page document, and since more and more these days, pages are being built 'on the fly' rather than existing as a repository of static files - this is eminently doable - so much so, I would have thought that it must be implemented somewhere out there already. |
|
| |