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

Move some plugins to ign-gui #835

Closed
ahcorde opened this issue May 26, 2021 · 9 comments
Closed

Move some plugins to ign-gui #835

ahcorde opened this issue May 26, 2021 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@ahcorde
Copy link
Contributor

ahcorde commented May 26, 2021

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?

@ahcorde ahcorde added the bug Something isn't working label May 26, 2021
@ahcorde ahcorde self-assigned this May 26, 2021
@mjcarroll
Copy link
Contributor

I'm in favor of moving whatever possible into ign-gui. 👍

@ahcorde
Copy link
Contributor Author

ahcorde commented May 27, 2021

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 ?

@mjcarroll
Copy link
Contributor

My opinion would be that we can move them in the next major release of both gui and gazebo without deprecation. Anybody depending on ign-gazebo would already be depending on ign-gui.

@scpeters
Copy link
Member

I support moving plugins to ign-gui when possible

these ones look straightforward to me

  • video_recorder
  • view_angle

these ones depend on ignition transport services /gui/view_angle and /gui/record_video:

I think the camera_video_recorder system and the view_angle service would have to be migrated to ignition::gui::Scene3D

@scpeters
Copy link
Member

I know there are different names used for Scene3D in ign-gui and GzScene3D in ign-gazebo since the config files just look for shared libraries. So I expect we might need to use different names for the ign-gui version?

@chapulina
Copy link
Contributor

Yes! These plugins should have never been added to ign-gazebo to begin with, we did that for expediency at first, but new plugins such as Screenshot have been added directly to ign-gui.

So I expect we might need to use different names for the ign-gui version?

Correct, we'd need to use different names if we want them to coexist. But @mjcarroll 's idea is interesting:

we can move them in the next major release of both gui and gazebo without deprecation.

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.

@ahcorde
Copy link
Contributor Author

ahcorde commented Jun 16, 2021

Fortress collection file is pointing to main in ign-gui and ign-gazebo. I start moving these two plugins from ign-gazebo to ign-gui:

  • grid_config
  • tape_measure

@ahcorde
Copy link
Contributor Author

ahcorde commented Jun 21, 2021

@chapulina
Copy link
Contributor

All plugins that could be trivially moved have been

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants