Release 3.0 Overall Goals

There are several motivations for release 3.0 of Cytoscape, but the overriding theme of the release is to refactor/redesign the code so that things become easier. Things in this case has several specific meanings:

Easier interface for plugin writers to understand and use.
Better modularity or layering making it easier for components of Cytoscape can be used in different contexts.
Clean up/refactor the structure of the existing Cytoscape core so that it can be more easily maintained, modified, and extended in the future.
Make backwards compatibility easier to maintain.
Clean up the user interface so that it's easier for users.

Desired Features

2.6. The primary feature for Cytoscape 3.0 is to do everything that 2.6 does. See [http://cytoscape.org Cytoscape].
Layer Cytoscape. Separate Cytoscape functionality into clearly defined layers or modules. The motivation is to allow alternative users of Cytoscape. For more information read: [:CytoscapeLayerRefactor: RFC 46], [:HeadlessModeRFC:RFC 6], [:WebFrontEnd: RFC 55].
Separate the view from the model. The motivation for this is to use Cytoscape in various headless (or alternatively headed) modes. See: [:HeadlessModeRFC:RFC 6], [:WebFrontEnd: RFC 55].
Command layer. In current versions of cytoscape one of the primary impediments to headless mode operation is the problem that the GUI it tightly coupled with almost all actions available to users (load file, save file, etc.). To solve this, Cytoscape needs a command layer that is cleanly separated from the application (not necessarily the view). This command layer should also be extensible so that plugin writers can add their own commands. See: (write an RFC).
Improved Event handling. Cytoscape currently uses a mish-mash of different events to signal system state changes. This is confusing, error prone, and causes performance problems. We need to develop a simple, clean Cytoscape event handling interface that can be used listen for and fire common events. See: [:EventHandling: RFC 52].
Custom graphics. We would like the ability for plugin writers to be able to define their own shapes and edges to be displayed and integrated into Cytoscape. See: [:RichLineTypes:RFC 32], and (write shape RFC).
Improve build process and package structure. We would like to simplify the build process for cytoscape so that all necessary libraries and plugins can easily be found and built with the core. See: [:DependencyManagement:RFC 44].
Local Attributes. Allow for attributes to be specific to networks in addition to maintaining the current global attributes. See: [:LocalAttributes:RFC 31], [:AttributeNamespaces:RFC 37].

Refactoring Strategy

Rather than rewriting Cytoscape from scratch we intend to refactor the existing code base. Since we already have a working version of Cytoscape that suits many people's needs quite well, a central tenet of the refactoring process will be to maintain a working version of Cytoscape. That means that each time a change is made (i.e. code checked into the trunk), all unit tests should pass and Cytoscape's main functionality should still work. This will be an iterative process with many small changes, rather than a few large ones. The hope is that with this process we will not lose functionality as we make changes.

Rough module refactoring plan

The general plan is to begin by cleaning up the existing code base and modularize what we can while changing as little as possible. The goal is to establish the modules that comprise Cytoscape and the dependencies between them. Once we have a coherent structure of existing code, we can begin redesigning modules to suit our new requirements.

Prepare the existing code base for refactoring.

Fix all deprecation warnings and remove unused code.
Begin building software using maven instead of ant.
Separate existing code into modules.
- Networks
- Attributes
- View
- Layouts
- VizMapper
- IO
- Plugins
Write unit tests.

Once the existing code base has been cleaned up, we can begin our redesign efforts for 3.0. The general strategy will be to work from the bottom up. That is to say, begin with the modules at the base of the dependency graph that all other modules depend on. This means work on Networks and Attributes first, followed by the View and on up through the dependency graph.

A time schedule has been put together to allow for time to discuss and plan each module and provide some end dates for when each discussion should be finished and implementation can begin. As much as possible we will work to adhere to this to allow 3.0 to be released in a reasonable time frame.

attachment:Cyto3ProjectPlan.xls

Cytoscape 3.0 Project Plan
ID	Name	Description	Duration	Predecessors
Milestones
1	First Relayered System
2	Relayered Core Initial Release
4	Modular System Milestone 1	Layer current code base	60.d
5	Separate code into layers	Per the RFC's: Graph model, View model, IO, View (presentation), Application, Command	20.d
6	Introduce temporary interfaces	Starting with the graph model, write interfaces to allow other layers to access the graph model and remove all dependencies to classes outside the graph model. Once it has no dependencies, work on other layers to ensure dependencies are correct and unidirectional.	40.d	5
7	Unit test/documentation	Per each layer, multiple people can work on this	20.d	6
8	Build Process - Maven	Mavenize separate layers to build modularly again start from the graph model	10.d
9	Merge 2.6 bug changes	If Mike's branch is used merge 2.6 changes into 3.0 branch	5.d
10	Recode Core Interfaces Milestone 2	Replace temporary interfaces with stable, planned interfaces. First relayered system finished	165.d	4
11	Graph Model	Use what's been learned from Step 1 to write use cases specific to the graph model as used within core code. Ideally 3-10 use cases should be identified and written.	90.d
12	Use Cases	Based on use cases develop a graph model interface for core usage. Add indexing pattern for fast graph iteration.	15.d
13	Interface Development	25.d		12
14	Plugin Interface Development	\|Determine if a separate Plugin interface is required to limit access to specific parts of the graph model.	10.d	13
15	Interface Implementation	25.d	14
16	Unit test/documentation	Each layer's interface needs to include unit tests and documentation in order to be considered finished.	15.d	15
17	View Model	Similar to Step 8, the difference being that this layer deals only in the persistable visual data that needs to be stored (but not the actual presentation layer).	60.d	13
18	Use Cases	3-10 use cases	10.d
19	Interface Development	Provide for view models that allow for multiple view models per graph model, are persistable (in IO) but not dependent on the actual presentation.	10.d	18
20	Interface Implementation	15.d	19
21	Unit test/documentation	15.d	20
22	IO	45.d	13,19
23	Use Cases	5.d
24	Interface Development	5.d	24
25	Plugin Interface Development	10.d	25
26	Interface Implementation	10.d	26
27	Unit test/documentation	15.d	27
28	View (Presentation)	???	19
29	Use Cases	10.d
30	Interface Development	??? Not sure about this one. The presentation layer may require more time and will be adjusted later	20.d	30
31	Plugin Interface Development	???	31
32	Interface Implementation		40.d	32
33	Unit test/documentation		15.d	33
34	Command	85.d	13,19
35	Use Cases	10.d
36	Interface Development		20.d	36
37	Plugin Interface Development	10.d		37
38	Interface Implementation		30.d	38
39	Unit test/documentation	15.d		39
40	Application	55.d	13,19
41	Use Cases	5.d
42	Interface Development	10.d		42
43	Plugin Interface Development	10.d		43
44	Interface Implementation	15.d		44
45	Unit test/documentation	15.d		45
46	Examine further componentization (OSGi)	??		4

Discussions

[:Oct2007SeattleMeeting: Seattle Meeting 2007]
[:CytoscapeRetreat2007/HackathonNotes: Amsterdam Hackathon 2007]
[:Cytoscape_3.0/Model: New Model]
[:Cytoscape_3.0/View: View Layer Proposal]
[:Cytoscape_3.0/HyperEdges: Hyperedges]
[:MavenInfo: Some info for using Maven]

Timeline