Re: [geclipse-dev] Unwanted UI dependencies

[Ariel Garcia <garcia@xxxxxxxxxx>]

> Many of this problems are caused by a
> dependency to org.eclipse.compare (which should be easy to remove), but

i didn't realize that  org.eclipse.compare was really a UI plugin... that 
naming is really bad...

> > I see 2 possibilities:
> >
> > 1)       Create an extra ui plug-in for each efs plug-in, e.g.
> > eu.geclipse.efs.gridftp.ui, and move the ui functionality to these
> >
> > 2)       Incorporate the ui functionalities into the general
> > middleware ui plug-ins, e.g. eu.geclipse.globus.ui (BTW, I do not see
> > a eu.geclipse.glite.ui?!)

i vote for solution 2:
*  efs.gridftp contains just 3 classes dealing with the preference settings 
	-> these could go into globus.ui, and the gridftp path validator which can
  be trivially made UI-independent or put into globus.ui

* efs.gria has currently no ui-related classes 

* efs.srm has only the mount action delegate -> would fit in glite
  (glite.ui actually if it would exist ;-)

* efs.lfc has the most ui classes (8), several action delegates and the 
replicas-view related classes. These could also go into glite(.ui).
Third parties willing to use the efs.LFC code will either base on the 
geclipse framework (hopefully) or "steal" the code to avoid using the 
framework anyway... so i don't see an advantage keeping a separate 
efs.lfc.ui plugin

Cheers, Ariel