-
Notifications
You must be signed in to change notification settings - Fork 0
Short Term PhyloBox Requirements
andrewxhill edited this page Dec 14, 2010
·
3 revisions
A result of the GMOD Hackathon. A list of immediate requirements for PhyloBox integration into such projects as JBrowse and Gbrowse.
- finished Complete //Namespace-safe PhyloBox javascript widget (see Using-the-PhyloBox-Remote-Client)
- finished Two-way event communication for PhyloBox methods/events
- finished URL-fetch from PhyloBox serverside to get tree data. Client provides a url to the data.
- finished Read a client tree. API call to accept a PhyloXML-formatted file generated by JBrowse backend. This will draw the initial tree once Phylobox is instantiated by JBrowse.
- finished Send "node clicked" event to JBrowse. This is necessary for genome track selection in JBrowse (use cases above).
- Send "node rotated" event to JBrowse. This is necessary for rearranging genome tracks in JBrowse (use cases above). It could be achieved in two ways:
- Sending a updated ordering.(? need to talk to phylobox guys)
- Sending a list of the subset which was reordered.(? need to talk to phylobox guys)
- Send "node removed" event to JBrowse. This is necessary for deleting genome tracks in JBrowse simultaneously with deletion in Phylobox.
- finished For internal nodes: send all descendant leaf IDs
- finished For leaf nodes: send just those leaf IDs.