[Springide-eclip-developer] FW: Refactoring and Spring IDE

[Watkins, D. <dav...@fa...>]

Just 'seeding' the list!


> > With regards to the re-validate options then my refactoring=20
> stuff will=20
> > only pick up changes coming in via the refactoring actions (rename,=20
> > move etc), it doesn't pick up on direct changes to the=20
> code, however=20
> > it should be relatively simple to either add a context menu=20
> (which I=20
> > think is a bit 'clunky') or to add support for change=20
> listening in the=20
> > java editor.  The only problem with the latter is the speed=20
> with which=20
> > we can process changes coming from the editor.  We may need=20
> to look at=20
> > implementing localised revalidation.  Anyway, I'll take a look.
>=20
> Providing a context menu to Java editor should be feasible=20
> (the AnyEdit plugin is a very good sample). For limittion the=20
> re-validation only to those config files which uses the=20
> corresponding Java type as bean class we have to extend the=20
> Bean model. I will add support for looking up config files by=20
> a given class name for the localised revalidation.=20
> Support for asking the model if a given class name is used as=20
> a bean class (and for which beans) is already available. This=20
> is used by the new version of the BeansUILabelDecorator.
>=20
> David, maybe you can investigate for a way to add a resource=20
> change listener to the Java editor and calling the=20
> revalidation in an efficient way.
>=20
> I will refactor the BeansProjectValidator that it can be used=20
> independently from the Eclipse incremental builder (which it=20
> currently implements / extends).
>=20
> > Whilst we're on the subject is there a time line for the=20
> next release.
> > If it's reasonable way off I can move over some of the=20
> non-v3 specific=20
> > stuff to the core/ui packages (mainly the search pages).
>=20
> That would be cool.
>=20
> > I'm also
> > wanting to make the core model more active via the interfaces - for=20
> > instance it'd be nice top have a option to 'search for spring files'
> > which can parse non java resources looking for the DTD=20
> signature and=20
> > add them to the config list.  This woud make adopting=20
> Spring-IDE even=20
> > simpler for existing Spring users.  If possible, I'd like=20
> to do this=20
> > via the interfaces rather than dropping down to the=20
> internal classes.
>=20
> We have to think about refactoring the Spring IDE model=20
> interfaces in a way the Spring Framework bean factory does.=20
> Currently we have only one interface per object. To not=20
> clutter these interfaces with stuff which is only used in=20
> rare cases we should define specialized sub-interfaces, e.g.
>=20
>     interface IBeansClassAware {
>         // all the bean class related methods
>         boolean isBeanClass(String className)
>           :
>     }
>=20
>     class BeansModel implements IBeansModel, IBeansClassAware {
>        :
>     }
>=20
>     class BeansProject implements IBeansProject, IBeansClassAware {
>        :
>     }
>=20
>     class Bean implements IBean, IBeanClassAware {
>        :
>     }
>=20
> So let's collect all requirements and cluster the=20
> corresponding methods into specialized interfaces.
>=20
> > Also, out of
> > interest do you and Loren think we'd be better maintainining a low=20
> > level history/changes document or are you happy to read CVS=20
> comments?
>=20
> I started to maintain a changes.txt file for every plugin.=20
> Here are all major addition / modifications are listed. Maybe=20
> we can leverage this.
>=20
> Btw. shouldn't we switch with our discussions to the mailing=20
> list=20
> (https://lists.sourceforge.net/lists/listinfo/springide-eclip-
> developer
> )? Maybe we get additional ideas from other developers=20
> through the list.
>=20
> Cheers,
> Torsten
>=20
>=20
>=20
> On 14.09.2004, at 11:35, Watkins, David wrote:
>=20
> > Torsten,
> >
> > Fantastic news!  Many, many congratulations to you and Melanie.  He=20
> > looks very peaceful in the photo - hope he's not keeping you up all=20
> > night!
> >
> > With regards to the re-validate options then my refactoring=20
> stuff will=20
> > only pick up changes coming in via the refactoring actions (rename,=20
> > move etc), it doesn't pick up on direct changes to the=20
> code, however=20
> > it should be relatively simple to either add a context menu=20
> (which I=20
> > think is a bit 'clunky') or to add support for change=20
> listening in the=20
> > java editor.  The only problem with the latter is the speed=20
> with which=20
> > we can process changes coming from the editor.  We may need=20
> to look at=20
> > implementing localised revalidation.  Anyway, I'll take a look.
> >
> > Whilst we're on the subject is there a time line for the=20
> next release.
> > If it's reasonable way off I can move over some of the=20
> non-v3 specific=20
> > stuff to the core/ui packages (mainly the search pages).  I'm also=20
> > wanting to make the core model more active via the interfaces - for=20
> > instance it'd be nice top have a option to 'search for spring files'
> > which can parse non java resources looking for the DTD=20
> signature and=20
> > add them to the config list.  This woud make adopting=20
> Spring-IDE even=20
> > simpler for existing Spring users.  If possible, I'd like=20
> to do this=20
> > via the interfaces rather than dropping down to the=20
> internal classes.
> >
> > I appreciate you've got your hands full at the moment so=20
> don't worry=20
> > if you haven't got much time to spend on the project.  Also, out of=20
> > interest do you and Loren think we'd be better maintainining a low=20
> > level history/changes document or are you happy to read CVS=20
> comments?
> >
> > Anyway, congratulations once again.
> >
> > Cheers,
> >  dw
> >
> >
> >> -----Original Message-----
> >> From: Torsten Juergeleit [mailto:tor...@t-...]
> >> Sent: 13 September 2004 20:26
> >> To: Loren Rosen; Watkins, David
> >> Subject: Refactoring and Spring IDE
> >>
> >> David,
> >>
> >> would the following JIRA issue be resolved with your refactoring=20
> >> support for Spring IDE?
> >>
> >> http://opensource.atlassian.com/projects/spring/browse/IDE-21
> >>
> >> Or does it make sense to add an entry to the Java editor's context=20
> >> menu for re-validating all Spring projects? Maybe we could=20
> limit the=20
> >> re-validation to the config files where the corresponding=20
> Java type=20
> >> (opened in the Java editor) is used as bean class.
> >>
> >> BTW, currently I am a little short of time for Spring IDE.
> >> This is due our first baby child was born 8 days before=20
> >> (http://www.kliniken-mtk.de/babycards/baby/C94N518N.html ).
> >>
> >> Cheers,
> >> Torsten
> >>
> >>
> >
>=20
>=20