Hi, It's true that we should have unified UI's for all the applications. But reinventing the front-end MVC frameworks won't be a good idea (agree with Chan's idea). IMO we should look deeper into this and find a proper way to do the front-ends of our application (at least selecting the technologies & setting-up guidelines for UI design will be helpful).
Thanks, Best Regards, Lakshitha Harshan Software Engineer Mobile: *+94724423048* Email: hars...@wso2.com Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com <http://wso2.com/>* lean.enterprise.middleware. On Mon, May 5, 2014 at 9:44 AM, Pubudu Dissanayake <pubu...@wso2.com> wrote: > Please refer my in-line comment. > > > On Sun, May 4, 2014 at 9:29 AM, Chanaka Jayasena <chan...@wso2.com> wrote: > >> I agree that we need to unify the look and feel of these UIs. When >> working with WSO2 Cloud the importance of unified look and feel is more >> visible. Considering the top and left menus usability wise both have pros >> and cons. Generally it's good to have a left side menu when there are >> growing number of options for it. In the Cloud UI it's better to have the >> menu at the top, since we have to inject the same menu to the App Factory >> UI and API Store/Publisher UIs. >> >> @Dilshan, API Store, API Publisher, and App Factory is done with an older >> version of Caramel. This is why there is a significant difference in the >> coding pattern. I don't think Caramel existed when the API Store/Manger >> applications were started developing. The latest version of Caremel we use >> for Stratos Web Console is way better than the older versions. It pushes >> front end developers to write clean code without messing with complex >> jQuery Dom manipulation to present data to the UI. We have handlebars.js >> with Caramel. Even though handebars.js ( Template Engine) and AngularJS ( >> HTML Compiler and data binder ) is completely different things, using them >> together doesn't make sense IMO. Chthura please do a research and find out >> that his need for AngularJS is filled by handebars.js or not. >> >> To have a consistent look and feel in Carbon products, the way Carbon UI >> initially developed helped. If we can have a similar patten where there is >> a core component with default styles, layout and let each product override >> these styles with there own, it will drive every product to have a common >> look and feel. >> >> Indeed, Having unified UI framework is a must and let products to build > their own UI is a bad idea. We should come up with a proper structure ( > previous carbon releases has this component.xml based approach ) therefore > we can build on top of it (hence can re-use it for future carbon UI > framework) . IMO consistency has to be there. > > >> thanks, >> Chanaka >> >> -- > *Pubudu Dissanayake* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > Mobile: 0775503304 > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
