Re: [Springide-eclip-developer] Brainstorming for bean search functions

[Torsten J. <tor...@on...>]

Some additional info for clarification:

Search type 3 was a comment sent by someone who tried to sell Spring to  
his co-workers.
He wrote "... First, they wanted some way to make sure that all  
properties were mapped, so I thought it would be interesting to display  
which properties have values and which do not. ...".

Maybe we can offer a context menu action for a selected bean in the  
beans view which displays a view with all available properties of the  
bean classes together with their wiring state (value assigned or no  
value assigned).

Search type creates a kind of tree from wired beans. This search is  
already done for the beans graph editor. For a given config, config set  
or bean a list of all included beans is created. Then every bean from  
this listed is checked which other beans are referenced via properties  
or constructor arguments (including inner beans) and these referenced  
beans are to this list too.

Acess point c) is already used for the "Open Java Type" and "Show In  
Spring Beans View" text editor context menu actions. It's implemented  
as a "viewerContribution" via the extension point  
"org.eclipse.ui.popupMenus" , e.g.

    <extension
          point="org.eclipse.ui.popupMenus">
       <viewerContribution
             targetID="#TextEditorContext"
              
id="org.springframework.ide.eclipse.beans.ui.actions.beansConfigFile">
          <action
                label="%popupMenus.showInView.label"
                icon="icons/full/etool16/show_in_view.gif"
                 
definitionId="org.springframework.ide.eclipse.beans.ui.commands.showinvi 
ew"
                 
class="org.springframework.ide.eclipse.beans.ui.actions.ShowInView"
                menubarPath="additions"
                 
id="org.springframework.ide.eclipse.beans.ui.actions.showinview">
          </action>
     </viewerContribution>
   </extension>

The interesting part is the editor's context ID in the attribute  
"targetID".
The action uses the editor's current selection / cursor position to  
guess it's target.

Cheers,
Torsten


On 31.03.2005, at 19:39, Watkins, David wrote:

> Hiya,
> I can see the value of 4 (if I understood
> the idea correctly) however I'm not sure
> that 3 is paraticularly useful; I quite
> often have a bunch of default values and/or
> properties for hooking mock objects into
> my beans.  I wouldn't want to see those
> coming up as unassigned properties as I
> very rarely assign them.  Perhaps better
> would be a context option on a bean in the
> view to display available properties
> (and perhaps have something like the
> Source..Override/Implement Methods option
> in the JDT Editor which can insert some
> template <property/> markup for you).
> However I think this should be on a per bean
> basis, not across multiple beans.
>
> Going back to 4, I take it you mean being
> able to ask Spring IDE something like:
> Show me all the beans which get wired
> into this argument of this class (or
> it's subtypes)?
>
> Incidently, looking at your access point
> list (c), some time ago I looked at how to
> contribute to an 'unspecified' editor and
> couldn't see an easy way of doing it.  Given
> that Spring IDE is 'editor neutral' this may
> be tricky to implement.  However it may well
> be the case that I've just missed the relevant
> extension point!
>
> Cheers,
> dw
>
>
> P.S. are there any plans to look at adding the ability to follow import
> tags?  If not, I'll take a
> look at it when the fresh code arrives.
>
>
>> -----Original Message-----
>> From: spr...@li...
>> [mailto:spr...@li...]
>>  On Behalf Of Torsten Juergeleit
>> Sent: 31 March 2005 16:00
>> To: Spring IDE Developer List
>> Subject: [Springide-eclip-developer] Brainstorming for bean
>> search functions
>>
>> All,
>>
>> I'm thinking about adding a new plugin to Spring IDE's bean
>> factory plugins which brings support for searching the bean
>> model. Dave already created a nice extension to Spring IDE
>> whith this kind of functionality
>> (http://springui-ext.sourceforge.net/search.html ). This is a
>> great starting point.
>>
>> Now I'm just wondering which kind of search capabilities you
>> are interested in?
>>
>> The following is my take:
>>
>> 1. list of beans with a given name (already implemented by Dave)
>>
>> 2. list of beans with a given bean class (already implemented by Dave)
>>
>> 3. list of beans with unassigned properties (no property +
>> corresponding value defined for a bean class' public setter)
>>      http://opensource.atlassian.com/projects/spring/browse/IDE-37
>>
>> 4. list of beans referenced by a given model element (bean,
>> property or constructor argument)
>>
>>
>> And what are the access points for these search capabilities?
>>
>> Here is my best guess:
>>
>> a) additional pane in Eclipse list of different search panes (Dave
>> already implemented a combined pane for 1. and 2.)
>>
>> b) context menu for model elements selected in beans view (could be a
>> good fit for 3. and 4.)
>>
>> c) context menu for current cursor position in text editor
>>
>>
>> What do you think?
>>
>> Cheers,
>> Torsten
>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by Demarc:
>> A global provider of Threat Management Solutions.
>> Download our HomeAdmin security software for free today!
>> http://www.demarc.com/info/Sentarus/hamr30
>> _______________________________________________
>> Springide-eclip-developer mailing list
>> Spr...@li...
>> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by Demarc:
> A global provider of Threat Management Solutions.
> Download our HomeAdmin security software for free today!
> http://www.demarc.com/info/Sentarus/hamr30
> _______________________________________________
> Springide-eclip-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springide-eclip-developer
>