Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bootstrap 2.3 Released

blog.getbootstrap.com

Post reply on HN
Print view View original

41–50 of 118 posts

Re: Bootstrap 2.3 Released

#41

Post by visarga »

zopticity wrote: post #31

Man, I love bootstrap. Not only is it pretty well design from the front end and back end. The less files that are architected are awesome, I wouldn't have thought of it on my own. The guys built it for full customization for advance programmers and dead simple for beginners. Keep up the good work! The only disadvantage to this is that all startups are now 'lazy' and begin using bootstrap default theme colors and styl…

Maybe they could add support for color scheme designers to the customized version (such as kuler.adobe.com or colorschemedesigner.com, which are works of art in my opinion).

Also, some things are difficult to modify. What if I want two navbars, one with a different height than the other? Some tweaks seem pretty difficult to make.

Re: Bootstrap 2.3 Released

#42

Post by mjohn »

phoobahr wrote: post #8
instakill wrote: post #2

Not sure how I feel about the swearing on the page.

sooo... Counter(re.findall(r"[^a-zA-Z]([a-zA-Z]+)[^a-zA-Z]",requests.get(" http://blog.getbootstrap.com/2013/02/07/bootstrap-2-3-releas... ).content.lower())) I see one occurrence of 'shit'. I'm not sure how I feel about your pansy ass semi-outrage of someone else's release page language. Oh, wait. I feel nothing, approximately what this entire conversation thread is worth.

Love the use of Counter & requests, but you get 76 li elements with your regex - one of which contains another occurance.

Re: Bootstrap 2.3 Released

#43

Post by sc00ter »

logn wrote: post #32
blowski wrote: post #19

Earlier quoted context omitted.

I agree, it's gratuitous. Anyone with a swear filter (families, corporates) can't look at the documentation, and religious organisations may feel uncomfortable. Being open source, perhaps there's a fork opportunity for 'Bootstrap without the swearing'.

VelcroStrip?

Or keep the name Bootstrap for the fork, and rename this JockStrap?

Re: Bootstrap 2.3 Released

#44

Post by flaie »

rtpg wrote: post #22
robomartin wrote: post #15

> Renamed all of the variables to use dashes instead of camelCase. I absolutely detest camelCase. It ranks down there with good-old Hungarian notation. So, I am now wondering, why this change? Are people finally coming to their senses?

I don't want to start a flame war, but I was wondering if there is a rationale for prefering dash-case? I have a hard time not writing in camelCase by default now.

I believe it could be usefull for CSS selectors[1]

The following rule will match for values of the "lang" attribute that begin with "en", including "en", "en-US", and "en-cockney":

    *[lang|="en"] { color : red }
So you may now be able to select with CSS elements with that syntax, for example matching all text-warning, text-info, text-center etc with just

    *[class|="text"] { font-weight: bold }
Correct me if I'm wrong.

I don't know if it would be practical or not. Other than that it just a matter of preference, CSS classes tends to be generally separated by dashes from my point of view, whether I prefer Camel Case or not.

[1]: http://www.w3.org/TR/CSS2/selector.html#attribute-selectors

Re: Bootstrap 2.3 Released

#45

Post by davidw »

zopticity wrote: post #31

Man, I love bootstrap. Not only is it pretty well design from the front end and back end. The less files that are architected are awesome, I wouldn't have thought of it on my own. The guys built it for full customization for advance programmers and dead simple for beginners. Keep up the good work! The only disadvantage to this is that all startups are now 'lazy' and begin using bootstrap default theme colors and styl…

I'll take the time to say thanks too, since they seem to be following this.

We've long had lots of open source infrastructure like Linux, Rails, Postgres, Apache, and so on and so forth that was very much a "by programmers, for programmers" affair. It's very nice to get some "design" infrastructure - Bootstrap has made my sites look a lot better, and I get compliments from people.

So, a big thanks to the bootstrap guys!

Re: Bootstrap 2.3 Released

#46

Post by RobAley »

Sandman wrote: post #40
rgo wrote: post #35

Earlier quoted context omitted.

I personally prefer using the exact oposite to the language. That way my code or customizations are set apart visually: obj.getSomethingById() Non-native English speakers sometimes prefer to name variables in their native language for the same reason.

Why is it important that your code is visually set apart from the rest of the language?

When someone, particularly a beginner, is reading the code and come across, say, an unfamiliar function name, then they know straight away whether to look for it in the language docs or a definition somewhere else in the code. Not essential, but handy.

Re: Bootstrap 2.3 Released

#47

Post by egeozcan »

frisco wrote: post #10

Why the dropping of support for submenus? I find those really useful and it would be a pain to have to patch them back in.

They were so handy to have for those corporate and/or data-oriented web sites and doc archives.

Re: Bootstrap 2.3 Released

#48

Post by egeozcan »

egeozcan wrote: post #47
frisco wrote: post #10

Why the dropping of support for submenus? I find those really useful and it would be a pain to have to patch them back in.

They were so handy to have for those corporate and/or data-oriented web sites and doc archives.

...and BTW zurb offers a sleek solution to the "small-screen drop-down problem": http://foundation.zurb.com/page-templates/contact.html -- it extends the bootstrap's idea somehow and I was expecting to see something like this in the third version instead of having it removed.

Re: Bootstrap 2.3 Released

#50

Post by rschmitty »

mullr wrote: post #38
fat wrote: post #24

Earlier quoted context omitted.

fwiw, we generally just try to do what the language does: border-radius document.createElement etc…

This is the correct rationale, and should be used to end every argument about naming conventions.

what about the programmers who made javascript and css? I'm sure they flame each other!
Post reply on HN