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

Create initial empty vslam-sandbox GUI #18

Open
vadixidav opened this issue Aug 30, 2020 · 4 comments
Open

Create initial empty vslam-sandbox GUI #18

vadixidav opened this issue Aug 30, 2020 · 4 comments

Comments

@vadixidav
Copy link
Member

vadixidav commented Aug 30, 2020

This task is to get vslam-sandbox running with a simple GUI. The command line arguments should be used exactly the same way they are today, but the GUI should contain info logs as if one used RUST_LOG=info at the command line. The GUI and application exit after all the processes that are currently done are done. GUI should be made with iced for wgpu compatibility.

@codec-abc
Copy link
Contributor

A quick question here, the GUI and the command line arguments should become a single executable of do you want to keep them separate? if yes, how the program should know if the program should run in command line or open a window?

@vadixidav
Copy link
Member Author

@codec-abc vslam-sandbox will become the GUI. You can pass command line arguments to a GUI. When it runs, it will always open a GUI. It will just perform the same things it does today, but with the logs displayed in the GUI.

@codec-abc
Copy link
Contributor

Ok I understand more what you have in mind. My question was more about headless servers. Because today, it should work almost anywhere but if we required a GUI (especially since a one that draw 3D with webgpu) it might not work everywhere or could crash because of some faulty drivers or something else.

@vadixidav
Copy link
Member Author

We can create a series of separate command line utilities later. vslam-sandbox should become a GUI only. At some point we can take the various functions it performs and turn them into separate utilities. What it was doing before was running everything all-in-one, but we will want to split everything out a bit more so a user can run small steps at the command line. Alternatively, we might create some kind of command line thing that takes in a list of operations to perform in a batch to avoid saving/reloading. However, vslam-sandbox will remain just a GUI, and we can make all of that later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants