3 ms·

My reasoning behind this is to get developers working together to come up with future web components for use on the web. Rather than have lots of different com

My reasoning behind this is to get developers working together to come up with future web components for use on the web. Rather than have lots of different competing components, lets get a proper discussion going without the need for working groups - we'll just build the damn things, and release them in the wild. I've put up three ideas already - Calendar, Image Gallery and Lightbox - but if you have other idea, just raise an issue on the main website issues (https://github.com/WebComponents/webcomponents.github.com/issues https://github.com/WebComponents/webcomponents.github.com/is...) and I'll create it and make sure you join the organisation!

Honzo 14y ago
This vaguely reminds me of this... http://xkcd.com/927/ http://xkcd.com/927/
- SudarshanP 14y ago
  This may superficially look like yet another standard but is highly likely to be much better "Let us set up yet another committee to cook up yet another standard". The Google I/O talk mentioned on the other thread explains how we can separate out the semantics from the implementation and let components from different providers inter operate. I feel things like Shadow DOM will give real encapsulation for the first time in web development. As of now we either use Iframes or try(through self descipline) not to cause damage when mix components from different sources.
iambot 14y ago
I really like the idea, wondering how to make them as simple/un-opinionated enough so as to work with all other frameworks - a big ask (and not easy.) Do you imagine that they would all have zero dependencies? Perhaps the wiki/homepage should suggest a base way of interacting with said widgets.
- tanepiper 14y ago
  I would recommend you check out the GoogleIO talk on this: https://www.youtube.com/watch?v=2txPYQOWBtg https://www.youtube.com/watch?v=2txPYQOWBtg But yes, the idea is that what we have is zero-dependency, best practice components that could a) be used by any framework b) drive browser vendors to look at the best and most commonly used tags, so they can then be implemented natively.

Honzo 14y ago

This vaguely reminds me of this... http://xkcd.com/927/ http://xkcd.com/927/

SudarshanP 14y ago
This may superficially look like yet another standard but is highly likely to be much better "Let us set up yet another committee to cook up yet another standard". The Google I/O talk mentioned on the other thread explains how we can separate out the semantics from the implementation and let components from different providers inter operate. I feel things like Shadow DOM will give real encapsulation for the first time in web development. As of now we either use Iframes or try(through self descipline) not to cause damage when mix components from different sources.

iambot 14y ago

I really like the idea, wondering how to make them as simple/un-opinionated enough so as to work with all other frameworks - a big ask (and not easy.) Do you imagine that they would all have zero dependencies? Perhaps the wiki/homepage should suggest a base way of interacting with said widgets.

tanepiper 14y ago
I would recommend you check out the GoogleIO talk on this: https://www.youtube.com/watch?v=2txPYQOWBtg https://www.youtube.com/watch?v=2txPYQOWBtg But yes, the idea is that what we have is zero-dependency, best practice components that could a) be used by any framework b) drive browser vendors to look at the best and most commonly used tags, so they can then be implemented natively.