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

Initial support for manually adding container and space view in the hierarchy #4616

Merged
merged 22 commits into from Jan 4, 2024

Conversation

abey79
Copy link
Contributor

@abey79 abey79 commented Dec 22, 2023

What

This is an initial take for the new so-called "additive workflow", which enables building a hierarchy of container and space views from scratch. It involves the following changes in UX:

  • The automatic simplification of the container tree is (mostly) disabled, as empty containers must be (temporarily) allowed while building a hierarchy.
  • Instead, a new "Simplify Container" button is available in the Selection Panel to simplify the subtree under the selected container.
  • A list if container children is displayed in the container Selection Panel, with a button to add more.
  • A new "Add Container or Space View" modal makes it possible to add a container and/or a space view of any type in the selected container.
    This feature is gated behind an experimental flag (Rerun Menu -> Options -> Enable the container addition workflow).
image

This PR also reorganises the experimental flags in the rerun menu such that they are visible in web and release builds. (superseded by #4661)

Fixes #4492
Fixes #4493

TODO (not necessarily in this PR)

Checklist

  • I have read and agree to Contributor Guide and the Code of Conduct
  • I've included a screenshot or gif (if applicable)
  • I have tested the web demo (if applicable):
  • The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

@abey79 abey79 added ui concerns graphical user interface 📺 re_viewer affects re_viewer itself include in changelog labels Dec 22, 2023
.map(|entry| {
SpaceViewBlueprint::new(
entry.class.identifier(),
&format!("empty {}", entry.class.display_name()),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Naming it "empty" immediately makes the name wrong as soon as you add content.

Maybe: "New {}"?

Better yet, we could make name optional -- if it's None then we could generate the name dynamically at runtime and otherwise we could use whatever the user has provided.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This default naming is becoming annoying :) #4669

Copy link
Member

@jleibs jleibs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I pushed a small mutabillity fix -- otherwise looks great.

Copy link
Member

@jleibs jleibs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I pushed a small mutabillity fix -- otherwise looks great.

# Conflicts:
#	crates/re_viewer/src/ui/rerun_menu.rs
#	crates/re_viewer_context/src/app_options.rs
#	crates/re_viewport/src/viewport.rs
#	crates/re_viewport/src/viewport_blueprint.rs
@abey79 abey79 merged commit 7342ff8 into main Jan 4, 2024
41 of 42 checks passed
@abey79 abey79 deleted the antoine/additive-workflow branch January 4, 2024 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
include in changelog 📺 re_viewer affects re_viewer itself ui concerns graphical user interface
Projects
None yet
2 participants