| [geclipse-dev] Remarks and questions to eu.geclipse.info |
|
Hi All, During testing the M5 I had a deeper look into our
info-plug-in and some remarks and questions have popped up from that. Since
these are not really bugs I would rather like to discuss them on the list. So
here we go… 1) First
a very general point that I already discussed with Ariel. Should the info
plug-in be renamed to eu.geclipse.core.info? Ariel voted +1, I did -1, but in
the meantime I am at +1 :) Note that renaming it would also mean to put the UI
stuff into eu.geclipse.ui rather than in a separate eu.geclipse.info.ui
plug-in. Nevertheless this is not that important, just wanted to mention it for
the sake of completeness. Let’s come to the more important points… 2) The
info plug-in defines an extension point, i.e. eu.geclipse.info.infoService. What
is the purpose of this extension point? Do we really need this? I am convinced that
this is not needed since everything concerning model elements can be done with
the core’s extension points (at least this is what I believe :) 3) Furthermore
there is a second extension point defined, i.e. eu.geclipe.info.infoViewerFilter
which is used – as far as I understand – to plug-in the middleware
filters available from the info viewers action bar. Also here I would say this is
not necessary, at least if we are filtering not for middlewares (remember, we
are middleware independent, otherwise we would already have a middleware
extension point in the core) but for VO types (which brings the middleware into
g-Eclipse), i.e. GRIA, VOMS, etc. You could then get a list of all available
VOs by querying the VO manager and making use of the IVirtualOrganization#getTypeName()
method, this could give you the filter’s name. Nevertheless I would
recommend to not present filters for all VOs but only for VOs that are currently
assigned to at least one project. Currently I also have a GRIA filter no matter
if I have a GRIA VO – or better info service – defined. 4) Concerning
the filters we currently have them spread over the action bar (there are two,
the “Show only filled information elements” and the middleware
filters). I would favour a solution following the package explorer approach.
There you have a dedicated “Filters…” action under the views
menu that opens a dedicated dialog containing all available filters. Also note
the “Select the element to exclude from the view” field in that
dialog. Wouldn’t that be a great addition to our filters, having listed
there the GLUE elements? That’s all for the moment. Nick, maybe you
would like to comment (or anybody else)?! So going back to the M5 tests … ;-) Cheers, Mathias |