The Sights Interface Design Wizard 2.0 about sights HOT 3 OPEN

Perhaps my greatest contribution to humanity is the possible renaming of "The Sights Interface Design Wizard 2.0" to "Worksight".

from sights.

Had a great meeting today and we have some ideas that we need to get down.

Complete configuration for a robot should be stored in separate files: Hardware configuration and layout configuration.
This allows multiple layouts to be defined for the same hardware, without reconfiguring the hardware - which in turn allows for great pagination (#45).

How do we make it clear to the user (regardless of backend implementation) when they are editing a layout (multiple layouts can be valid for the same hardware) or hardware?

Solution: Separate it with two "pages" in the Sights Interface Design Wizard 2.0.

The first: Hardware.
This is where hardware (sensors, motors) is configured.
We haven't thought much about the interface of this page. We need a list of all hardware (populated by the installed hardware plugins), and a list of configured hardware. A user can create a configured piece of hardware (as many as they want) from an unconfigured piece provided by the plugins (for example, the user can create 4 motors using the same motor plugin). We should probably have the ability to create motor groups here in the hardware section. We need to show a list of all the already configured hardware, so that users can edit their configurations.

The second: Layouts.
This is the one we know a bit more about - it's basically what we've already discussed above (two sidebars; the left is a list of all possible graphs (populated by all graph plugins (including standalone graph plugins and graphs bundled with sensor plugins)) and the right is a list of all hardware (sensors, motors, etc), with the area in the middle between the sidebars used to build the interface layout and add hardware to graphs) - except that the right (hardware) sidebar no longer contains a list of all possible hardware based on the installed plugins (sensor and motor plugins). Instead, this right sidebar now contains a list of all hardware that has been configured.

Crossover
The astute among you may have noticed that "configured hardware" exists as both an output of the Hardware page, and an input on the Layouts page. Should the user be able to edit already configured hardware in both pages, or just in the Hardware page?

How do we display two "pages"? This discussion needs another issue. Sights will display some content on the main page (graphs, cameras), some in modals on top of that (SSH) and some in new pages (Sights Interface Design Wizard 2.0 is itself a new page, and then there are two sub-pages (hardware, layout) within that)

from sights.

Possible third page: Controls
This is where motor "control groups" could be defined (replacing motor groups in the hardware page entirely). Keyboard/controller controls can be assigned to various robot actions on this page.

from sights.