hi @gc3, this is a great initiative!
To quickly answer your questions:
- header guards should not be needed
- you still have to put the patch declaration in a
.hpp file with the same name as your main patch class, in order to satisfy our build assumptions. These assumptions can be overridden if you use offline OwlProgram compilation, but not (currently) with our online compiler.
You can of course put the patch class declaration in a .hpp file, then put the implementation in a
.cpp file as is commonly done. Any
.cpp file that is part of the patch will be compiled as a separate compilation unit.
Documentation: we used to have a wiki on the old hoxtonowl.com website, but it wasn't well maintained. We could set up a new wiki, but personally I'm thinking that first fleshing things out on the forum, then publishing documentation pages on the main website, could be a better process. What do you think?