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

91–100 of 149 posts

Re: Bootstrap 3.0 Upcoming changes

#91

Post by jackmoore »

solox3 wrote: post #77
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…

Maybe they aren't using the property of the dash character just yet, but it is special in CSS: http://stackoverflow.com/a/5598250

They don't use that selector as far as I know, because it's very brittle. Something like [class|='span'] would only match classes starting with 'span-' if they are the first class in the class list. So it wouldn't match something like ''

Re: Bootstrap 3.0 Upcoming changes

#92

Post by harlanlewis »

apricot13 wrote: post #86
luigi wrote: post #51

Earlier quoted context omitted.

I've always wondered why they initially chose camelCase and not dashes. I like keeping camelCase for JS only. CSS uses dashes (border-top). LESS uses dashes in its example documentation.

because you can't double click on class names that contain dashes to quickly copy and paste them into your html. - do look neater but I wont switch because it frustrates me so much to not have that simple feature!

Funny, my editor usage is different, so I prefer dashes for the exact reason you don't. I use opt+(shift)+arrow keys to navigate and select words instead of mouse doubleclick.

camelCase and under_scores both select the full string as a word. But if you throw some-dashes-in-there, and you're using the keyboard, it's super fast to select just the bits of the value you want. Without the dash, you have the select a character level to modify aspects of the string, which is fairly fiddly for being such a common task.

A simple example of this being awesomely quick is adding a pre/postfix to values, eg:

@color-link @color-link-hover @color-link-active

Re: Bootstrap 3.0 Upcoming changes

#93

Post by ihsw »

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

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.

Re: Bootstrap 3.0 Upcoming changes

#94

Post by timdorr »

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…

Could someone create a compatibility stylesheet that defines all the camelCased variables based on the new dashed values? Just as a stand-in until you can update all your variables.

That or can someone write up a nice Sed script to grep through my less files and change all the variable names?

Re: Bootstrap 3.0 Upcoming changes

#95

Post by FireBeyond »

CCs wrote: post #89
angersock wrote: post #68

Earlier quoted context omitted.

Maybe 5% of users need to get their shit together and upgrade. :|

They can't upgrade. Hospitals and big companies lock down the computers, you can't install anything. If it comes with IE7, that's all you got. And it's not because of these companies. E.g. they need to run a specific custom version of SAP (accounting), which on turn crashes if any other browser is present. Upgrading would cost over $30M, so forget it for a while. Or the hospital needs to validate the hardware + OS +…

To a degree, definitely. As someone who works in healthcare (both as a practitioner - paramedic), and whose other job is healthcare IT...

I know your example is exaggerated for effect, but there is (or should) be a difference between "general use" PCs in a hospital, and Patient Care / Management PCs (EHR, workflow automation, digital diagnostic imaging, pharmacy and the like). That in itself is a failling of healthcare IT policy.

Sure, your critical systems should all be be "certified", but even that is an area ripe for disruption - witness DrChrono in EHR, and I myself am working, or brainstorming on, better "field reporting" (i.e. 911 response laptops / tablets - most software in this field is horrific for usability, though admittedly there is pretty cool functionality, the ability to transmit 12-lead ECG to the hospital for prepping cath labs is fantastic) - definitely willing to talk to people interested in such a thing.

Edit: as an aside, I'm yet to see MRI software that wasn't driven by a Solaris backend, or even Irix, though that does demonstrate how this area works.

Re: Bootstrap 3.0 Upcoming changes

#96

Post by FireBeyond »

envex wrote: post #84
johnny22 wrote: post #72

Earlier quoted context omitted.

does SASS work without installing the pre-processor? I know LESS does. I didn't think SASS did. LESS will work well enough with just the js file loaded (if a bit slower).

You still have to compile both. You shouldn't be running less.js in production.

Interesting, I didn't know this, though in retrospect, it should be obvious, versus compilation.

Re: Bootstrap 3.0 Upcoming changes

#97

Post by pc86 »

vyrotek wrote: post #49
josscrowcroft wrote: post #23

Earlier quoted context omitted.

When was the last time anybody used FF 3.6? Serious question.

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.

Re: Bootstrap 3.0 Upcoming changes

#98

Post by Trufa »

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!

Re: Bootstrap 3.0 Upcoming changes

#99

Post by jarcoal »

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!

It was just an example, but what this means is that they are switching to semantic naming, rather than style naming.

Re: Bootstrap 3.0 Upcoming changes

#100

Post by sbarre »

fourstar wrote: post #32
tiredoffps wrote: post #9

Glad they are finally using icon fonts instead of PNG. Now we can make icons any color and add drop shadows if needed.

It can be easily done (with any svg/fonts you have) using this awesome tool if you're interested: http://icomoon.io

Wow, that site pegs Chrome at 100% CPU on my Macbook Pro..
Post reply on HN