| 7 | | == future issues == |
| 8 | | * Documenting our API with Sphinx |
| 9 | | * Handling "private" modules -> future exports |
| 10 | | * how chimera discovers tools on startup |
| 11 | | * debugging from source tree |
| 12 | | * build tools |
| | 5 | * ~~Greg will put notes on chimera2 wiki~~ |
| | 6 | * Greg will create git directories |
| | 7 | |
| | 8 | == Future issues == |
| | 9 | |
| | 10 | * Documenting our API with Sphinx |
| | 11 | * Handling "private" modules -> future exports |
| | 12 | * how chimera discovers tools on startup |
| | 13 | * debugging from source tree |
| | 14 | * build tools |
| 16 | | === chimera will be top-level namespace === |
| 17 | | |
| 18 | | from chimera.core import graphics |
| 19 | | from chimera import MAV |
| 20 | | from chimera import extralibrary |
| 21 | | |
| 22 | | === Tentative guidelines for core === |
| 23 | | |
| 24 | | * data structures that many tools need to agree on |
| 25 | | * facilities that many tools are likely to use |
| 26 | | * single version number |
| 27 | | * stable API |
| 28 | | * centrally and well documented |
| 29 | | |
| 30 | | === tentative guidelines for non-core === |
| 31 | | |
| 32 | | * if it has no API |
| 33 | | * updated frequently |
| | 18 | 1. chimera will be top-level namespace: |
| | 19 | {{{ |
| | 20 | from chimera.core import graphics |
| | 21 | from chimera import MAV |
| | 22 | from chimera import extralibrary |
| | 23 | }}} |
| | 24 | 1. Tentative guidelines for core: |
| | 25 | * data structures that many tools need to agree on |
| | 26 | * facilities that many tools are likely to use |
| | 27 | * single version number |
| | 28 | * stable API |
| | 29 | * centrally and well documented |
| | 30 | 1. Tentative guidelines for non-core: |
| | 31 | * if it has no API |
| | 32 | * updated frequently |