7 ms·
Cue a dozen comments about flat buttons. This looks like a nice set of changes for Bootstrap. I'm not sure how I feel about the grid class name changes, but th
by aaronbrethorst 13y ago
Cue a dozen comments about flat buttons.
This looks like a nice set of changes for Bootstrap. I'm not sure how I feel about the grid class name changes, but then again, I went all-in on Foundation a few months back, so it doesn't affect me one way or another.
I'm sure mdo and fat have excellent reasons for using Less instead of Sass, but I'm a Rails user and I like Sass better to boot. Anyway, no matter, I'm glad to see Bootstrap is continuing to push forward!
- taspeotis 13y agoI've inherited a web application that's held together with invalid HTML and riddled with inline CSS. Got the green light to redo it all. Replacing all the markup has been on hold pending BS3 (the mobile-first aspect of BS3 seems a big win over BS2), but while waiting I've seen a lot of people talking about Zurb Foundation and its "superior" grid system. From a purely HTML5+CSS3 point of view, what do you think of BS vs. Zurb?
- Kiro 13y agoWhy do people think Zurb's grid system is better? I don't remember it being any different from Bootstrap's grid system.
- robeasthope 13y agoZurbs' grid uses percentage widths for columns and is mobile-first - BS 3 now uses a similar system which makes the only really difference SASS/SCSS vs LESS if you just want the grid
- mesec 13y agoIIRC, Boostrap 2 can use percentage widths too -- you need to use the "row-fluid" class (instead of just "row").
- robeasthope 13y agoFair point
- aaronbrethorst 13y agoClearly, I can't speak to BS3, but the thing I like most about Foundation is the mobile-first grid: build your grid layout using Foundation's 'small-n' classes and it just works on larger screens too. If you want to develop more complex layouts for larger screens, all you have to do is append 'large-n' class names (and now 'medium-n' exists, too).
- johnny22 13y agobs3 is mobile first also
- hnriot 13y agoThat's interesting to read, beccause on my iPad 4 BS3 is very sluggish. Buttons visibly wait to show any change, menus the same. I don't have this problem with BS2. Maybe when it ships this will have been eliminated.
- zw 13y agoHm, I'm experiencing that as well (probably to somewhat less extent) on a mini. Very strange.
- ayi 13y agobootstrap 3's grid system now uses percents instead of fixed pixels. also col-lg or col-sm classes can be used to design/show different content on different resolutions. my vote is on bootstrap.
- yannis 13y agoResponsive tables is a big plus for Zurb.
- gkoberger 13y agoI prefer LESS over SASS, simply because of how often I use mixins and how nice ".border-radius(5px)" is compared to "@include border-radius(5px)". That being said, my current setup is Stylus+Nib. (And for the above examples, you'd just write "border-radius: 5px" and it takes care of everything. Much more flexible.)
- STRML 13y agoActually, in SASS, border-radius is done with the syntax `+border-radius(5px)`. You're thinking of SCSS, which is much more verbose but has more similar syntax to CSS.
- gkoberger 13y agoAh, good point. Yes, I use SCSS (although SASS is a closer comparison to Stylus).
- emn13 13y agothere is such a thing as plain border-radius: 5px, you know? I think mixin's are generally overused; having to maintain css as well as right it, I'm quite happy with a syntax that doesn't encourage their use. If you need em: fine, but the you won't care about @include vs. "." anyhow.
- untog 13y agoAs I'm sure you well know, a mixing includes vendor specific prefixes. And the whole point of mixins is to make it easier to maintain. Once they're written, you don't need to worry.
- timdorr 13y agoThe percentage of browsers that still require these prefixes are miniscule. I've been using border-radius, box-shadow, box-sizing, and others without prefixes for a while now without issue. Check caniuse.com for their status and you'll find vendor prefixes are dropping like flies.
- hcatlin 13y agoTo the commenters, it's Sass not SASS.
- joevandyk 13y agoUgh, those aren't buttons. Those are text inside a rectangle. :( http://monosnap.com/image/Vc05ZRQmGTmRrYvTEbLaYAI6w.png http://monosnap.com/image/Vc05ZRQmGTmRrYvTEbLaYAI6w.png -- those do not look interactive at all.
- jmduke 13y agoThat's an opinion, not a fact. If I see a colored rectangle that's offset from the text with a label that indicates action[1], I immediately think its a button. I'm willing to wager a non-trivial amount of consumers do so as well, but this is what things like context and split testing are for. [1] The trickiness with flat design is when buttons for action are also used as information display. One of the biggest issues with the first iteration of Metro was that you'd have a box that shows your current number of emails -- and you didn't know if that was just a part of your dashboard or also a link to your email that had a nice preview. That's not a failing of flat design, that's a failing of design.
- ricardobeat 13y agoI see labels. Of course context plays a huge part, but it's a gamble whether this trend will survive for long.
- skinnymuch 13y agoSort of reminds me of people saying colored text without underlines aren't links