Hi Julien, Thanks a lot for your interest and feedback! If I understand your example correctly, it is very similar to the time-zone selection example Hixie gave on this mailing list. As it so happens, I just added that as a use case for components at http://wiki.whatwg.org/wiki/Component_Model_Use_Cases.
Regarding sharing of data in your examples: I'm not sure it can work exactly as you described, because of confinement considerations (a component should not be able to access 'window', nor 'document', nor the DOM, without the embedding document's consent), but we are in the middle of writing a proposal that should address most of that (confinement, declarative syntax, data sharing, to be precise), which should be forthcoming soon. Cheers, - Roland On Mon, Oct 10, 2011 at 17:43, Julien Richard-Foy <[email protected]>wrote: > Hi, > > I’m interested in the component model proposal [1] and tried to > imagine what architecture patterns our apps would follow by using it. > I wrote my notes here [2] and I’d like you to read and comment them. > > The most difficult problem to solve seems to be the way components > will be bound together since we don’t control how they are instanciated and > configured. > > Regards, > Julien > > [1] http://wiki.whatwg.org/wiki/Component_Model > [2] http://substance.io/julienrf/dom-component-model/1 >
