[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: AW: AW: [geclipse-dev] Separating geclise grid modelfrom eclipseworkspace
|
Hi Romain,
One thing that we did not take into account in this discussion is that
not only g-Eclipse makes use of the workspace. Actually a lot of
external plug-ins including org.eclipse.core.* use the .metadata
sub-directory of the workspace to store session relevant data in it. So
even if we could decouple our model completely from the workspace you
may be forced to have a workspace anyways.
Now I am not the expert on this. So maybe Markus can comment here.
> The user launches SimExplorer for distributing a simulation from it's
> desktop. He launches a simulation distribution. He stores anything
> possible in the distant information system database (a service of
> SimExplorer). Afterwards, he starts the application from another
> computer, he tries to retrieve the distributed application that is
being
> executed, but some objects refers to a local workspace (something that
> is hard to put in the information system database).
Yeah, I see your point!
> The solution might be to reconstruct a workspace from the information
> system. But I think it is a pain in the ass.
Another solution would of course be to make use of Eclipse's
synchronization methods. You could use for instance CVS or SVN to put
your workspace with all information (job descriptions, jobs, etc.) into
a repository that can be accessed afterwards by the same user from a
different machine or by other users with appropriate access rights. But
as I think you depend on your information database this may not be an
option, right?!
> That might be a good idea. But I think that making the workspace
> management optional, would be the best solution.
Maybe you're right here. Butt his is the prize for being an Eclipse
project. So honestly, I do not see a way to completely decouple
g-Eclipse from a workspace. So we may think about alternative solutions.
Cheers, Mathias
