From dfa4f916b62cbd20054ef7a677359e60eade14d1 Mon Sep 17 00:00:00 2001 From: cbdev Date: Thu, 1 Jul 2021 22:56:44 +0200 Subject: Route all core messages properly --- README.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index f2c9518..638624e 100644 --- a/README.md +++ b/README.md @@ -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. -- cgit v1.2.3