- From: <bugzilla@jessica.w3.org>
- Date: Tue, 30 Jul 2013 11:56:14 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22836
Dominic Cooney <dominicc@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dominicc@chromium.org
--- Comment #1 from Dominic Cooney <dominicc@chromium.org> ---
(In reply to comment #0)
> Every tech concept/architecture should derived from single First Principle,
> so that the concept/architecture is compact, consistent and easy to
> understand in future evolution.
This is an interesting idea. I'm not sure that I agree it has to be just one,
but let me think about it.
> Per my understanding, component model(web components) tries to model the UI
> to get UI better structured and reused. And we need a First Principle to
> guide this.
The experience from early adopters is that Web Components is useful UI and for
much more. UI is something relatively concrete that many web developers have
experience with so it is a good place to start explaining Web Components. Maybe
we should make another try at explaining the more general idea.
> I think the most suitable First Principle here can be Object Oriented.
> E.g. Custom Elements try to make html elements object oriented (support
> element encapsulation and extend)
I think object orientation is a bad metaphor; the composition of Custom
Elements is pretty different to objects. Although the ideas about encapsulation
and reuse are pretty close to the mark.
> Shadow DOM try to make dom tree object oriented(support dom tree
> encapsulation and extend)
> So base on above statement, I think we should have a better name for Shadow
> DOM, since this name can not reflect its core value & feature.
Do you have a suggestion for what this name would be?
> Also the same for the method to start shadow dom (ele.createShadowRoot).
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 30 July 2013 11:56:15 UTC