Re: AW: [geclipse-dev] Separating geclise grid model from eclipse worksp

[Romain <reuillon@xxxxxxxx>]

Hi Mathias,
> As already stated in this new bug the implementations of the Grid model
> are tightly bound to the Eclipse workspace. 
I think this is a shame. Your model is well designed (high abstraction 
level) and you provide several implementations of it. It is a dream for 
whoever wants to implement applications that at some point should submit 
jobs to a distributed environment. Having a tight link to the eclipse 
workspace here is painful when you just want to benefit from the 
abstraction layer of geclipse within your own tools. For example we have 
an information system. It is able to store many information about our 
application for traceability purposes. I want it to store the jobs with 
a description, the id, the wms url.... for further use, but as long as 
IGridJobs and IJobDescription are linked with workspace objects seems 
pretty complicated.
> We always assumed that
> potential users do have a workspace since this is the very basic concept
> of Eclipse. Therefore it will hardly be possible to now decouple
> everything from the workspace. Nevertheless we will discuss the specific
> details within the bug.
>
> Just one further comment. I know that dealing with the workspace is a
> burden and not always easy. Nevertheless you gain a lot from using the
> workspace concepts, especially in terms of g-Eclipse. Even if we would
> be successful to decouple single classes (e.g. GridJob) from the
> workspace you definitely will loose functionality (e.g. direct links to
> the in/output files etc.).
>   
Actually I don't really need it. It is possible to disable it within the 
current context?
> Cheers, Mathias
> _______________________________________________
> geclipse-dev mailing list
> geclipse-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/geclipse-dev
>
>