Rick, That sounds find to me. It seemed to me there were 3 directions to take Pyphy and/or Mavric: (1) A set of Python modules (2) A stand-alone program (3) A Loci plug-in We could and should do all three. So we have (1) Pyphy (Thomas) (2) Mavric (Rick) (3) Loci phylogenetic plug-in(s) (Loci developers) Okay with you, Thomas? Of course you can say Pyphy is developed at The Open Lab (URL). Ciao. Jeff Rick Ree wrote: > > J.W. Bizzaro wrote: > > > Hmmm. I guess eventually mavric will be part of Loci, if that's what you > > intend. I was under the impression that pyphy/mavric was just a Python module. > > This is particularly true when we consider that we have only made a sketch of > > how something like pyphy/mavric can be integrated. Is pyphy/mavric meant to > > work only with Loci? If so, then you can say it is part of The Loci Project. > > If pyphy/mavric will be separate for some time or only some derivative will be > > integrated into Loci, you can say it is part of The Open Lab. > > I propose that we just refer to the pyphy/mavric package as 'pyphy', with > the intention that eventually it could be used in developing the > phylogenetic components of Loci. Thomas, you could then just refer to it > as "trees were visualized using pyphy, a phylogenetic software toolkit > available from The Open Lab (url:)..." or something like that. > > The name mavric could be used for a stand-alone application, like the tree > editor I prototyped in gnome-python and which Thomas converted to Tk. > > How does that sound? > > --Rick > > _______________________________________________ > pipet-devel maillist - pipet-devel at bioinformatics.org > http://bioinformatics.org/mailman/listinfo/pipet-devel -- J.W. Bizzaro mailto:bizzaro at bc.edu Boston College Chemistry http://www.uml.edu/Dept/Chem/Bizzaro/ --