NOTE: We are working on migrating this site away from MediaWiki, so editing pages will be disabled for now.

Difference between revisions of "December 2 2010"

From GMOD
Jump to: navigation, search
(Minutes for December 9 (Suzi))
Line 1: Line 1:
== Agenda for 12/2/2010 WebApollo meeting ==
 
 
 
== Minutes for December 9 (Suzi) ==
 
== Minutes for December 9 (Suzi) ==
  

Revision as of 22:22, 9 December 2010

Minutes for December 9 (Suzi)

  • AI: Suzi to contact John about getting code for BRIX
  • Gregg
    • Draggable and Droppable issue. Both Gregg and Mitch had possible solutions. Went with Mitch's suggestion to implement the needed method in the constructor. Eliminated global variable and Nomi has picked up the changes which seem to work.
    • Ed: Firebug saying there is an error message when loading JBrowse, but no other visible effect on behavior (re. Chrome although both are using Firefox)
    • More optimizations for other UCSC data types in Trellis
  • Nomi
    • Working on allowing users to select multiple features and drag all at once to create annotation
    • Adding/removing features from selection set is working, and the creation of annotations upon drop is mostly working
    • However, JQuery doesn't directly support multiple-drag, so you can only see one feature being dragged, not all the selected features.
      • There is a multi-drag plugin for JQuery, but it seems to work on Chrome but not on Firefox.
    • One solution is to create a faux feature either
      • At the time the drag event begins
      • Or cumulatively as additional features are selected.
  • Ed
    • Current JBrowse only supports one level of nesting, so where do genes go?
    • Mitch, perhaps just keep genes out of the display level
      • NCList knows what features are contained in a region
      • Whereas subfeatures know about parent-child relation (e.g. gene-transcripts)
    • AI: Mitch to send example to Ed
    • JQuery used typically where server is generating HTML elements, client adds behavior
    • However in our case the HTML elements are being created on the client and are dynamic, so need to synchronize when the queries are run.