diff options
author | cbdev <cb@cbcdn.com> | 2021-07-01 22:56:44 +0200 |
---|---|---|
committer | cbdev <cb@cbcdn.com> | 2021-07-01 22:56:44 +0200 |
commit | dfa4f916b62cbd20054ef7a677359e60eade14d1 (patch) | |
tree | e2a02e43eabb6b53961a6214dc9ff0d82b852094 /README.md | |
parent | 3b134cc43965c1c196734be7a162da7cddeeafc8 (diff) | |
download | midimonster-dfa4f916b62cbd20054ef7a677359e60eade14d1.tar.gz midimonster-dfa4f916b62cbd20054ef7a677359e60eade14d1.tar.bz2 midimonster-dfa4f916b62cbd20054ef7a677359e60eade14d1.zip |
Route all core messages properly
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 14 |
1 files changed, 9 insertions, 5 deletions
@@ -300,12 +300,16 @@ for detailed information). ## Development -The architecture is split into the `midimonster` core, handling mapping -and resource management, and the backends, which are shared objects loaded -at start time, which provide a protocol mapping to instances / channels. +The architecture is split into the `core`, handling mapping and resource management, +the `frontends` which handle how the core is invoked and presented (ie. command line or graphical interface), +and the `backends`, which are shared objects loaded at start time providing a protocol mapping to instances / channels. -The API and structures are more-or-less documented in [midimonster.h](midimonster.h), -more detailed documentation may follow. +There is a general [developer information document](DEVELOPMENT.md) that outlines basic guidelines for +contribution. The [MIDIMonster knowledge base](https://kb.midimonster.net/) has a section on development, +containing additional helpful information and tutorials. + +The backend API, lifecycle and structures are documented in [midimonster.h](midimonster.h), the +frontend API and lifecycle in [core/core.h](core/core.h). To build with `clang` sanitizers and even more warnings enabled, run `make sanitize`. This is useful to check for common errors and oversights. |