Hi,
Thanks for the reply Nicklas. It makes a lot of sense to create
abstract classes as you suggest. We'll investigate what things we'd
like to have in an AbstractPluginExecuter class, but mainly I think
is code having to do with data import/export and plugin permisssions.
But I'm sure oth
Adam Ameur wrote:
> Hi,
>
> I would like to extend some methods in the Base1PluginExecuter for
> another purpose.
I think we need to be careful about this. The Base1PluginExecuter and
BioAssaySetExporter was designed and implemented to solve ONE specific
problem: Being able to run plug-ins d
Hi,
I would like to extend some methods in the Base1PluginExecuter for
another purpose. I'm trying to create a more general version of the
plug-in that is allowed to run on both 1- and 2-channel data.
So if possible. I would want to have the following methods/classes
changed to 'protected':
Hi.
>
> I add this as a ticket. Can you specify the methods that you need
> acces to.
>
> /Johan
>
I tried using the "protected" modifier Kjell proposed. And for that worked
except for ListMap Which I think is a so called inner class of
Base1PluginExecuter. It had to be public.
I changed in
