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.

Sign up for GitHub

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

Jump to bottom

Split out the visualizers to a separate application #203

Open

Jasper-Bekkers opened this issue Feb 5, 2024 · 0 comments

Labels

roadmap

Member

Jasper-Bekkers commented Feb 5, 2024 •

edited

Loading

This will be a bit of a longer road map item, but to keep this crate lean I'd like to turn all our gui crates off by default.

Ideally we we structure this project like puffin. Meaning we split this project up into several creates an a loose application.

The core allocator
The egui based visualizer, ready to embed directly into apps
A standalone application that uses the equi library.

For this to work well need to refactor a few things, as well as add an (optional) networking layer to have the allocator connect to the viewer.

I think longer term this can set us up in a way where we could use the same visualizer and tools for CPU memory as well.

Jasper-Bekkers added the roadmap label

Jasper-Bekkers mentioned this issue

Add a public API to expose allocation reports #226

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment