What's New

• Developer's documents update in progress - Kei (3/10/2009)

• Current progress on Cytoscape 3.0 development is monitored at /DevelopmentModules

Quick Start

• Quick start guide for Cytoscape 3 developers

• Start guide for Cytoscape 3 developers using Eclipse

• 3.0 API -- Please note that this still an active work-in-progress and subject to change at any time!

Plugin Development

This is a first version of documentation for Cytoscape 3.0 geared towards plugin developers Pages under this header will be put in a proper directory structure. In the near future all documentation regarding Cytoscape 3.0 will come in a clean separate wiki.

• Start page for plugin development for Cytoscape 3; getting started

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 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: RFC 46, RFC 6, RFC 55.

• Separate the view from the model. The motivation for this is to use Cytoscape in various headless (or alternatively headed) modes. See: RFC 6, 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: Command Layer Discussions.

• 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: 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: 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: RFC 44.

• Local Attributes. Allow for attributes to be specific to networks in addition to maintaining the current global attributes. See: RFC 31, RFC 37.

• Dynamic language support. Implement a built-in support to access Cytoscape API from dynamic (scripting) languages. See: Scripting RFC

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. Start dates will be added after 2.6 is officially released.

Layer design discussion schedule

API naming

The following table summarizes the classes that represent a given object in each layer.

* After discussing things at the second mini-retreat, we realized that visualizing CyDataTable/CyRow/CyColumns should have the same view-model and presentation layers that networks/nodes/edges have. We haven't discussed these, nor has anyone proposed names for them, which is why those fields are filled in.

Project Plan

See attachment for a nicely formatted version of the table below that includes time estimates, potential dates and notes regarding each. Please keep in mind this is meant to be very high level and will gain details through our discussions of each module. Cyto3ProjectPlan.xls

Note also that the dependencies and time estimates can change. Some of these things are potentially doable in parallel so we will update this as we determine which pieces are being done. As people volunteer for parts we will also add them to the table to keep everyone aware of what is being done.

Visual Development Timeline

This diagram displays provides lots of information:

• It provides a best (initial) guess of which modules will exist in Cytoscape 3.0.
• It shows some of the dependency relationships between modules.
• It groups modules into layers (based on color).
• Some modules (pink) haven't been put into layers because there is some question about which layer they should go in, but they have been put near the modules where they might belong.
• We will begin discussions at the bottom and work our way up (as indicated by the time arrow). There are tentative numbers assigned to the modules which we will discuss first.

Design Discussions

• Seattle Meeting 2007

• Amsterdam Hackathon 2007

• New Model

• View Layer Proposal

• Hyperedges

• Using Maven with Cytoscape This includes links to plugins for Eclipse, IDEA and NetBeans as well as descriptions for use with Eclipse.

Mini-Retreat Discussions

• /MiniRetreatOne

• /MiniRetreatTwo

• /MiniRetreatThree

• Mini Retreat: March 4, 2011 at UCSD

Timeline

Release Date: TBD

Implementation

• Cytoscape 3 Developer's Guide

TODO List

• ToDo

Testing Cytoscape 3.0

• Enhanced Test Plan