gazebosim/gz-gui

GridConfig UX improvements

Open

#356 opened on Feb 3, 2022

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)C++ (68 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (103 stars)
PR merge metrics
 (PR metrics pending)

Description

Desired behavior

Current GridConfig UI below.

Proposed enhancements:

  • "Horizontal" should precede "Vertical" field, for better intuition
  • "Position" field should be more clear which part of the grid it refers to, the center, a corner and which corner, etc.
  • Consider making the "Color" group a linear layout as opposed to 2 x 2. Opposing argument: 2 x 2 saves space over vertical. They might fit horizontally.

Other enhancements:

  • There has been community suggestion that we offer an interface in degrees for angles. Has not been discussed internally. If we make standard widgets to be reused across plugins, that might be something to add.
  • If we do that, then similar could be said of colors in range 0-255, since color pickers online and in drawing tools usually give colors in that range.

Screenshot from 2022-02-03 01-05-35

Implementation suggestion

GridConfig plugin is located at https://github.com/ignitionrobotics/ign-gui/tree/ign-gui6/src/plugins/grid_config

Additional context

Original discussion here https://github.com/osrf/lrauv/pull/125

Contributor guide

Research direction
Start by examining the GridConfig plugin code located at src/plugins/grid config in the ign gui repository. Understand the current UI layout defined in the QML or widget files. Then implement the proposed changes in order: reorder fields (Horizontal before Vertical), improve the 'Position' field clarity with tooltips or labels, and adjust the 'Color' group layout to be linear. Consider reusing or creating standard widgets for angle and color inputs as a separate task. Test the changes by running the application and verifying the UI behaves as expected.
Tech stack
cpp
Domain
desktop
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Qt
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70