← Revision 1 as of 2008-01-18 22:34:06 →
Size: 2360
Comment:
|
Size: 2681
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was renamed from CytoscapeEditor3 | |
Line 3: | Line 4: |
|| '''RFC Name''' : …|| '''Editor(s)''': … || '''Date''': … ||'''Status''': … || |
||'''RFC Name''' : CytoscapeEditor_Palette_3_0 ||'''Editor(s)''': Allan Kuchinsky, Michael Smoot ||'''Date''': 18th January, 2008 ||'''Status''': Under Construction || |
Line 9: | Line 8: |
~-''Provide a brief description of the purpose and goals of project.''-~ |
* Generalize the mechanism for generating the Cytoscape Editor's palette so that the full range of Cytoscape visual properties is accommodated in palette |
Line 12: | Line 10: |
~-''Describe why this project is being proposed and what issues are addressed.''-~ | 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 |
Line 21: | Line 19: |
Line 24: | Line 21: |
Line 29: | Line 25: |
1. '''Milestone 1: …''' | 1. '''Milestone 1: …''' |
Line 32: | Line 28: |
1. '''Milestone 2: …''' | 1. '''Milestone 2: …''' |
Line 45: | Line 40: |
*''Add comment here…'' |
* ''Add comment here…'' |
Line 49: | Line 42: |
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.''' | 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.''' |
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 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
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.