The current implementation (as of b5d2a65..., 24 Sept. 2009) provides few methods for customizing the feature glyphs within a single track. These
’customizations’ are defined by the strand/phase state of the feature, and
allow only for a limited number and type of glyph selections. This differs
substantially from the Gbrowse glyph generation scheme, which permits broad
glyph customization through perl callbacks in the configuration file.
Concept
It would be useful for users to be provided with some means for controlling the
glyphs selected for individual features within a track. There are (at least)
two immediate benefits to this.
It will be easier to ’combine’ multiple data types into a single track
while maintaining the visual distinctness of each data type.
It will provide for (possibly) more informative ’dynamic’ glyphs.
Current State
The current implementation (as of b5d2a65..., 24 Sept. 2009) provides few methods for customizing the feature glyphs within a single track. These ’customizations’ are defined by the strand/phase state of the feature, and allow only for a limited number and type of glyph selections. This differs substantially from the Gbrowse glyph generation scheme, which permits broad glyph customization through perl callbacks in the configuration file.
Concept
It would be useful for users to be provided with some means for controlling the glyphs selected for individual features within a track. There are (at least) two immediate benefits to this.
original LH ticket
This ticket has 0 attachment(s).