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

61–70 of 118 posts

Re: Bootstrap 2.3 Released

#61

Post by joesb »

flaie wrote: post #44
rtpg wrote: post #22

Earlier quoted context omitted.

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…

[*class|="text"] will also matched textWarning, textInfo, textCenter, etc.

Re: Bootstrap 2.3 Released

#62

Post by ralmeida »

instakill wrote: post #2

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

I too feel a little put off by this. I find it immature and gratuitious, like others have said in this thread. This made me recall that in the examples they have HTML comments reading "le javascript" and "le CSS" if I recall correctly.

I have a personal pet peeve with people using 'Internet slang' outside _humor_ places on the Internet (some people I know overuse it to the point of annoyance), and so the discomfort I feel reading these terms sneaks up to my impressions of Bootstrap and its authors. Of course, rationally I know it's a good product made by outstanding people, so I still use it without refrain, though.

Re: Bootstrap 2.3 Released

#63

Post by flaie »

joesb wrote: post #61
flaie wrote: post #44

Earlier quoted context omitted.

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…

[*class|="text"] will also matched textWarning, textInfo, textCenter, etc.

Seems strange to me since the spec says the following:

Represents an element with the att attribute, its value either being exactly "val" or beginning with "val" immediately followed by "-" (U+002D).

it should match text-foo or text but not textFoo

Re: Bootstrap 2.3 Released

#65

Post by jameswyse »

fat wrote: post #23
dotborg wrote: post #11

Replace all CSS transitions with JavaScript transitions. why?

I'll probably write up something at length about this decision when/if it happens… but this is the current thinking: CSS transitions are just total shit to deal with in javascript. What people often don't realize is that there is an event for transitionEnd in javascript – but this isn't always fired in a reliable way – only when a transition successfully ends (which isn't all the time). This is incredibly problematic…

Thanks for taking the time to explain this fat, I had noticed problems with transitionEnd sometimes not firing but never got around to researching it.

Re: Bootstrap 2.3 Released

#66

Post by thiderman »

rgo wrote: post #35
fat wrote: post #24

Earlier quoted context omitted.

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

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.

That's a really bad thing in my eyes. Why teach a beginner that consistency is something that does not exist?

Also, non-english variables are an abomination! I've worked with code with some finnish variables. Not only is it harder to grok, it's actively distracting.

Re: Bootstrap 2.3 Released

#67

Post by roel_v »

beagle3 wrote: post #52
roel_v wrote: post #37

Earlier quoted context omitted.

"I don't want to start a flame war, but I was wondering if there is a rationale for prefering dash-case?" No, there isn't. It's one of those typical things that novice programmers fret about. Consistency within a code base is much more important than which style is used exactly. Having the style be a compile parameter would make sense to me, not switching from one to the other.

> Consistency within a code base is much more important than which style is used exactly. I know this is a commonly held belief, and I held it too for a short while. But then, I was managing a project that ran on both Linux (lower_case_name libraries), Windows (CapitalizeEachWord), had components in Python (ClassesAreLikeThis but variables_like_this), Java (camelCaseIsAnAbomination) and even some VB6 (don't even reme…

Well within several modules of the same project, I guess it's inevitable, and not that problematic, especially not between several languages; but seeing (at the top of one function)

int my_counter; char hostName[256]; double LIFESPAN;

doesn't make for pleasant reading, I'm sure you agree.

Re: Bootstrap 2.3 Released

#68

Post by perry5000 »

egeozcan wrote: post #48
egeozcan wrote: post #47

Earlier quoted context omitted.

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.

That submenu works great on my tablet and phone. Very easy to navigate. I hope it compels Mark and Jacob to reconsider the submenu for Bootstrap 3.

Re: Bootstrap 2.3 Released

#69

Post by aleem »

markdotto wrote: post #5
ddoolin wrote: post #3

Bootstrap 3 will be mobile-first? Didn't they say they had NO plans to make Bootstrap mobile-first? Interesting.

I don't ever recall saying that, but if I did, I'm happy to have been wrong. Super stoked about the direction we're going.

I am not sure what "mobile first" means, could you please explain what that means for the end-developers?

The only thing to that effect I see right now is that responsive less files will no longer be separate from the core. That will probably mean that I will be forced to support mobile platforms.

Is there more to it?

(Aside, wishing someone would take a deeper look at https://github.com/twitter/bootstrap/issues/4935)

Re: Bootstrap 2.3 Released

#70

Post by lengads »

blowski wrote: post #21
phoobahr wrote: post #8

Earlier quoted context omitted.

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.

Ctrl + F shows two. Time to update your regex-fu, or use simpler tools.

re.findall() returns all non-overlapping matches. We need to use a positive lookahead on the third part of the pattern to stop it from consuming the non-character:

  re.findall(r"[^a-zA-Z]([a-zA-Z]+)(?=[^a-zA-Z])", ..)
Post reply on HN