Cytoscape Wiki|
← Revision 33 as of 2012-05-10 21:40:57
Size: 2363
Comment: under construction...
|
← Revision 34 as of 2012-05-10 21:48:19 →
Size: 2685
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
|
Cytoscape 3.0 strives for a modular architecture where the application consists of a set of jar files where each jar contributes a well defined subset of functionality to the application. The design is oriented around the OSGi service model (i.e. micro service) with API and implementation separated into different jar files. We’ve introduced the use of OSGi as a way to create and enforce a modular, sustainable code base. We’ve introduced Maven as a build system to help manage the many jar files created. |
|
| Line 10: | Line 12: |
|
* We’ve introduced a few new technologies to 3.0 to help solve many of our existing problems. OSGi is a java based module system. We’ve introduced the use of OSGi as a way to create and enforce a modular code base. We’ve introduced Maven as a build system to help manage the many jar files created. |
* [[../CoreDevelopment/Architecture#OSGi_Basics|OSGi]] * [[../CoreDevelopment/Architecture#Maven_Basics|Maven]] |
Cytoscape 3.0 App Development
Introduction
Cytoscape 3.0 has a greatly simplified API that is clearly defined. API jars are strictly separate from the implementation jars. We believe that we’ve learned our lessons with 2.x and have greatly improved the usability of the API to benefit our active developer community. The API is versioned using the Semantic Versioning standard. This means that an app designed to work with an early version of 3.x will be guaranteed to work through at least version 4.0 of Cytoscape. Our commitment to supporting app developers is stated in an explicit backwards compatibility contract found in each class in the public API so that both core developers and app writers will understand how a class might change.
Architecture and Technologies
Cytoscape 3.0 strives for a modular architecture where the application consists of a set of jar files where each jar contributes a well defined subset of functionality to the application. The design is oriented around the OSGi service model (i.e. micro service) with API and implementation separated into different jar files. We’ve introduced the use of OSGi as a way to create and enforce a modular, sustainable code base. We’ve introduced Maven as a build system to help manage the many jar files created.
API and Javadocs
Porting a 2.x Plugin to a 3.0 App
Tutorials
TEMP