-
Notifications
You must be signed in to change notification settings - Fork 44
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
Provide reusable QML components with common widgets #310
Comments
I am pretty sure that if a However, with QML modules, the name of the folder containing the With the right setup, this wold be possible from QML:
Basically, use |
@chapulina I just opened a draft pull request with changes like the ones I described in #310 (comment) If this looks like the right approach, more files can be added to the QML module and import statements can be updated where the module will be used. |
We got reusable vector, pose and color widgets. That's enough to close this ticket for now. As we develop more plugins, if we identify widgets that are being recreated multiple times, we should consider following the pattern of the new |
Widgets created with Ignition GUI often have duplicate code for interfaces to vectors, poses, colors, etc. It would be easier to construct various plugins if we offered these building blocks out of the box. It would also help users to write widgets that have the same look and feel.
Desired behavior
When I'm writing a plugin, I'd like to import Ignition GUI's resources and immediately include common components. For example:
Alternatives considered
Keep using custom components for each plugin.
Implementation suggestion
See the implementation for IgnSpinBox, which is currently used in multiple plugins.
Additional context
Igntiion Gazebo's ComponentInspector plugin already implements a lot of these. The work should consist in porting them to
ign-gui
and making them as general as possible.The text was updated successfully, but these errors were encountered: