Opened 17 years ago
Last modified 17 years ago
#13 new enhancement
AnnotationColor mapper needs a user interface
|Reported by:||diane||Owned by:||diane|
|Priority:||major||Milestone:||Standing on our heads|
One might imagine that users would actually like to edit colors by doing something other than changing a text file.
The difficulty is deciding if annotations and motifs should be lumped together? and if so does the UI let you add motifs and annotations or just motifs? This is a bit harder as the definition of a motif and the generic annotation is very different. Motifs are defined by a sequence, while generic annotations are start/stop locations--so they definitely need different sets of input controls.
Change History (6)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
comment:3 by , 17 years ago
|Type:||defect → enhancement|
Another way to solve this would be to make a sequence class that includes a color type and make it possible to edit the color of any sequence type.
comment:4 by , 17 years ago
|Milestone:||Few Small Repairs → Standing on our heads|
comment:5 by , 17 years ago
|Milestone:||Standing on our heads → release_1.1|
Hmm... maybe we also need a some way of changing the shape?
comment:6 by , 17 years ago
|Milestone:||release_1.1 → Standing on our heads|
Also I should refactor how AnnotationColor is used.
There are many places where I have hard coded colors, and I have more than one instance of the AnnotationColor mapper, (PathWindow and GlTracks)
Might be nice if there was a single instance handling all of my colors, that gets initialized with default colors for things like forward and reverse compliment tracks.