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

121–130 of 149 posts

Re: Bootstrap 3.0 Upcoming changes

#121

Post by robryan »

d1plo1d wrote: post #115
ihsw wrote: post #93

Earlier quoted context omitted.

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.

There is however the problem that historically they have not keep a copy of the old docs online. So if you stick to 2.2.2 your probably going to be SOL when it comes to reference info. Sure there is an archive somewhere of the old docs but that is a long way from ideal.

Aren't the docs part of the repo?

Re: Bootstrap 3.0 Upcoming changes

#122

Post by markdotto »

nathanstrauser wrote: post #29
nosecreek wrote: post #12

Earlier quoted context omitted.

I was worried when I saw this, but the very next bullet point is: >Overhauled default grid system. Now uses percentage widths, padding, and box-sizing: border-box instead of pixel widths and margins. Nesting and offsets remain the same. Which sounds like they are actually making everything fluid, and removing fixed widths. Perhaps a good thing, although border-box means no IE7 support.

same thoughts here - worried, then optimistic as it should actually be a more simple syntax to create nested grids - would be really nice if you'd be able to do a project wide removal of "-fluid" and it all just works the same

That should work just as you described it.

Re: Bootstrap 3.0 Upcoming changes

#123

Post by markdotto »

jpdevereaux wrote: post #36
Griever wrote: post #31

Exciting! I really hope they do end up going with multiple modal widths in 3.1, as I've had to do this myself on more than a few occasions. On a side note, I'm curious as to why they decided to refactor their variable names to include dashes instead of just sticking with camel casing. Personally, I find camel casing to be much more readable.

For a while the dash-ing annoyed me until I realized that it makes selecting/changing part of a variable name easier (at least in vim). Can't imagine that's the reasoning behind it but it does work out well.

Vim wasn't the exact reason, but text selection is a huge part of it. Readability and text selection are huge.

Re: Bootstrap 3.0 Upcoming changes

#124

Post by zalew »

novamantis wrote: post #118
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 almost fell out of my chair when you said "government people who can't control their own computers". That's just so wrong. No they refuse to change. Administrators have no excuses anymore. If they literally couldn't control their computers, they would have to be terminators.

> Administrators have no excuses anymore.

Yes they do. They have procedures and are paid to act according to them. You are clearly unaware how the public sector works, or how expensive are upgrades in such scale. Upgrading software for the whole administration sector of a big country means upgrading a few hundreds/thousands computers per city (depending on the population), do the math; and only if the upgrade is even possible (breaking dependencies of software ordered 10 years ago).

Yeah, 'the system is broken', blah blah, it is what it is.

BTW Polish parliament (420 people) members were given iPads 'to save on paper'. Aside from the fact they watch porn at work, the yearly cost of maintanance and upgrades is at $150k. Yep.

You probably want your govt to spend money on better things than upgrading browsers.

Re: Bootstrap 3.0 Upcoming changes

#125

Post by markdotto »

hackerboos wrote: post #11

How about dropping support for LESS and using SASS instead?

Negatory, but given the prominence of the ports and use of Sass, we'll likely try to do something here to help folks out who are using that over Less. No reason we couldn't write a script to translate the two or officially sanction a port. Both have their pros and cons; just a matter of time, duplicate code, etc.

Re: Bootstrap 3.0 Upcoming changes

#126

Post by markdotto »

bluetidepro wrote: post #6
riffraff wrote: post #3

> Hero unit > ❑ Convert class to .jumbotron. can someone explain the rationale here?

V2.2.2 used ".jumbotron" AND ".masthead" for the hero unit in the docs, so I think they are just condensing that to one class. See this screenshot: http://bluetide.pro/cPkH/5LohuilN

Pretty much. Plus, it's a much better (and more socially known) metaphor for describing its function and presentation.

Re: Bootstrap 3.0 Upcoming changes

#128

Post by jrochkind1 »

markdotto wrote: post #125
hackerboos wrote: post #11

How about dropping support for LESS and using SASS instead?

Negatory, but given the prominence of the ports and use of Sass, we'll likely try to do something here to help folks out who are using that over Less. No reason we couldn't write a script to translate the two or officially sanction a port. Both have their pros and cons; just a matter of time, duplicate code, etc.

that's awesome to hear.

Even if you don't officially sanction or provide a port yourself -- just hearing that you're open to tweaking the way you do things a bit to make it easier for _others_ to port to Sass (and keep their ports up to date with bootstrap evolution) -- is super encouraging.

I'd actually suggest that as a first step, just talk to the folks maintaining the ports, and ask if there's anything you can tweak on your end to make their jobs easier.

Re: Bootstrap 3.0 Upcoming changes

#129

Post by jrochkind1 »

markdotto wrote: post #90
isabre wrote: post #55

"Dropped all things fluid." Looks like I've got some updating to do in the near future.

The default grid system will be come fluid (using percents for widths), so you'll have to just find and replace the row classes and you should be okay. Unsure about more complex layouts though.

This is awesome, thanks for the clarification.

I got scared at 'dropping fluid', because it's become been pretty clear to me that the fluid approach in bootstrap was better for most apps, and I was wondering why in fact using the fluid approach wasn't more popular. I got worried that you were making it much more difficult -- but it turns out you agree with me, and instead are making it the out of the box default! woo!

Re: Bootstrap 3.0 Upcoming changes

#130

Post by dheerosaur »

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 don't mind haveing color variables. When I need a new red, I define @projectRed or @redAlt. It is so much easier to remember red than some dangerColor.

Why will they choose hyphenated variables instead of camelCase?

Post reply on HN