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
Supervision tools #2350
Supervision tools #2350
Conversation
Maybe the conversion script should be applied to the control_panel example file (and remove the corresponding section in the file) |
execution fails if directory |
I propose I run the script myself with the latest control_panel_example.xml, commit all the tool files, then remove the tools from the control_panel_example.xml (I will leave a commented custom configuration example). And maybe the script should not be part of this pull request |
…xml and write custom configuration example.
47425c0
to
df302b2
Compare
…w one." This reverts commit 7cf89fb.
@dewagter @podhrmic What do you think about this evolution ? The improvements are:
|
anyone for a comment of this modification ? |
Looks good! |
Looks good to me:-) |
The improvements: - it is easier to add new tools that will be immediately visible for the users - you can hide tools that you don't use - you can set different default using the control_panel file - it is backward compatible so you you don't change your current control_panel you keep every like before
The purpose of this PR is to move the tools configuration (partially) out of the control_panel.xml.
The default tool configuration will be in individual files (one for each tool) in conf/tools/.
You can then override the default configuration in your control_panel.xml (eg. to change the default arguments or add custom tools). You can also add the
blacklisted="true"
attribute to the tools in your control_panel.xml to hide it in the paparazzi center.This way, you will be able to see the new tools without changing your control_panel.xml, and you can make a custom configuration without affecting the default one.