-
Notifications
You must be signed in to change notification settings - Fork 276
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
Move some plugins to ign-gui #835
Comments
I'm in favor of moving whatever possible into ign-gui. 👍 |
what's the process of doing that ? should I need to deprecate something ? or is it just remove from ign-gazebo and move the plugin to ign-gui ? |
My opinion would be that we can move them in the next major release of both |
I support moving plugins to ign-gui when possible
these ones look straightforward to me
these ones depend on ignition transport services
I think the camera_video_recorder system and the |
I know there are different names used for |
Yes! These plugins should have never been added to
Correct, we'd need to use different names if we want them to coexist. But @mjcarroll 's idea is interesting:
Technically, Ignition GUI would just pick up the different library, so I think it could work. If we take this route, we should make sure we don't change any of the plugin arguments so users can transition seamlessly. |
Fortress collection file is pointing to
|
PRs
|
All plugins that could be trivially moved have been |
I was checking some of the plugins that are currently in ign-gazebo but they don't have any gazebo dependency. I think we should move these plugins to ign-gui.
For example:
@scpeters @iche033 @mjcarroll thoughts?
The text was updated successfully, but these errors were encountered: