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

Brick – UI Components for Modern Web Apps

mozilla.github.io

Post reply on HN
Print view View original

61–70 of 78 posts

Re: Brick – UI Components for Modern Web Apps

#61

Post by jnbiche »

k3n wrote: post #30
bpatrianakos wrote: post #28

This is cool and certainly useful but I have concerns. Forgetting for a moment that this is a shim and imagining that all browsers support this natively, isn't this sort of thing outside the intended purpose of html. Html should describe content not styling and this sort of thing seems ripe for abuse. I thought XML was the markup language for describing custom data. Adding the ability to create your own DOM elements…

Isn't that pretty much the M.O. of Angular? Not that it makes it right or wrong, but this just seems like a different take on the same (or similar) concepts.

The web components spec is precisely what AngularJS has been anticipating since Angular's inception. I believe the idea was (and still may be) to integrate web components once they are officially adopted by the major browsers.

Re: Brick – UI Components for Modern Web Apps

#62

Post by varunkumar »

potch wrote: post #31
jwilliams wrote: post #2

Interesting, although I think the "beta" is quite literal. Seems to lack a bit of polish. The one I was most interested in was the Date Picker, but locks up Chrome (28) and Safari (6) on my machine. http://mozilla.github.io/brick/component/datepicker/demo/ind...

Hi! I work on Brick. Yes, there are still rough edges on these components, and we're putting them out there in the hopes of getting feedback and bug reports- a traditional beta.

Hi, Is there any documentation to read about the implementation of these components? Does it use x-tags??

Re: Brick – UI Components for Modern Web Apps

#65

Post by rubyn00bie »

I think it's fucking awesome and it works like a boss in FF 24 (beta) on OS X. I'm very excited about this project only because standard UI elements are so irritating to make (after having done it hundreds of times) and the alternative libraries (in my opinion) all do too much and too little at the same time.

For everyone complaining about Chrome, I would like to say this is "beta" and "ahahahahaha."

Not to be malicious though! I just have a really shit experience on the web with a lot developers only targeting Chrome/Webkit. Like ScalaTour for instance-- a wretched experience if you're /not/ using Chrome (read unusable).

It's nice to see it go the other way for once! ;-)

Re: Brick – UI Components for Modern Web Apps

#68

Post by csuwldcat »

itry wrote: post #57

Calendar looks broken in FF and Chrome here. All I see is: 21 21 21 21 21 21 21 21 21 21 21 According to Browsershots it looks like this on many browsers: http://browsershots.org/http://mozilla.github.io/brick/compo... Same with the datepicker. Some other stuff also looks broken. I would much prefer one piece of javascript per component. So if I liked one, I could use it and improve it. Im not so much inclined to use…

Each component is isolated in just the way you describe, the only requirement is the base X-Tag Web Component library.

Re: Brick – UI Components for Modern Web Apps

#69

Post by jwilliams »

potch wrote: post #31
jwilliams wrote: post #2

Interesting, although I think the "beta" is quite literal. Seems to lack a bit of polish. The one I was most interested in was the Date Picker, but locks up Chrome (28) and Safari (6) on my machine. http://mozilla.github.io/brick/component/datepicker/demo/ind...

Hi! I work on Brick. Yes, there are still rough edges on these components, and we're putting them out there in the hopes of getting feedback and bug reports- a traditional beta.

Cool. I see the date picker has been fixed - thanks muchly & thanks for putting this out there.

In terms of feedback :) I gave it a shot. The only one that had a native date picker component (on my setup) was Chrome. The polyfill version didn't seem fully operational (just an overflow list of the same date?).

The Chrome native suffers from the same UX snafu that so many Date Pickers do - it's fine for relative dates, but terrible for absolute ones. If you want to schedule an event in a week it's great. Or of you want to search for flights.

However, if you want to enter a Date of Birth, it's terrible. You have to scroll through hundreds of months to get to the year you want.

So maybe you fall back to typing? In the native picker in Chrome, you can muddle through the day/month piece, but you can't type a straight year. e.g. start by typing "19" for "1975" and it'll match "1909". This also makes it impossible to enter a date in the 2000's!

You do get a "spinner" that might let you set the year, but the buttons are so small I think it defies practical usability.

Bah! Interestingly the iOS version does not suffer from this gripe as has a slot-machine three drum date selector. It does default to today, but it's pretty easy to move +/-50 years in either direction.

Sorry, that was a genuine rant. I know this is not intrinsic to Brick, but for me a universal Date Picker is #1 bugbear that I'd like it to solve.

(* The Chrome one also defaulted to the wrong timezone. Clicking "today" selected the wrong date.)

Post reply on HN