|
From: Arne L. (JIRA) <no...@at...> - 2007-08-11 09:01:24
|
[ http://opensource.atlassian.com/projects/spring/browse/RCP-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_25357 ]
Arne Limburg commented on RCP-165:
----------------------------------
Besides the issue to remove the commands-context.xml completely from the advisor, I would like to have a nice default for the menubar and toolbar. But I see that my default-commands-context.xml does no good step in that direction. What about a DefaultMenuBarCommandGroup that is created in getMenuBarCommandGroup if no commands-context is set or if the menuBarBeanName is not set. Same could go with the toolBar. We then could remove your magic bean names. I will create a patch with an empty CommandGroup in that case. If you agree, I would implement the DefaultMenuBarCommandGroup and DefaultToolBarCommandGroup.
> Eliminate need for special bean names when configuring Application and ApplicationServices
> ------------------------------------------------------------------------------------------
>
> Key: RCP-165
> URL: http://opensource.atlassian.com/projects/spring/browse/RCP-165
> Project: Spring Framework Rich Client Project
> Issue Type: Improvement
> Reporter: Oliver Hutchison
> Assignee: Jan Hoskens
> Fix For: 0.3.0
>
> Attachments: Application.java.patch, RCP-165.patch, RCP-165.patch
>
>
> We should totally eliminate the special bean names that are required when configuring the Application and ApplicationServices singletons. Both these classes should be configurable using DI.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|