Following are some of the requirements I would like to see in UI component model. Just brainstorming.
1. Change and develop web app without building the product. ( As we discuss web app will get assembled at build/run time If we can assembled in development time it will save lot of time ) 2. Permission model which will show and hide UI components based on user roles. 3. Framework level support to enhance web application security. 4. L10n & I18n Also I wonder if the components that we write can be included as web-components. Cheers Jo On Tue, Jul 21, 2015 at 2:51 PM, Manuranga Perera <[email protected]> wrote: > This is the information I captured, please add if I missed anything. > > * API Analytics could be written using UES, but this will not be > immediately done. since the current static app is in a shippable state. > * There will be an effort to develop the UES dashboards using UI component > model. > * Dashboard render will be an single embeddable component which will take > the dashboard definition as an input. > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > -- -- *Joseph Fonseka* WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 772 512 430 skype: jpfonseka * <http://lk.linkedin.com/in/rumeshbandara>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
