Re: [Treebase-devel] phylowidget issue

[William P. <wil...@ya...>]

On Nov 1, 2010, at 11:08 AM, Rutger Vos wrote:

> To me, tree-editing seems like an odd requirement anyway. It would be
> much better for all involved if all editing is done inside client-side
> mesquite.

Well.. as it is, we currently use two completely different versions of PhyloWidget in TreeBASE. On the search/browse side, we use the latest version of PhyloWidget from phylowidget.org(*) -- and launched from the phylowidget.org site. On the submission side, we use a locally (i.e. server) stored, older stripped-down version, but modified to allow writing to the database.  One solution is to replace the search/browse links so that they point to jsPhyloSVG. 

bp

(*) that's not entirely true, in that for trees accessed through /phylows/, they are displayed in the older, stripped-down version -- which, is an oversight. It would be better if that, too, used the latest phylowidget.org version, or alternatively, jsPhyloSVG.