Differences between revisions 3 and 10 (spanning 7 versions)

Cytoscape 3.0 (and beyond) Development Modules

Comments:

A status of "Incomplete" means that essentially no work has been done for this module in 3.0. Module size is a rough estimate of how much code or data is contained in that module. Module impact refers to how much a change in that module will impact other modules. Module impact is not meant to be a value judgment! It merely tries to communicate how many other modules have dependencies on it.

model

Description:	The core network and data table models used by everyone else.
3.0 Status:	The API and an implementation are largely complete.
Who has done the work in 3.0:	UCSD with lots of feedback from others
Who did the work in 2.x:	everyone
Module size:	Large
Module impact:	Large

work

Description:	An API for definining and executing Tasks, configuring the Tasks, and supporting undo.
3.0 Status:	The API and implementation are largely complete.
Who has done the work in 3.0:	Pasteur, UCSD
Who did the work in 2.x:	(didn't exist prior to 3.0)
Module size:	Large
Module impact:	Large

logging

Description:	Both developer and user logging framework.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	Pasteur
Who did the work in 2.x:	UCSF, ISB
Module size:	Small
Module impact:	Medium

io

Description:	APIs for importing and exporting data including networks, tables, sessions, and images.
3.0 Status:	The API is largely defined, but all implementations need to be refined.
Who has done the work in 3.0:	UCSD, Pasteur, Toronto
Who did the work in 2.x:	everyone
Module size:	Large
Module impact:	Large

view-model

Description:	An API that defines the visualization of a network (and later table), but doesn't actually do the rendering.
3.0 Status:	The API and implementation are largely complete.
Who has done the work in 3.0:	UCSD, Daniel Abel
Who did the work in 2.x:	(didn't exist prior to 3.0)
Module size:	Medium
Module impact:	Large

vizmap

Description:	An API that modifies a view-model based on attribute (data table) values.
3.0 Status:	The API is largely complete and the user interface implementation is nearing completion.
Who has done the work in 3.0:	UCSD
Who did the work in 2.x:	(didn't exist prior to 3.0)
Module size:	Medium
Module impact:	Small

presentation

Description:	An implementation that renders (to screen, to image file, to ??) a network whose visualization is defined by a view-model.
3.0 Status:	The API has been sketched and an implementation is in place, but it needs a lot of refinement.
Who has done the work in 3.0:	UCSD
Who did the work in 2.x:	everyone
Module size:	Medium
Module impact:	Medium

attribute-presentation

Description:	An implementation that renders a data table.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	???
Who did the work in 2.x:	UCSD, others
Module size:	Small
Module impact:	Small

editor

Description:	A user interface that allows users to add, delete, and change nodes and edges in a network.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	???
Who did the work in 2.x:	Agilent
Module size:	Medium
Module impact:	Small

layout

Description:	An API and several implementations of layout algorithms that modify the view-model for a given network.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	???
Who did the work in 2.x:	UCSF, UCSD
Module size:	Large
Module impact:	Small

search/filters

Description:	An API and user interface that allows a network to be searched and/or filtered.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	???
Who did the work in 2.x:	MSKCC, Maital Ashkenazi, UCSD
Module size:	Medium
Module impact:	Medium

groups

Description:	An API and user interface that allows groups of nodes to be defined and captured as subnetworks.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	???
Who did the work in 2.x:	UCSF
Module size:	Medium?
Module impact:	Medium

merge

Description:	An API that provides for set operations on networks based on attributes of the networks.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	???
Who did the work in 2.x:	UCSD
Module size:	Small
Module impact:	Small

linkout

Description:	An API that allows objects in Cytoscape to be linked to web databases.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	???
Who did the work in 2.x:	MSKCC, Agilent
Module size:	Small
Module impact:	Small

webservices

Description:	An API that provides a common interface for accessing web based interaction databases.
3.0 Status:	Some work has been done, but incomplete.
Who has done the work in 3.0:	UCSD
Who did the work in 2.x:	MSKCC, Toronto, UCSD
Module size:	Small
Module impact:	Medium

scripting

Description:	An API that allows scripts written in other programming languages (Python, Groovy, Javascript, etc.) to access and use the Cytoscape API.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	UCSD(Kei, proof-of-concept code only)
Who did the work in 2.x:	UCSF, UCSD
Module size:	Small?
Module impact:	Small

swing-application

Description:	A Java Swing-based desktop application for visualizing and analyzing networks (what everyone knows today as "Cytoscape").
3.0 Status:	About 75% complete (excluding core plugins).
Who has done the work in 3.0:	UCSD
Who did the work in 2.x:	everyone
Module size:	Large
Module impact:	Large

command-line-application

Description:	A command-line application built from low-level cytoscape modules that can perform various tasks (e.g. load a networks, lay it out, and render it to an image file) without the need for a graphical user interface.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	???
Who did the work in 2.x:	(didn't exist prior to 3.0)
Module size:	Medium
Module impact:	Medium

plugin-manager

Description:	A user interface for downloading, installing, automatic-update, and otherwise managing cytoscape bundles.
3.0 Status:	The user interface is largely finished, but still needs to be integrated with the swing application.
Who has done the work in 3.0:	UCSD
Who did the work in 2.x:	ISB, UCSD
Module size:	Large
Module impact:	Medium

qa/testing

Description:	The management and oversight of the development, planning, and execution of unit tests, functional tests, acceptance tests, performance tests, and general promotion of "quality."
3.0 Status:	Incomplete.
Who has done the work in 3.0:	???
Who did the work in 2.x:	There are a few unit tests scattered about contributed by different groups, but no comprehensive strategy.
Module size:	Medium
Module impact:	it depends

architecture

Description:	The management and oversight of the overall Cytoscape architecture and how different modules interact with one another.
3.0 Status:	It exists, but is poorly documented.
Who has done the work in 3.0:	UCSD
Who did the work in 2.x:	everyone
Module size:	Small
Module impact:	Large

documentation

Description:	The management and oversight of documentation for Cytoscape including the website, user manuals, tutorials, developer documents, wikis, and API documention.
3.0 Status:	Incomplete.
Who has done the work in 3.0:	???
Who did the work in 2.x:	everyone
Module size:	Large
Module impact:	Large

dev-process

Description:	The management and oversight of the development processes, build tools, release tools and processes for Cytoscape.
3.0 Status:	Ongoing.
Who has done the work in 3.0:	ISB, Toronto, UCSD
Who did the work in 2.x:	everyone
Module size:	Small
Module impact:	Large

usability

Description:	The evaluation and refinement of Cytoscape usability including usability testing and tracking.
3.0 Status:	Inactive.
Who has done the work in 3.0:	???
Who did the work in 2.x:	Pasteur, ???
Module size:	Small
Module impact:	it depends

decorated-networks

Description:	A future project for providing enhanced visualizations of networks in cytoscape with other background and foreground graphics and text (e.g. cell location).
3.0 Status:	Two Google Summer of Code Project are ongoing
Who has done the work in 3.0:	UCSD (Kei. Proof-of-concept code only)
Who did the work in 2.x:	UCSF, MSKCC, Agilent
Module size:	Large?
Module impact:	Medium

web-application

Description:	A web-based version of Cytoscape.
3.0 Status:	Usable beta version complete and available as part of the beta.genemania.org website
Who has done the work in 3.0:	Lead: Christian Lopes (GeneMANIA group, Bader Lab, Toronto). Interest: Sarah Killcoyne, Hector Rovira (ISB), DanielAbel
Who did the work in 2.x:	(didn't exist prior to 3.0)
Module size:	Large
Module impact:	Small

database-backend

Description:	A future project that will provide a relational (or other) database backend for Cytoscape.
3.0 Status:	Future project.
Who has done the work in 3.0:	???
Who did the work in 2.x:	(didn't exist prior to 3.0)
Module size:	???
Module impact:	Small

extended-cydatatable

Description:	A future project that extends the interface for CyDataTable to allow things like joins and other relational database capabilities.
3.0 Status:	Future project.
Who has done the work in 3.0:	???
Who did the work in 2.x:	(didn't exist prior to 3.0)
Module size:	???
Module impact:	Small

Outdated_Cytoscape_3.0/DevelopmentModules (last edited 2011-02-24 15:35:42 by PietMolenaar)

-  ← Revision 3 as of 2009-04-20 01:24:23 →
  Size: 6618
  Editor: adsl-75-17-114-73
  Comment:
+  ← Revision 10 as of 2009-04-23 20:34:02 →
  Size: 11204
  Editor: nebbiolo
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 3:
+==== Comments: ====

A status of "Incomplete" means that essentially no work has been done for this module in 3.0.  '''''Module size''''' is a rough estimate of how much code or data is contained in that module.  '''''Module impact''''' refers to how much a change in that module will impact other modules.  Module impact is '''''not''''' meant to be a value judgment! It merely tries to communicate how many other modules have dependencies on it.
-Line 4:
+Line 7:
-''Description:'' The core network and data table models used by everyone else.



''Status:'' The API and an implementation are largely complete.



''Who has done the work:'' UCSD with lots of feedback from others
+||''Description:'' ||The core network and data table models used by everyone else.||

||''3.0 Status:'' ||The API and an implementation are largely complete.||

||''Who has done the work in 3.0:'' ||UCSD with lots of feedback from others||

||''Who did the work in 2.x:'' ||everyone||

||''Module size:''||Large  ||

||''Module impact:''||Large  ||
-Line 11:
+Line 15:
-''Description:'' An API for definining and executing Tasks, configuring the Tasks, and supporting undo.



''Status:'' The API and an implementation are largely complete.



''Who has done the work:'' Pasteur, UCSD
+||''Description:'' ||An API for definining and executing Tasks, configuring the Tasks, and supporting undo.||

||''3.0 Status:'' ||The API and implementation are largely complete.||

||''Who has done the work in 3.0:'' ||Pasteur, UCSD||

||''Who did the work in 2.x:'' ||(didn't exist prior to 3.0)||

||''Module size:''||Large  ||

||''Module impact:''||Large  ||
-Line 18:
+Line 23:
-''Description:'' Both developer and user logging framework.



''Status:'' Incomplete.



''Who has done the work:'' ???
+||''Description:'' ||Both developer and user logging framework.||

||''3.0 Status:'' ||Incomplete.||

||''Who has done the work in 3.0:'' ||Pasteur||

||''Who did the work in 2.x:'' ||UCSF, ISB||

||''Module size:''||Small  ||

||''Module impact:''||Medium  ||
-Line 25:
+Line 31:
-''Description:'' APIs for importing and exporting data including networks, tables, sessions, and images.



''Status:'' The API is largely defined, but all implementations need to be refined.



''Who has done the work:'' UCSD, Pasteur, Toronto
+||''Description:'' ||APIs for importing and exporting data including networks, tables, sessions, and images.||

||''3.0 Status:'' ||The API is largely defined, but all implementations need to be refined.||

||''Who has done the work in 3.0:'' ||UCSD, Pasteur, Toronto||

||''Who did the work in 2.x:'' ||everyone||

||''Module size:''||Large  ||

||''Module impact:''||Large  ||
-Line 32:
+Line 39:
-''Description:'' An API that '''''defines''''' the visualization of a network (and later table), but doesn't actually do the rendering.



''Status:'' The API and implementation are largely complete.



''Who has done the work:'' UCSD, Daniel Abel
+||''Description:'' ||An API that '''''defines''''' the visualization of a network (and later table), but doesn't actually do the rendering.||

||''3.0 Status:'' ||The API and implementation are largely complete.||

||''Who has done the work in 3.0:'' ||UCSD, Daniel Abel||

||''Who did the work in 2.x:'' ||(didn't exist prior to 3.0)||

||''Module size:''||Medium  ||

||''Module impact:''||Large  ||
-Line 39:
+Line 47:
-''Description:'' An API that modifies a view-model based on attribute (data table) values.



''Status:'' The API is largely complete and the user interface implementation is nearing completion.



''Who has done the work:'' UCSD
+||''Description:'' ||An API that modifies a view-model based on attribute (data table) values.||

||''3.0 Status:'' ||The API is largely complete and the user interface implementation is nearing completion.||

||''Who has done the work in 3.0:'' ||UCSD||

||''Who did the work in 2.x:'' ||(didn't exist prior to 3.0)||

||''Module size:''||Medium  ||

||''Module impact:''||Small  ||
-Line 46:
+Line 55:
-''Description:'' An implementation that renders (to screen, to image file, to ??) a network whose visualization is defined by a view-model.



''Status:'' The API has been sketched and an implementation is in place, but it needs a lot of refinement.



''Who has done the work:'' UCSD
+||''Description:'' ||An implementation that renders (to screen, to image file, to ??) a network whose visualization is defined by a view-model.||

||''3.0 Status:'' ||The API has been sketched and an implementation is in place, but it needs a lot of refinement.||

||''Who has done the work in 3.0:'' ||UCSD||

||''Who did the work in 2.x:'' ||everyone||

||''Module size:''||Medium  ||

||''Module impact:''||Medium  ||
-Line 53:
+Line 63:
-''Description:'' An implementation that renders a data table.



''Status:'' Incomplete.  



''Who has done the work:'' ???
+||''Description:'' ||An implementation that renders a data table.||

||''3.0 Status:'' ||Incomplete.  ||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||UCSD, others||

||''Module size:''||Small  ||

||''Module impact:''||Small  ||
-Line 60:
+Line 71:
-''Description:'' A user interface that allows users to add, delete, and change nodes and edges in a network.



''Status:''  Incomplete.



''Who has done the work:'' Agilent
+||''Description:'' ||A user interface that allows users to add, delete, and change nodes and edges in a network.||

||''3.0 Status:''  ||Incomplete.||

||''Who has done the work in 3.0:'' ||??? ||

||''Who did the work in 2.x:'' ||Agilent||

||''Module size:''||Medium  ||

||''Module impact:''||Small  ||
-Line 67:
+Line 79:
-''Description:'' An API and several implementations of layout algorithms that modify the view-model for a given network.



''Status:'' Incomplete.



''Who has done the work:'' UCSF, UCSD
+||''Description:'' ||An API and several implementations of layout algorithms that modify the view-model for a given network.||

||''3.0 Status:'' ||Incomplete.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||UCSF, UCSD||

||''Module size:''||Large  ||

||''Module impact:''||Small  ||
-Line 74:
+Line 87:
-''Description:'' An API and user interface that allows a network to be searched and/or filtered.



''Status:'' Incomplete.



''Who has done the work:'' UCSD
+||''Description:'' ||An API and user interface that allows a network to be searched and/or filtered.||

||''3.0 Status:'' ||Incomplete.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||MSKCC, Maital Ashkenazi, UCSD||

||''Module size:''||Medium  ||

||''Module impact:''||Medium  ||
-Line 81:
+Line 95:
-''Description:'' An API and user interface that allows groups of nodes to be defined and captured as subnetworks.



''Status:'' Incomplete.



''Who has done the work:'' UCSF
+||''Description:'' ||An API and user interface that allows groups of nodes to be defined and captured as subnetworks.||

||''3.0 Status:'' ||Incomplete.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||UCSF||

||''Module size:''||Medium?  ||

||''Module impact:''||Medium  ||
-Line 88:
+Line 103:
-''Description:'' An API that provides for set operations on networks based on attributes of the networks.



''Status:'' Incomplete.



''Who has done the work:'' UCSD
+||''Description:'' ||An API that provides for set operations on networks based on attributes of the networks.||

||''3.0 Status:'' ||Incomplete.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||UCSD||

||''Module size:''||Small  ||

||''Module impact:''||Small  ||
-Line 95:
+Line 111:
-''Description:'' An API that allows objects in Cytoscape to be linked to web databases.



''Status:'' Incomplete.



''Who has done the work:'' MSKCC, Agilent (support via right-mouse menu handler)
+||''Description:'' ||An API that allows objects in Cytoscape to be linked to web databases.||

||''3.0 Status:'' ||Incomplete.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||MSKCC, Agilent||

||''Module size:''||Small  ||

||''Module impact:''||Small  ||
-Line 102:
+Line 119:
-''Description:'' An API that provides a common interface for accessing web based interaction databases.



''Status:'' Some work has been done, but incomplete.



''Who has done the work:'' UCSD
+||''Description:'' ||An API that provides a common interface for accessing web based interaction databases.||

||''3.0 Status:'' ||Some work has been done, but incomplete.||

||''Who has done the work in 3.0:'' ||UCSD||

||''Who did the work in 2.x:'' ||MSKCC, Toronto, UCSD||

||''Module size:''||Small  ||

||''Module impact:''||Medium  ||
-Line 109:
+Line 127:
-''Description:'' An API that allows scripts written in other programming languages (Python, Groovy, Javascript, etc.) to access and use the Cytoscape API.



''Status:'' Incomplete.



''Who has done the work:'' UCSD
+||''Description:'' ||An API that allows scripts written in other programming languages (Python, Groovy, Javascript, etc.) to access and use the Cytoscape API.||

||''3.0 Status:'' ||Incomplete.||

||''Who has done the work in 3.0:'' ||UCSD(Kei, proof-of-concept code only)||

||''Who did the work in 2.x:'' ||UCSF, UCSD||

||''Module size:''||Small?  ||

||''Module impact:''||Small  ||
-Line 116:
+Line 135:
-''Description:'' A Java Swing-based desktop application for visualizing and analyzing networks (what everyone knows today as "Cytoscape").



''Status:'' About 75% complete (excluding core plugins).



''Who has done the work:'' UCSD
+||''Description:'' ||A Java Swing-based desktop application for visualizing and analyzing networks (what everyone knows today as "Cytoscape").||

||''3.0 Status:'' ||About 75% complete (excluding core plugins).||

||''Who has done the work in 3.0:'' ||UCSD||

||''Who did the work in 2.x:'' ||everyone||

||''Module size:''||Large  ||

||''Module impact:''||Large  ||
-Line 123:
+Line 143:
-''Description:'' A command-line application built from low-level cytoscape modules that can perform various tasks (e.g. load a networks, lay it out, and render it to an image file) without the need for a graphical user interface.



''Status:'' Incomplete.



''Who has done the work:'' ???
+||''Description:'' ||A command-line application built from low-level cytoscape modules that can perform various tasks (e.g. load a networks, lay it out, and render it to an image file) without the need for a graphical user interface.||

||''3.0 Status:'' ||Incomplete.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||(didn't exist prior to 3.0)||

||''Module size:''||Medium  ||

||''Module impact:''||Medium  ||
-Line 130:
+Line 151:
-''Description:'' A user interface for downloading, installing, automatic-update, and otherwise managing cytoscape bundles.



''Status:'' The user interface is largely finished, but still needs to be integrated with the swing application.



''Who has done the work:'' UCSD
+||''Description:'' ||A user interface for downloading, installing, automatic-update, and otherwise managing cytoscape bundles.||

||''3.0 Status:'' ||The user interface is largely finished, but still needs to be integrated with the swing application.||

||''Who has done the work in 3.0:'' ||UCSD||

||''Who did the work in 2.x:'' ||ISB, UCSD||

||''Module size:''||Large  ||

||''Module impact:''||Medium  ||
-Line 137:
+Line 159:
-''Description:'' The management and oversight of the development, planning, and execution of unit tests, functional tests, acceptance tests, performance tests, and general promotion of "quality."



''Status:'' Incomplete.



''Who has done the work:'' ???
+||''Description:'' ||The management and oversight of the development, planning, and execution of unit tests, functional tests, acceptance tests, performance tests, and general promotion of "quality."||

||''3.0 Status:'' ||Incomplete.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||There are a few unit tests scattered about contributed by different groups, but no comprehensive strategy.||

||''Module size:''||Medium  ||

||''Module impact:''||it depends  ||
-Line 144:
+Line 167:
-''Description:'' The management and oversight of the overall Cytoscape architecture and how different modules interact with one another.



''Status:'' It exists, but is poorly documented.



''Who has done the work:'' UCSD
+||''Description:'' ||The management and oversight of the overall Cytoscape architecture and how different modules interact with one another.||

||''3.0 Status:'' ||It exists, but is poorly documented.||

||''Who has done the work in 3.0:'' ||UCSD||

||''Who did the work in 2.x:'' ||everyone||

||''Module size:''||Small  ||

||''Module impact:''||Large  ||
-Line 151:
+Line 175:
-''Description:'' The management and oversight of documentation for Cytoscape including the website, user manuals, tutorials, developer documents, wikis, and API documention.



''Status:'' Incomplete.



''Who has done the work:'' ???
+||''Description:'' ||The management and oversight of documentation for Cytoscape including the website, user manuals, tutorials, developer documents, wikis, and API documention.||

||''3.0 Status:'' ||Incomplete.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||everyone||

||''Module size:''||Large  ||

||''Module impact:''||Large  ||
-Line 158:
+Line 183:
-''Description:'' The management and oversight of the development processes, build tools, release tools and processes for Cytoscape.



''Status:'' Ongoing.



''Who has done the work:'' UCSD, ???
+||''Description:'' ||The management and oversight of the development processes, build tools, release tools and processes for Cytoscape.||

||''3.0 Status:'' ||Ongoing.||

||''Who has done the work in 3.0:'' ||ISB, Toronto, UCSD||

||''Who did the work in 2.x:'' ||everyone||

||''Module size:''||Small  ||

||''Module impact:''||Large  ||
-Line 165:
+Line 191:
-''Description:'' The evaluation and refinement of Cytoscape usability including usability testing and tracking.



''Status:'' Inactive.



''Who has done the work:'' ???
+||''Description:'' ||The evaluation and refinement of Cytoscape usability including usability testing and tracking.||

||''3.0 Status:'' ||Inactive.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:''  ||Pasteur, ???||

||''Module size:''||Small  ||

||''Module impact:''||it depends  ||
-Line 171:
+Line 199:
-''Description:'' A future project for providing enhanced visualizations of networks in cytoscape with other background and foreground graphics and text (e.g. cell location).



''Status:'' Future project.



''Who has done the work:'' UCSF, MSKCC/Agilent (via changes to canvas object)
+||''Description:'' ||A future project for providing enhanced visualizations of networks in cytoscape with other background and foreground graphics and text (e.g. cell location).||

||''3.0 Status:'' ||Two Google Summer of Code Project are ongoing||

||''Who has done the work in 3.0:'' ||UCSD (Kei.  Proof-of-concept code only)||

||''Who did the work in 2.x:'' ||UCSF, MSKCC, Agilent||

||''Module size:''||Large?  ||

||''Module impact:''||Medium  ||
-Line 178:
+Line 207:
-''Description:'' A future project for a web front end for Cytoscape.



''Status:'' None for the Cytoscape Consortium, but various member organizations are developing independent projects.



''Who has done the work:'' ISB, Toronto
+||''Description:'' ||A web-based version of Cytoscape.||

||''3.0 Status:'' ||Usable beta version complete and available as part of the beta.genemania.org website||

||''Who has done the work in 3.0:'' ||Lead: Christian Lopes (GeneMANIA group, Bader Lab, Toronto). Interest: Sarah Killcoyne, Hector Rovira (ISB), DanielAbel||

||''Who did the work in 2.x:'' ||(didn't exist prior to 3.0)||

||''Module size:''||Large  ||

||''Module impact:''||Small  ||
-Line 185:
+Line 215:
-''Description:'' A future project that will provide a relational (or other) database backend for Cytoscape.



''Status:'' Future project.



''Who has done the work:'' ???
+||''Description:'' ||A future project that will provide a relational (or other) database backend for Cytoscape.||

||''3.0 Status:'' ||Future project.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||(didn't exist prior to 3.0)||

||''Module size:''||???  ||

||''Module impact:''||Small  ||
-Line 192:
+Line 223:
-''Description:'' A future project that extends the interface for CyDataTable to allow things like joins and other relational database capabilities.



''Status:'' Future project.



''Who has done the work:'' ???
+||''Description:'' ||A future project that extends the interface for CyDataTable to allow things like joins and other relational database capabilities.||

||''3.0 Status:'' ||Future project.||

||''Who has done the work in 3.0:'' ||???||

||''Who did the work in 2.x:'' ||(didn't exist prior to 3.0)||

||''Module size:''||???  ||

||''Module impact:''||Small  ||

Diff for "Outdated_Cytoscape_3.0/DevelopmentModules"