Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geclipse-dev] Plug-in dependencies 
Hi,

some items regarding the ui dependencies:

- just for the record: i removed the fake dependency of   efs.gria on UI 
components (images related method in the activator). If UI stuff is needed 
for the gria connections it should go to gria.ui.

- i added the new  glite.ui  plugin to the glite-feature and the build 
maps, i don't know if that is ready... probably Pawel you will make a more 
formal announcement for people to check it out from CVS.

- in efs.gridftp  the only dependency which remains is through the use of
   AbstractUIPlugin#.getPreferenceStore() ...

- in efs.srm it is just the MountAction class

- glite.info   depends on  info.ui  and org.eclipse.ui... that is just due 
to the Glue viewer filter , we should move that filter to glite.ui now

- same with gria.info for the filter.
  There was still another dependency, the Activator being a UIPlugin 
instead a plain one,  I converted that one.


- then we have all of
     gvid*
     launch.glogin*
     remotebuilder
     terminal*
     test.framework*
     webview
     worldwind
  which do not try to separate ui from non-ui parts. That is probably ok 
for some (like terminal, webview, worldwind ;-)  but i would tend to think 
that test.framework should have a test.framework.ui plugin with all the ui 
dependencies there. What do you think Kasia/Szymon?

    Gvid is problematic because VTK (eu.geclipse.vtk) depends on gvid, 
which therefore makes the vtk / vtk.ui separation useless.
Can we do something there Thomas?


You can see all the plugins which depend on e.g.ui here:
http://iwr-geclipse.fzk.de:8443/luntbuild/publish/gEclipse/mk_test/geclipse-1.0_N20080516-1550/artifacts/Dependencies.html#r-eu.geclipse.ui


Cheers, Ariel

Back to the top