Ralf Waspe

I am currently trying to make the hello-world example less c# in appearence.

By that I mean a separation of header and source.

However, this is somehow ugly, as nearly all class members (inlets, outlets, attribute, arguments ….) have a list of strings as arguments for the help, which can not be set post construction.

Furthermore, the constructors of classes such as a message do not accept a pointer to a member function of the class containing the message. Instead I must put a long std::bind to a member function into the constructor as well. (as a workaround I have written some templates for that)

What are the reason behind these design choices and would fixes to these issues to the min-devkit be welcome?

I am currently trying to make the hello-world example less c# in appearence.
By that I mean a separation of header and source.

I am currently trying to make the hello-world example less c# in appearence.
By that I mean a separation of header and source.
However, ... 

min-devkit api / message callback functions