Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bootstrap 3.0 Upcoming changes

github.com

Post reply on HN
Print view View original

101–110 of 149 posts

Re: Bootstrap 3.0 Upcoming changes

#101

Post by conradfr »

ScotterC wrote: post #81
ses4j wrote: post #79

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...

I've found this site to be very helpful: http://bootstrapdocs.com/

As someone with something like four applications on different Bootstrap versions, THANK YOU (and to the creator of this site as well).

ps: yes I know you can just use the docs from the archives.

Re: Bootstrap 3.0 Upcoming changes

#102

Post by FuzzyDunlop »

ScotterC wrote: post #81
ses4j wrote: post #79

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...

I've found this site to be very helpful: http://bootstrapdocs.com/

That's certainly nicer than the one I threw together (and never found time to update manually) at http://bootstrap-docs.org. I'd probably consider pointing the domain at one that was maintained properly :)

Re: Bootstrap 3.0 Upcoming changes

#103

Post by pilif »

Trufa wrote: post #98
dminor wrote: post #34

> 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'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.

Re: Bootstrap 3.0 Upcoming changes

#104

Post by OriginalSyn »

TillE wrote: post #30
steferson wrote: post #2

Really sad they are dropping support for IE7 unfortunately I will not be upgrading to this version then.

IE8 runs on XP, though. Just about every Windows computer still in operation should have IE8 installed, for security reasons if nothing else.

Should but from what I understand IE6/7 still account for fairly large portion of our revenue.

Re: Bootstrap 3.0 Upcoming changes

#105

Post by VaughnDTaylor »

markdotto wrote: post #58
Swizec wrote: post #40

> All variables now use dashes instead of camelCase. For example, it's now @body-background instead of @bodyBackground. Not sure how I feel about this. On one hand that's a pretty large sweeping change that is going to break all my customizations. On the other, dashes look much better in css and I prefer them for class names and so on. Not even sure why, is this some sort of community standard I picked up somewhere a…

I struggled with making this decision, but ultimately it's all about readability for me. Hope it's not too much of a hassle for folks, but that's why this happens in a major update and not minor ones :).

I like the human-readability that dashes lend to URLs, but there are two things that bother me about using them in this case:

1. A dash is an operator, which could get confusing when you are doing math. For example: (@grid-gutter-width * (@grid-columns - 1)).

2. As far as variables go... thisIsDoubleClickable, and_so_is_this, but-this-is-not. I suppose it's not the biggest deal in the world, but I really hate having to drag my mouse to select.

My two cents...

Re: Bootstrap 3.0 Upcoming changes

#107

Post by VaughnDTaylor »

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 simply pointing to the bootstrap-master directory. However, the inclusion of variables.less in bootstrap-master > bootstrap.less (where it's an import) makes this difficult - variables.less is the ONLY file in bootstrap-master that I need to slightly tweak for each site I create. The variables.less file should not be a default import in bootstrap.less - at least this would be ideal for me. The way things are now, I have to modify bootstrap.less (to tell it not to import variables) and variables.less (to control colors, grid, etc). I'd like to just update all of the bootstrap-master files in one fell swoop without worrying about overwriting my changes to these two files. If variables was not a default import AND it was outside of this framework directory, I could update every file in bootstrap-master without worrying about overwriting anything. I hope I have communicated this in the right way - it seems a bit muddled?

Re: Bootstrap 3.0 Upcoming changes

#108

Post by bung »

VaughnDTaylor wrote: post #105
markdotto wrote: post #58

Earlier quoted context omitted.

I struggled with making this decision, but ultimately it's all about readability for me. Hope it's not too much of a hassle for folks, but that's why this happens in a major update and not minor ones :).

I like the human-readability that dashes lend to URLs, but there are two things that bother me about using them in this case: 1. A dash is an operator, which could get confusing when you are doing math. For example: (@grid-gutter-width * (@grid-columns - 1)). 2. As far as variables go... thisIsDoubleClickable, and_so_is_this, but-this-is-not. I suppose it's not the biggest deal in the world, but I really hate having…

Yea this is an age old discussion, I also like the separation that dashes or underscores give. Personally I'm a fan of underscores myself, mostly because I can then have id="foo_bar" #foo_bar and $foo_bar, for html, css, and jQuery variables, respectively, and remembering that JS can't have dashes in variable names. This makes the double clickable aspect super handy to me :)

Sometimes I hear that people don't want to have to press shift, which is understandable considering how much we code. But if bootstrap devs are already pressing shift in order to use camelCase, I wonder why they didn't pick underscores.

Re: Bootstrap 3.0 Upcoming changes

#109

Post by VaughnDTaylor »

bung wrote: post #108
VaughnDTaylor wrote: post #105

Earlier quoted context omitted.

I like the human-readability that dashes lend to URLs, but there are two things that bother me about using them in this case: 1. A dash is an operator, which could get confusing when you are doing math. For example: (@grid-gutter-width * (@grid-columns - 1)). 2. As far as variables go... thisIsDoubleClickable, and_so_is_this, but-this-is-not. I suppose it's not the biggest deal in the world, but I really hate having…

Yea this is an age old discussion, I also like the separation that dashes or underscores give. Personally I'm a fan of underscores myself, mostly because I can then have id="foo_bar" #foo_bar and $foo_bar, for html, css, and jQuery variables, respectively, and remembering that JS can't have dashes in variable names. This makes the double clickable aspect super handy to me :) Sometimes I hear that people don't want to…

This is my general rule: If it's client-facing (eg. a URL) then use dashes - it's more readable (at least I feel it is). If it's developer-facing, use underscores or camel case. Sure it's not as pretty, but it's functional - which is really what we need. This boils down to - do whatever is best for the user.

Re: Bootstrap 3.0 Upcoming changes

#110

Post by aed »

VaughnDTaylor wrote: post #107

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 touching bootstrap.less.

Yes, this does mean that the variables are being define again. However, this won't matter because what you define in your project.less will override everything else.

Post reply on HN