Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enhance module xml descriptions, same for subsystems? #150

Closed
flixr opened this issue Mar 2, 2012 · 1 comment
Closed

enhance module xml descriptions, same for subsystems? #150

flixr opened this issue Mar 2, 2012 · 1 comment
Labels
Build system Enhancement Improve upon exiting functionality

Comments

@flixr
Copy link
Member

flixr commented Mar 2, 2012

Add a <doc> node with also <define> and <configure>, and the possible values for each to the module xml file.
Then you have the description, and can do a sanity check on the configuration options and easily list the available ones.

We should then probably also include the appropriate settings files, as per issue #23

The question then is if we really want to keep both, subsystems and modules... as it is only a semantic difference with modules representing optional part and subsystems mandatory parts. (ok, and they have different directories, etc.)
Basically if you write a module that doesn't use the module periodic and event functions, and instead it's functions get directly called from main, you have a subsystem...

@gautierhattenberger
Copy link
Member

Done with #182

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build system Enhancement Improve upon exiting functionality
Projects
None yet
Development

No branches or pull requests

2 participants