Live data from Hacker News

Twitter's Bootstrap 2 ready for testing and feedback

markdotto.com

11–20 of 87 posts

Re: Twitter's Bootstrap 2 ready for testing and feedback

#11
post #9

Have been using and loving Bootstrap for the past few weeks. Can't recommend it highly enough. I thought Themeforest templates were a great secret weapon, but the thoughtfulness that went into the actual markup in Bootstrap makes working with it fast and painless. That said: no idea what's in Bootstrap 2. Someone got a concise summary?

The docs offer more details: http://markdotto.com/bs2/docs/index.html

Here's my quick (and probably incomplete) list:

- new 12 column grid

- responsive layout

- tons of new JS plugins

- stacked forms are now the default

- lots of new 'controls', like split buttons, new tabs, toolbars, highly styled radio buttons and check boxes.

- icons(!)

Re: Twitter's Bootstrap 2 ready for testing and feedback

#12
I've been using Twitter Bootstrap on a two projects for months. It has a huge upside, even for designers who write their own CSS. Version 2 seems to be filling in some gaps ( like responsive design and navigation lists/tabs ) and "filling out" with many nice-to-haves ( like progress bars ). I'm really looking forward to using version 2. Thank you Mark and Twitter team for the great work!

Re: Twitter's Bootstrap 2 ready for testing and feedback

#13
post #9

Have been using and loving Bootstrap for the past few weeks. Can't recommend it highly enough. I thought Themeforest templates were a great secret weapon, but the thoughtfulness that went into the actual markup in Bootstrap makes working with it fast and painless. That said: no idea what's in Bootstrap 2. Someone got a concise summary?

Let's see:

Button groups. Toolbars. Icons sprites. Progress bars. Checkboxes and radios as buttons. More appropriate terminology (Tooltips instead of Twispies). Some retouches on styling and class naming. An overall increase of functionality for most of the existing stuff.

It's definitely a worthwhile upgrade, and it seems to be all added functionality, not a lot of semantic changes.

Re: Twitter's Bootstrap 2 ready for testing and feedback

#14
post #9

Have been using and loving Bootstrap for the past few weeks. Can't recommend it highly enough. I thought Themeforest templates were a great secret weapon, but the thoughtfulness that went into the actual markup in Bootstrap makes working with it fast and painless. That said: no idea what's in Bootstrap 2. Someone got a concise summary?

Not quite a concise summary, but looking at the documentation, the biggest changes I noticed were :

- Responsive design using media queries

- CSS Progress bars

- A few new javascript plugins (Carousel, Typehead)

- Icons

The documentation is online here in case you missed the link the article : http://markdotto.com/bs2/docs/index.html

Maybe someone has a better summary

Re: Twitter's Bootstrap 2 ready for testing and feedback

#16
post #9

Have been using and loving Bootstrap for the past few weeks. Can't recommend it highly enough. I thought Themeforest templates were a great secret weapon, but the thoughtfulness that went into the actual markup in Bootstrap makes working with it fast and painless. That said: no idea what's in Bootstrap 2. Someone got a concise summary?

The big one, for me at least, is the move from a 16-column grid to a 12-column grid. I didn't look into the technical differences, just those that would impact development with it.

I just converted a ton of stuff (like last week), so it's pretty fresh in my mind. I feel like I should have checked the wip branch first, but this has really become my favorite kit. I've been about 95% YUI and the remainder OOCSS, and Bootstrap is the fastest concept-to-reality I've used.

I'm not too worried about upgrading if there are some compelling reasons to do so.

Re: Twitter's Bootstrap 2 ready for testing and feedback

#17
post #16
post #9

Have been using and loving Bootstrap for the past few weeks. Can't recommend it highly enough. I thought Themeforest templates were a great secret weapon, but the thoughtfulness that went into the actual markup in Bootstrap makes working with it fast and painless. That said: no idea what's in Bootstrap 2. Someone got a concise summary?

The big one, for me at least, is the move from a 16-column grid to a 12-column grid. I didn't look into the technical differences, just those that would impact development with it. I just converted a ton of stuff (like last week ), so it's pretty fresh in my mind. I feel like I should have checked the wip branch first, but this has really become my favorite kit. I've been about 95% YUI and the remainder OOCSS, and Bo…

I found the dox from Aaron's comment (thanks, everyone!). Bootstrap 2 looks amazing.

What's the win going from 16 to 12 columns?

Re: Twitter's Bootstrap 2 ready for testing and feedback

#19
post #2

I've been using the new twitter bootstrap with backbonejs for some prototypes and have progressed much faster than I anticipated. The learning curve on this one was not bad at all -- the examples are great!

Yeah, it's a fantastic combo. I recently opted to do subsequent dev on Knockout.js, though. LOC for markup, styling, and javascript under this regime is fantastically small and really quick to develop.

Don't mean to hijack, but I'm curious if anyone has gone the other way, i.e., choose backbone over knockout. My main concern is DOM overload/GC issues. Backbone is also considerably smaller, but that's not as important in my context.

Re: Twitter's Bootstrap 2 ready for testing and feedback

#20
post #10
post #2

I've been using the new twitter bootstrap with backbonejs for some prototypes and have progressed much faster than I anticipated. The learning curve on this one was not bad at all -- the examples are great!

Bootstrap and backbone are great together. I wish there was more concrete tutorials on getting the two to play nice, but all I could find was bits and pieces about both. Even with that I have managed to knock out a few prototypes fairly easily.

Any twitter bootstrap tutorials you can recommend, beside just using inspect element in Chrome console?
Post reply on HN