Cytoscape Wiki|
← Revision 1 as of 2007-07-18 23:45:35 →
Size: 2801
Comment:
|
Size: 2791
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| || '''RFC Name''' : ... || '''Editor(s)''': ... || |
##Fill in RFC Name, primary authors and editors, and the status of the RFC ##Example Status states include: Work in Progress, Open for Comment, Closed || '''RFC Name''' : Code Layering || '''Editor(s)''': AlexPico || '''Status''': Work in Progress || |
| Line 9: | Line 12: |
| == About this document == | == Proposal == |
| Line 11: | Line 14: |
| This is an official Request for Comment (RFC) for '''Add your text here'''. | ##The sections below may be useful when creating an RFC, delete the ones that are not |
| Line 13: | Line 16: |
| For details on RFCs in general, check out the [http://www.answers.com/main/ntquery?method=4&dsid=2222&dekey=Request+for+Comments&gwp=8&curtab=2222_1&linktext=Request%20for%20Comments Wikipedia Entry: Request for Comments (RFCs)] | '''Code Layering''' - for the purpose of enabling a command layer (headless mode) and different front ends (e.g., web-based or SVG). Some may see this as ''refactoring'', but I think we can identify critical feature-based goals that derive from code layering that can be more readily justified as project aims that are typically expected to produce something "new". |
| Line 15: | Line 18: |
| == Status == |
== Use Cases == * '''Headless Mode''': Something we talked about having for a while. Do people have particular projects that would benefit from this? * '''Web-based Front Ends''': there is evolutionary pressure for software these days to be more web-based (versus stand-alone or even web start). Can we come up with specific projects that would make use of this? * ''Cytoscape Server'': many at ISB would utilize this for larger network analysis projects and several would embed it into internal and external web sites * ''GenMAPP-CS'' funding is starting in August and we plan to hire someone to work on this sort of development in Cytoscape to expand the client options. * ''WikiPathways.org'' might be able to embed a special front end of cytoscape for advanced pathway analysis * ''http://t1dbase.org'' would like to be able to use Cytoscape directly through a web front end (Nat Goodman has directly requested it several times) * ''add here'' |
| Line 17: | Line 27: |
|
##Put the date and the status. Status can be e.g. "Not yet completely written", "Open for public comment", "Closed for public comment". There could be some explanation of the status Not yet completely written; please feel free to expand on content and idea |
== General Notes == == Requirements == == Backward Compatibility == * Identify critical areas effected by layering: * ''add here'' == Implementation Plan == * Identify collections of classes to be layered * Layer the code * Develop new features == Comments == |
| Line 25: | Line 48: |
|
== Proposal == ##The sections below may be useful when creating an RFC, delete the ones that are not '''Code Layering''' - for the purpose of enabling a command layer (headless mode) and different front ends (e.g., web-based or SVG). Some may see this as ''refactoring'', but I think we can identify critical feature-based goals derived from such efforts that can be more readily incorporated into project aims that need to produce something "new" in order to be justified. == Use Cases == * Headless Mode: Something we talked about having for a while. Do people have particular projects that would benefit from this? * Web-based Front Ends: there is evolutionary pressure for software these days to be more web-based (versus stand-alone or even web start). Can we come up with specific projects that would make use of this? * GenMAPP-CS funding is starting in August and we plan to hire someone to work on this sort of development in Cytoscape to expand the client options. * WikiPathways.org might be able to embed a special front end of cytoscape == General Notes == == Requirements == == Deferred Items == == Open Issues == == Backward Compatibility == == Expected growth and plan for growth == == References == == Implementation Plan == * ["/Implementation Plan"] == Comments == |
RFC Name : Code Layering |
Editor(s): AlexPico |
Status: Work in Progress |
Proposal
Code Layering - for the purpose of enabling a command layer (headless mode) and different front ends (e.g., web-based or SVG). Some may see this as refactoring, but I think we can identify critical feature-based goals that derive from code layering that can be more readily justified as project aims that are typically expected to produce something "new".
Use Cases
Headless Mode: Something we talked about having for a while. Do people have particular projects that would benefit from this?
Web-based Front Ends: there is evolutionary pressure for software these days to be more web-based (versus stand-alone or even web start). Can we come up with specific projects that would make use of this?
Cytoscape Server: many at ISB would utilize this for larger network analysis projects and several would embed it into internal and external web sites
GenMAPP-CS funding is starting in August and we plan to hire someone to work on this sort of development in Cytoscape to expand the client options.
WikiPathways.org might be able to embed a special front end of cytoscape for advanced pathway analysis
http://t1dbase.org would like to be able to use Cytoscape directly through a web front end (Nat Goodman has directly requested it several times)
add here
General Notes
Requirements
Backward Compatibility
- Identify critical areas effected by layering:
add here
Implementation Plan
- Identify collections of classes to be layered
- Layer the code
- Develop new features
Comments
How to Comment
To view/add comments, click on any of 'Comment' links below. 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. Here is an example to get things started: ["/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.