Cytoscape Wiki|
← Revision 5 as of 2008-01-18 23:47:39
Size: 2681
Comment:
|
← Revision 6 as of 2008-02-11 23:06:21 →
Size: 3310
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| * Generalize the mechanism for generating the Cytoscape Editor's palette so that the full range of Cytoscape visual properties is accommodated in palette | * Generalize the mechanism for generating the Cytoscape Editor's palette so that the full range of Cytoscape visual properties is accommodated in the palette |
| Line 10: | Line 10: |
| The current Cytoscape mechanism for constructing palettes in the Cytoscape Editor is driven by the current Visual Style. Discrete mappings for Node fill color and shape are used to generate a set of palette entries with | The current Cytoscape mechanism for constructing palettes in the Cytoscape Editor is driven by the current Visual Style. Discrete mappings for Node fill color and shape are used to generate a set of palette entries with varying shapes and colors. Discrete mappings for Edge target arrow are used to generate a set of palette entries with varying target arrow shapes. This limitation is arbitrary and doesn't take advantage of the broad range of Node shapes, colors, size, border characteristics, and other visual properties that can be defined via the vizmapper. Likewise, for edges, the broad range of visual properties available include line width, line style, source arrow. The generation of the palette should be generalized so that any visual property that is defined in the vizmapper can be utilized and reflected in the editing tool. |
RFC Name : CytoscapeEditor_Palette_3_0 |
Editor(s): Allan Kuchinsky, Michael Smoot |
Date: 18th January, 2008 |
Status: Under Construction |
Proposal
- Generalize the mechanism for generating the Cytoscape Editor's palette so that the full range of Cytoscape visual properties is accommodated in the palette
Background
The current Cytoscape mechanism for constructing palettes in the Cytoscape Editor is driven by the current Visual Style. Discrete mappings for Node fill color and shape are used to generate a set of palette entries with varying shapes and colors. Discrete mappings for Edge target arrow are used to generate a set of palette entries with varying target arrow shapes. This limitation is arbitrary and doesn't take advantage of the broad range of Node shapes, colors, size, border characteristics, and other visual properties that can be defined via the vizmapper. Likewise, for edges, the broad range of visual properties available include line width, line style, source arrow. The generation of the palette should be generalized so that any visual property that is defined in the vizmapper can be utilized and reflected in the editing tool.
Use Cases
Provide examples of how the products of this project will be used.
Implementation Plan
Outline and describe the process and major issues related to implementing this proposal. Illustrate your plan when possible. Try this free online tool for making diagrams -> [http://www.best4c.com/editor/NetMapApplication.jsp Best4c] (draw; save; then insert hyperlink into this page)
Project Management
Project Timeline
Provide a timeline for implementation. Insert a graphic if you can. Try this free online tool for making project timelines -> [http://www.helpuplan.com/index.asp Help-u-Plan] (create a new chart; modify; right-click to save gif; then attach to this page)
Tasks and Milestones
Outline the major milestones and tasks involved in implementation.
Milestone 1: …
- Task 1: ...
- Task 2: ...
Milestone 2: …
Project Dependencies
Outline and projects that depend on this project, link to relevant RFC's and note at what point dependent projects could be started.
Related RFCs
Link to other related RFCs
Issues
List any issues, conflict, or dependencies raised by this proposal
Comments
Add comment here…
How to Comment
Edit the page and add your comments under the provided header. By adding your ideas to the Wiki directly, we can more easily organize everyone's ideas, and keep clear records. Be sure to include today's date and your name for each comment. Try to keep your comments as concrete and constructive as possible. For example, if you find a part of the RFC makes no sense, please say so, but don't stop there. Take the extra step and propose alternatives.