> Could you please point us in the right direction.
The extension point can be found in the core: eu.geclipse.core.gridProjectFolder.
The fields of this extension point are:
id: A unique id
name: The name of this
folder
label: The default label
that will appear in the project for this folder
elementClass: The type of
elements that will be stored by default in this folder (has to extend or to
implement IGridElement)
preset: A boolean indicating if this folder should by default be
present in a new Grid project
icon: A (small) overlay
image that is used to mark the folder as a project folder for a specific type
of grid elements
Already existing implementations
can be found in eu.geclipse.ui for
the connection, job description and
job folders and in
eu.geclipse.workflow.ui for the workflow folder. BTW. Sylva, would it be
reasonable to also introduce a folder for visualizations, i.e. for
IGridVisualization objects?! I vote +1 for such a folder that may be optional,
i.e. preset=false.
I will not comment the
rest of your mail now since I first have to think about it (you’re the
expert for operators ;-) But hopefully the other members of our project have
some valuable comments?! Nevertheless I still have a bad feeling about having
such “shallow” projects in the sense of a VO. Another solution
would possibly be to define a special VO for operators (that may not be bound
to a specific middleware) rather than
using the Generic VO (which is thought to be only a fall back solution if
nothing else fits)?! We could even think about defining a “container VO”
that may contain a bunch of other VOs in order to collect functionalities and information across the borders of different
middlewares if this would help somehow.
Damn, now I did comment
the rest of your mail … well, it’s sometimes hard to just shut up
;-)
Cheers, Mathias