[Owl-devel] How to organize 'runner' classes?

Jose M. Duarte jose.m.duarte at gmail.com
Tue Mar 16 12:08:14 EDT 2010

Hi Henning

That makes a lot of sense indeed. I would go for the solution of grouping
them all in one single package, owl.runners sounds good to me. Also all the
stuff in the tinker package should go in there too. Actually at the moment
the tinker package is also misnamed as it contains gromacs related stuff


On 16 March 2010 15:31, Henning Stehr <stehr at molgen.mpg.de> wrote:

> Dear developers,
> We have quite a few classes whose main purpose is to run some external
> program, parse the output and return results as a java object. They
> are usually called SomethingRunner.
> The examples that I could find are : DaliRunner, PolyposeRunner,
> MaxClusterRunner, BlastRunner and TCoffeeRunner.
> In addition there is the Tinker related stuff which has its own
> package owl.tinker and the interface to paul in the obscure package
> actionTools.
> Shall we group all these together in some package? If so, how should
> this package be named? Some ideas would be: owl.runners,
> owl.externalprograms
> The main intention would be to make them easier to find and to make it
> obvious that everything in the package will depend on some external
> executable which needs to be installed seperately.
> Or, shall we keep them in the proteinstructure and sequence package as
> it is the case now? The argument here would be that e.g. Blast is
> strictly sequence related while Dali only deals with structures.
> Any opinions?
> Cheers,
> Henning
> _______________________________________________
> Owl-devel mailing list
> Owl-devel at bioinformatics.org
> http://www.bioinformatics.org/mailman/listinfo/owl-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.bioinformatics.org/pipermail/owl-devel/attachments/20100316/fb97d6a3/attachment.html>

More information about the Owl-devel mailing list