+1, we need this. I am looking in to extending caramel to support self-contained components.
On Sun, Jun 2, 2013 at 11:08 AM, Ruchira Wageesha <[email protected]> wrote: > Hi All, > > One interesting thing I have found regarding UI developments is, component > framework[1]. This is something you can use without waiting till the > support of Web Component specification[2] by each and every browser. > > Using component framework, you can group any UI functionality into > components, including js, css and html in a way they become self contained. > Every component defines its dependent component(as we do with maven) and > any component can be used independently if it's dependencies are available. > > Also, the components can be registered in a repository(on in our store) > where different people can go and grab components they want. *This way, > UI components developed by AppFactory team can be reused by any other team > * which is great thing for the UI layer, since we have many different > products with UIs. > > Only limitation here is, it uses node based build tool, but we can easily > write a maven plugin to do that. > > WDYT? > > [1] https://github.com/component/component > [2] http://www.w3.org/TR/components-intro/ > [3] > https://github.com/component/component/wiki/F.A.Q#what-about-web-components > > -- > *Ruchira Wageesha > **Associate Technical Lead** & Member, Management Committee, Development > Technologies* > *WSO2 Inc. - lean . enterprise . middleware | wso2.com* > * > email: [email protected], blog: ruchirawageesha.blogspot.com, mobile: > +94 77 5493444* > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- With regards, *Manu*ranga Perera.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
