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

Some fixes #11

Merged
merged 22 commits into from
May 19, 2023
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Tabify all panels (except for blueprint) (#7)
* initial styling impl

* make buttons that should be small, small

* Runtime depth config and fix device selection ui

* comment

* Proper runtime depth config updates

* switch to Yolo v8

* add comma to label for non open zoo models

* split 2d + 3d cam view vertically instead of horizontally

* Make the UI more configurable by converting the right panel into tabs. TODO: UX while laying out the panels. When a new space view appears only update the viewport layout, try to keep the user configured fixed function panels as they were. Just handle it in a way that is intuitive

* remove bottom panel, switch to RAW imu sensors

* XLink statistics initial implementation

* initial xlink throughput statistics impllementation, have to glow it up  a bit and maybe clean up the code

* Xlink and rerun rename (#9)

* Rename rerun py library to depthai_viewer

* bug fixes and started working on a smart auto layout that operates on an existing tree, to preserve ui as much as possible, while also creating good layouts

* auto layout

* Fix maximize not working and add maximize for Stats tab

* delete profiling stuff that shouldn't have been commited

* mostly fix smart layout, TODO: detect when you can group mono and color 3d + 2d views into a 4 way split

* add docstring for  update_tree

* WIP auto layout can_create_mono_quad checker, not at all finished yet
  • Loading branch information
zrezke authored May 18, 2023
commit fb52075b3413dd3a86a026ed60e8728694904582
4 changes: 2 additions & 2 deletions ARCHITECTURE.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,10 +22,10 @@ The logging data can be written to disk as `.rrd` files, or transmitted over TCP
The Rerun Viewer is where log data is visualized. It is usually run as a native app, but can also be compiled to WebAssembly (Wasm) and run in a browser.

#### Native viewer
The easiest way to launch the viewer is directly from the logging API with `rr.init("my_app", spawn=True)`. However, the standalone viewer can also be run from the command line, for example to view an `.rrd` file: `rerun mydata.rrd`.
The easiest way to launch the viewer is directly from the logging API with `viewer.init("my_app", spawn=True)`. However, the standalone viewer can also be run from the command line, for example to view an `.rrd` file: `rerun mydata.rrd`.

#### Web viewer
You can try running the viewer in a browser using `rr.serve()` in python, or using `rerun --web-viewer mydata.rrd`.
You can try running the viewer in a browser using `viewer.serve()` in python, or using `rerun --web-viewer mydata.rrd`.

The web viewer consists of just a few small files - a thin `.html`, a `.wasm` blob, and an auto-generated `.js` bridge for the wasm. These files are served using the [`re_web_viewer_server`](https://github.com/rerun-io/rerun/tree/latest/crates/re_web_viewer_server) crate.

Expand Down
Loading