Difference between revisions of "Talk:GBrowse syn"
From GMOD
(→Upcoming Hackathon (7/11/2010)) |
(→User interface) |
||
| Line 8: | Line 8: | ||
* I'd like a global configuration file, like GBrowse 2.0 now has. To get anything up and running you need a specific config file, which feels wrong somehow. | * I'd like a global configuration file, like GBrowse 2.0 now has. To get anything up and running you need a specific config file, which feels wrong somehow. | ||
* Sometimes the alignment is broken into blocks (each one should be a bona fide GB track remember) can we have a uniform scale across all blocks? I think small blocks are sometimes drawn to a different scale. | * Sometimes the alignment is broken into blocks (each one should be a bona fide GB track remember) can we have a uniform scale across all blocks? I think small blocks are sometimes drawn to a different scale. | ||
| − | ** The rendering of rulers in small blocks is crappy | + | ** The rendering of rulers in small blocks is crappy. |
==== YES WE CAN! ==== | ==== YES WE CAN! ==== | ||
* Allow users to re-position and re-orient blocks of the sequence. For example, one sequence may be composed of a set of 'BAC' features. You could allow users to flip and drag BACs around on the sequence so as to maximize synteny (while also visualizing the associated paired end data, naturally), and then write out the changes in some format. | * Allow users to re-position and re-orient blocks of the sequence. For example, one sequence may be composed of a set of 'BAC' features. You could allow users to flip and drag BACs around on the sequence so as to maximize synteny (while also visualizing the associated paired end data, naturally), and then write out the changes in some format. | ||
| + | ** By looking at the sequence ontology, you can determine which features are sequence components, and can therefore be moved in such a way. | ||
=== Database === | === Database === | ||
Revision as of 16:22, 4 November 2010
Contents
Upcoming Hackathon (7/11/2010)
Here are some ideas for things to work on w.r.t GBsyn dev. etc.
User interface
- The tracks don't 'feel' like GB 2.0 tracks, and are described in the manual as 'gbrowse-like'. Why can't we have proper GBrowse tracks? Wouldn't this allow a lot of code to be refactored?
- I'd like to use my existing track configuration to configure tracks in GBsyn. Additional options could be added to the GBsyn conf to turn tracks off, because its a pain to reconfigure them all from scratch again (especially using GBrowse 1.7 syntax) for GBsyn.
- I'd like a global configuration file, like GBrowse 2.0 now has. To get anything up and running you need a specific config file, which feels wrong somehow.
- Sometimes the alignment is broken into blocks (each one should be a bona fide GB track remember) can we have a uniform scale across all blocks? I think small blocks are sometimes drawn to a different scale.
- The rendering of rulers in small blocks is crappy.
YES WE CAN!
- Allow users to re-position and re-orient blocks of the sequence. For example, one sequence may be composed of a set of 'BAC' features. You could allow users to flip and drag BACs around on the sequence so as to maximize synteny (while also visualizing the associated paired end data, naturally), and then write out the changes in some format.
- By looking at the sequence ontology, you can determine which features are sequence components, and can therefore be moved in such a way.
Database
- Make the use of 'namespace' (database table prefixes) for alignment data the norm.
- Add support for namespaces. (It's all too easy for one dataset to trash another).
- Make a GFF3 loader, dammit!
Behind the scenes
- Oh, also, could you go ahead and make GBrowse_syn run under fastcgi? kthxbai
Miscellaneous
- The GBsyn 'alignment blocks' look really nice. Can you add something similar to GBrowse to guide the eye between the overview, region and details panels?
