Closed davebalmer closed 10 years ago
Ever thought about using LESS css, its pretty helpful on larger projects like this organizing your styling etc. Or would it be too large of an external dependency (ruby etc etc)?
There is an evolving JS version of LESS here that works with NodeJS...
Oooh a node.js version, very interesting, I'll check that out. Thanks! As for the original question, the core CSS should be simple enough for mortals to handle, it's just really messy at the moment. :)
The plan is to make a core set of CSS, and optional tweaks for various platforms, mostly for transitions (some perform better than others on things like Android). Then a theme layer on top of that for all the pretty stuff, with the hope that it'd be pretty easy to swap out themes (and custom CSS) with relative ease.
Less kicks ass, thank you for the suggestion! Very happy with it so far, and I'm adding a jo/less
folder to the repo for new themes.
Just a suggestion but if you go the node version of LESS css, you may want to think about using jake for your build system (although I do like the simplicity of cat'ing all your files together ;) github.com/mde/node-jake node is very cool for evented IO but I've been using it a ton just as an environment for development tooling. +1
Was using make files, but got some cries from MS devs who don't have cygwin. So for not, cat/copy is ok. Later? Will look into jake :)
jake is nice, but as everything node.js these days, it requires a cygwin environment to be fully functionnal (and without annoying issues). There is an effort to provide Windows binary (http://node-js.prcn.co.cc/) for node.js but npm (the kinda default node.js packaging system) relies on some unix tools.
Windows build is something I'm actively looking at improving. For now, the batch file approach is doing "ok", but certainly not ideal. :)
This was half-done. Time for a new revamp, but closing this thread.
"aluminum.css" has become sort of a mess. The files will be changed to have a "jo.css" file, with optional "ios.css", "webos.css", "mozilla.css" files that have tweaks (especially to default transitions). This should make it easier to skin, because the default CSS will have just enough to make the widgets work, with no significant visual styling.