although m a fan of MS but i will prefer chrome since its DOM is very resembling to IE and and in accordance to W3C but Firefox is just a mess for making trouble specially to the developers and designers..
We sometimes use CSSdry at work when we do Drupal stuff. One of my coworkers developed a module for that, though I'm not sold on it myself. I never use anything like it for my own projects. It's the compiling that throws me off, and it quickly gets tiresome to find the correct lines since it makes firebug harder to use.
@giles - how does that compare to a developer coming fresh to your project and not knowing anything about your own system? Same problem. In fact, you're less likely to suffer difficulties implementing a common framework, as then there's at least a chance they'll have come across it before.
I do recognise that frameworks are not without their criticisms, but there are good reasons why some people would want to use them.
Rob - 14 years ago
There's always csscaffold for regular php users.
The idea sounds great, but may require large projects to be benificial.
rvr - 14 years ago
sass & compass is the killer combination. learn it and you will love it.
i really like the nested feature of less, since i was trying to handle css-code like that years ago when i was dumb (but somehow smart as it turns out to be a great time-safer)
Hmm, I don't use a framwork per se, but I have a CSS reset and other sets of rules that make MY life easier. Nothing to compile, though, just plain CSS.
The problem with these frameworks is that you need to compile it or have the code interpreted by another program before it is usable. That is no problem of course if you already use ruby / rails in your project, but if you are developing on e.g. plain php you have a lot of overhead just for using one of these frameworks.
But the features (especially of Less) are very nice. I would like to see them embedded into the css core.
Less is indispensable. The variables in CSS are great for colours. And the nested blocks are brilliant. This stuff should be built into CSS by default.
@Frederick Some Frameworks are very sloppy and rigid and make future development tough. Compass is very flexible though, and designed to solve exactly that problem.
Here's one of the cool things you can do with Compass: CSS3 buttons that degrade nicely: http://brandonmathis.com/projects/fancy-buttons/
The problem with these frameworks is if another developer needs to work on the project further down the line and they don't know the framework then it can cause huge time delays and problems.
although m a fan of MS but i will prefer chrome since its DOM is very resembling to IE and and in accordance to W3C but Firefox is just a mess for making trouble specially to the developers and designers..
We sometimes use CSSdry at work when we do Drupal stuff. One of my coworkers developed a module for that, though I'm not sold on it myself. I never use anything like it for my own projects. It's the compiling that throws me off, and it quickly gets tiresome to find the correct lines since it makes firebug harder to use.
@giles - how does that compare to a developer coming fresh to your project and not knowing anything about your own system? Same problem. In fact, you're less likely to suffer difficulties implementing a common framework, as then there's at least a chance they'll have come across it before.
I do recognise that frameworks are not without their criticisms, but there are good reasons why some people would want to use them.
There's always csscaffold for regular php users.
The idea sounds great, but may require large projects to be benificial.
sass & compass is the killer combination. learn it and you will love it.
i really like the nested feature of less, since i was trying to handle css-code like that years ago when i was dumb (but somehow smart as it turns out to be a great time-safer)
Hmm, I don't use a framwork per se, but I have a CSS reset and other sets of rules that make MY life easier. Nothing to compile, though, just plain CSS.
Long live the standards.
The problem with these frameworks is that you need to compile it or have the code interpreted by another program before it is usable. That is no problem of course if you already use ruby / rails in your project, but if you are developing on e.g. plain php you have a lot of overhead just for using one of these frameworks.
But the features (especially of Less) are very nice. I would like to see them embedded into the css core.
Noo, but I would definitely consider using one if a need to handle a bigger project.
i know CSS framework is nor for professional development but we need it for many reasons.
Not yet, nut maybe in the future when they are even better, would give it a try.
Less is indispensable. The variables in CSS are great for colours. And the nested blocks are brilliant. This stuff should be built into CSS by default.
I can't imagine managing CSS in my current project without SASS. I makes things so easy to organize and variables/mixins are awesome!
I can see how it wouldn't be worth the trouble on small projects/sites however.
@Frederick Some Frameworks are very sloppy and rigid and make future development tough. Compass is very flexible though, and designed to solve exactly that problem.
Here's one of the cool things you can do with Compass: CSS3 buttons that degrade nicely: http://brandonmathis.com/projects/fancy-buttons/
Never. I've looked at a few before, but I've never been working on a project that has really allowed me to investigate them properly.
Less looks really interesting though and will definitely be something I take a closer look at. Need to look into getting Ruby set up first...
they're called suck
No, but the concept looks promising. Worth looking into some time.
The problem with these frameworks is if another developer needs to work on the project further down the line and they don't know the framework then it can cause huge time delays and problems.
I find these frameworks to be very sloppy.
Nope. But lesscss sounds promising... though that's more something like a CSS 'extension'.
Erm, no.