Well that sounds like a very reasonable plan. I especially like the idea of having a core package and project packages, that will hopefully make things a lot clearer.<br><br>And I would say it's better doing this soon rather than waiting to do it when it might be too difficult.<br>
<br>One thing I'd add to that if we are going to rearrange things is to also use the standard java layout with the DNS name as unique identifier. I've just checked and (surprisingly!) the <a href="http://owl.org" target="_blank">owl.org</a> domain is not taken! So I'm considering getting it. So basically we could name things org.owl.package (which is still a nice short name). Well now that I see Dan's email it's true that OWL is an acronym that is very likely to have been used a lot (even in a dyslexic way ;-) ). As he points out it is already in use in the bioinformatics context. Well I would say it is still ok, we knew that we had chosen a very popular name anyway...<br>
<br>One important question to ask before rearranging things is which external code do we want to keep up-to-date and linked to the latest development version of the library and which one we can consider "frozen" so that there's no need to update it (it will still be able to run with older tags/branches but not with the trunk). For sure CMView should be kept up-to-date. Any others?<br>
<br>Jose<br><br><br><br><br><br><div class="gmail_quote">On 19 March 2010 11:13, Henning Stehr <span dir="ltr"><<a href="mailto:stehr@molgen.mpg.de" target="_blank">stehr@molgen.mpg.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Dear developers,<br>
<br>
since we are currently rearranging some stuff in OWL which always<br>
makes it necessary to<br>
update imports and calls in other projects, maybe its a good time to<br>
think about the package<br>
structure in general to make OWL fit for the future.<br>
<br>
So here are some suggestions for changes to the package structure in OWL:<br>
<br>
Minor changes:<br>
<br>
- move all SomethingRunner classes from owl.proteinstructure and<br>
owl.sequence to owl.runners<br>
- create a subpackage owl.runners.blast and move all Blast related stuff there<br>
- move owl.tinker to owl.runners.tinker and create owl.runners.gromacs<br>
for gromacs stuff<br>
- create a subpackage proteinstructure.graphs and move all RIG and AIG<br>
related stuff there<br>
- maybe create proteinstructure.graphs.rigs and proteinstructure.graphs.aigs<br>
<br>
Major changes:<br>
<br>
- make a root package 'owl' and move everything there, i.e.<br>
owl.proteinstructure, owl.sequence, ...<br>
this would be clearer and prevent name conflicts with other<br>
libraries which may also contain e.g. a 'sequence' package<br>
<br>
- currently there are two types of packages:<br>
1. those containing collections of basic classes such as sequence,<br>
proteinstructure, features, connections, runners and<br>
2. those containing essentially independent projects such as casp,<br>
deltaRank, embed, sadp.<br>
Suggestion: Create a package owl.core and move all packages from 1.<br>
there. The basic idea would be that 'core' should<br>
be stuff that is used by many projects and 2. stuff that is more for a<br>
specific usecase<br>
- if we do the above, owl.proteinstructure.decoyScoring should be<br>
moved to owl.decoyScoring<br>
<br>
As you can see some of these are more long term plans but maybe it's<br>
less painfull to do it all together so that hopefully<br>
the package structure can remain stable for a while.<br>
<br>
For the moment, I won't do anything, but what do you think about these<br>
changes? We can dicuss later when would be<br>
a good time to actually do it.<br>
<br>
Henning<br>
<br>
_______________________________________________<br>
Owl-devel mailing list<br>
<a href="mailto:Owl-devel@bioinformatics.org" target="_blank">Owl-devel@bioinformatics.org</a><br>
<a href="http://www.bioinformatics.org/mailman/listinfo/owl-devel" target="_blank">http://www.bioinformatics.org/mailman/listinfo/owl-devel</a><br>
</blockquote></div><br>