|
0
|
1 |
Cone development
|
|
|
2 |
================
|
|
|
3 |
This page should describe all relevant information on any developer who has or will create any functionality on
|
|
|
4 |
top of the ConE functionality.
|
|
|
5 |
|
|
|
6 |
|
|
|
7 |
ConE is open source
|
|
|
8 |
-------------------
|
|
|
9 |
|
|
|
10 |
ConE is a open source project (Currently under Eclipse Public License v1.0), which can take contributions from anyone interested in ConE. In future the ConE
|
|
|
11 |
will propably be split to two separate parts; core and plugins. The core of ConE is mainly the public interface
|
|
|
12 |
and the storage agnostic functionality of ConE. This core part is intended to be more generic and functional on
|
|
|
13 |
any platform. The plugin part is meant for extensions of ConE that could be for example platform specific
|
|
|
14 |
implementation plugins that generate output files based on the configurations.
|
|
|
15 |
|
|
|
16 |
|
|
|
17 |
Developing ConE plugin
|
|
|
18 |
----------------------
|
|
|
19 |
|
|
|
20 |
See :ref:`plugin-howto`.
|
|
|
21 |
|
|
|
22 |
|
|
|
23 |
Using ConE API
|
|
|
24 |
==============
|
|
|
25 |
|
|
|
26 |
.. toctree::
|
|
|
27 |
:maxdepth: 2
|
|
|
28 |
|
|
|
29 |
api/api
|
|
|
30 |
rule
|
|
|
31 |
|
|
|
32 |
|