But, if there are two competing components having the same menu name, and they want both UIs on the product, the solution is not hiding, rather to have names that not conflict.
Also, if you do not want a UI, then right model is not to hide the UI, rather not to have that UI component at all, right? On Thu, Aug 1, 2013 at 11:35 PM, Sriskandarajah Suhothayan <[email protected]>wrote: > > Hi > > Currently when we install a UI bundle it will automatically add its Menu > links on the left hand side of the Management Console. > > Though this is really powerful it also have a disadvantage when it comes > to the common features that are used in most of the products. > > E.g Eventing this creates a menu item called "Topics" which may be > meaningful for MB but its confusing for CEP & AS and other products that > uses this component. This is the same for services which also brings > "Modules" section which is not useful for most of the products. > > Due to this, it is very confusing for the first time user to understand > where to start! > > As a solution I like to suggest to have a config file at the product level > that will hide these UI menus which doesn’t make sense, and on each > products UI feature they can have the component.xml that gives the renamed > values. > > Thought? > > Thanks > Suho > > -- > *S. Suhothayan > * > Associate Technical Lead, > *WSO2 Inc. *http://wso2.com * > <http://wso2.com/>* > lean . enterprise . middleware > > *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ > twitter: http://twitter.com/suhothayan | linked-in: > http://lk.linkedin.com/in/suhothayan* > * > * > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
