31–40 of 149 posts
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.
Glad they are finally using icon fonts instead of PNG. Now we can make icons any color and add drop shadows if needed.
> Responsive CSS is no longer separate. Will we still be able to easily remove things like the "large desktop" size?
I don't see why you couldn't. It's pretty easy to find media queries in the CSS, because of the unique styling they have in the CSS file.
If it's not easy to remove, I'm guessing that I can just set the large format to something ridiculously high for the minimum width.
Hooray! Should make customization that much easier.
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.
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?
The hacks required to make older versions behave tend to pile up with time, increasing complexity and maintenance overhead for the developers. There gets to be a point where the complexity and overhead is no longer worthwhile to appease a very slim demographic.
Just use older Bootstrap versions if you want older browser support. I don't want your legacy users slowing down the progression for the rest of the modern world :)
Does 'punted' mean punted away like in a sport? Or does it mean bet on, like at a casino?
I don't think I saw it on the doc, but is there a projected release date for 3.0? It sounds like there is some pretty awesome updates coming, even though they seem more "back-end" related.
It would be great to get a prospective date in those types of announcements.
Best case is they spend a bunch of time on estimation that they could have spent on delivery. More likely is that they rush something that was unexpectedly hard, or drop things that the would have rather kept in. Or, worst of both worlds, they announce dates that they then slip.
Better, I think, that things are done when they're done. Or that they just have frequent, regular releases, like Ubuntu and Firefox do.
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 along the way?