111–120 of 149 posts
Earlier quoted context omitted.
I'm sorry, I don't know what @state-warning-text is, googling it only seems to point to this article, could somebody explain please? thanks!
The problem is that a variable name like "orange" is a very bad variable name in case your design wants warnings to be in, say purple for whatever reason. If the LESS variable is called "state-warning-text", you can define that to be purple without the bad aftertaste of having to use "orange" when you mean purple.
Earlier quoted context omitted.
I'm sorry, I don't know what @state-warning-text is, googling it only seems to point to this article, could somebody explain please? thanks!
It was just an example, but what this means is that they are switching to semantic naming, rather than style naming.
Earlier quoted context omitted.
I know of a call center here in the US with 300 stations that have XP and FireFox 3.5 and they won't be upgrading anytime soon.
I don't think people are browsing cutting-edge websites on their call center computers.
I wish they weren't dropping IE7 support. You can make fun of "who uses that!" all you want, but we build a site that is used by government people who can't control their own computers, and our current demographics are 50% IE7! Nothing to be done, we just can't upgrade to Bootstrap 3.0. So -- if you MUST do this, at least leave the website docs up for Bootstrap 2, cause we're not going anywhere...
Bootstrap 2.2.2 is going to be the last 2.x release and it's fairly polished to begin with. There's nothing wrong with intentionally staying behind -- Bootstrap 3.x features will more than likely lean a lot more heavily on CSS3/HTML5.
Sure there is an archive somewhere of the old docs but that is a long way from ideal.
This is something that has been messing with my workflow so hear me out. First, I use CodeKit on my local machine to compile. CodeKit allows me to choose a framework (bootstrap-master > LESS files). I don't want to keep multiple versions of bootstrap-master sitting around on my computer. Preferably, I'd have the most current version with which I'd use to build all of my CSS (regardless of the site I'm working on) by…
I actually know exactly what you're talking about and here's what I do: - Put Bootstrap in a folder and import it as a framework in CodeKit. (Just like you.) - In my project folder, I create a LESS file for the project (e.g. project.less). - At the very top of my project.less I add an import for bootstrap (@import "bootstrap.less") - I define and customize all my LESS variables within the project.less without touchin…
> Removed all color variables (e.g., @blue, @orange, etc). New, more meaningful variables are on their way (such as @state-warning-text). Hooray! Should make customization that much easier.
I wish they weren't dropping IE7 support. You can make fun of "who uses that!" all you want, but we build a site that is used by government people who can't control their own computers, and our current demographics are 50% IE7! Nothing to be done, we just can't upgrade to Bootstrap 3.0. So -- if you MUST do this, at least leave the website docs up for Bootstrap 2, cause we're not going anywhere...
If they literally couldn't control their computers, they would have to be terminators.
Really sad they are dropping support for IE7 unfortunately I will not be upgrading to this version then.
_this_. And why drop support for FF 3.6 too? Is there a technical reason to drop support for older browsers or is it idealism?
This is something that has been messing with my workflow so hear me out. First, I use CodeKit on my local machine to compile. CodeKit allows me to choose a framework (bootstrap-master > LESS files). I don't want to keep multiple versions of bootstrap-master sitting around on my computer. Preferably, I'd have the most current version with which I'd use to build all of my CSS (regardless of the site I'm working on) by…
I actually know exactly what you're talking about and here's what I do: - Put Bootstrap in a folder and import it as a framework in CodeKit. (Just like you.) - In my project folder, I create a LESS file for the project (e.g. project.less). - At the very top of my project.less I add an import for bootstrap (@import "bootstrap.less") - I define and customize all my LESS variables within the project.less without touchin…