|
From: Torsten J. <tor...@on...> - 2004-10-18 20:57:50
|
I did some refactorings, mainly replacing redundant local data from the
internal models of the ui and graph plugin with a reference to the
corresponding element of the core's model. So the UI's property sources
are reusable because they depend on the core plugin's model only.
To reduce coupling of the graph to the ui plugin GraphEditorInput
encapsulates all the code which depends on the ui plugin.
For navigating to a specific node in the BeansView the new type
BeansViewLocation was introduced. By using this type any plugin is able
to select a node within the BeansView, e.g.
BeansViewLocation location = new BeansViewLocation();
location.setProjectName("myproject");
location.setConfigName("myconfig");
location.setBeanName("mybean");
location.setPropertyName("myproperty");
location.show();
Finally a new context menu entry (Open Bean Class) was added to the
bean nodes within the BeansView.
I updated the feature available on the Spring IDE update site.
Maybe you can give it a try.
Hopefully we can release the new version of Spring IDE this week?!?
Any feedback appreciated...
Cheers,
Torsten
|