|
3
|
1 |
.. _plugin-api:
|
|
0
|
2 |
|
|
3
|
3 |
Extending ConE with plugin API
|
|
|
4 |
==============================
|
|
0
|
5 |
|
|
3
|
6 |
The Plugin api is intended for extending the ConE functionality with plugins.
|
|
|
7 |
Currently there are two ways to extend the functionality:
|
|
0
|
8 |
|
|
3
|
9 |
1. Adding support for new implementation languages
|
|
|
10 |
2. Extending ConfML or ImplML validation
|
|
0
|
11 |
|
|
3
|
12 |
Usually a plug-in that provides a new implementation language also provides
|
|
|
13 |
validation for it.
|
|
0
|
14 |
|
|
3
|
15 |
Developing a ConE plugin
|
|
|
16 |
------------------------
|
|
|
17 |
* See `Cone API epydoc <../epydoc/index.html>`_ for reference guide.
|
|
0
|
18 |
|
|
3
|
19 |
.. toctree::
|
|
|
20 |
:maxdepth: 3
|
|
0
|
21 |
|
|
3
|
22 |
../plugins/dev-plugin/plugin-interface
|
|
|
23 |
../plugins/dev-plugin/index
|
|
|
24 |
../plugins/dev-plugin/validation-plugin-index |