- From: Mike Kamermans <nihongo@gmail.com>
- Date: Tue, 26 Mar 2013 14:48:35 -0400
- To: public-webapps@w3.org
Hey all, I've been playing with web components and custom elements for a bit, blogging about my understanding of it at http://pomax.nihongoresources.com/index.php?entry=1364168314 and writing a demo for the Mozilla "webmaker" dev group to see what we can do with them, which is hosted at http://pomax.github.com/WebComponentDemo/ This demo has a stack of custom elements that all "tack onto" a media element on the page, if there is one, with two pages, one with a media element, the other with an image instead, but identical code outside of that difference, using the components defined in http://pomax.github.com/WebComponentDemo/webmaker-components.html One thing we're wondering about how to play with is self-documenting components. Was there already work done on this, or has anyone else already played with that idea? Right now we've hardcoded the documentation as plain HTML, trying to come up with a nice way of autogenerating it by having some JS that checks whether the components were loaded as "the document itself" and if so, generate the documentation from the <element> definitions, but finding a clean way to include a general description as well as attribute documentation is tricky. If anyone has good ides for doing this, I'd be delighted to hear from you! Also, if there's anything on those pages that we did "wrong", or that can be done better, I'd also love to hear from you. These things feel like game-changers, and making things that use components and custom elements is proving extremely fun =) - Mike "Pomax" Kamermans
Received on Tuesday, 26 March 2013 18:49:06 UTC