-
Notifications
You must be signed in to change notification settings - Fork 1
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
Replace Camera with Scenery Display to support Virtual programs #221
Comments
If we're replacing the current camera interface with a scenery display, we need to consider how we switch between the camera and virtual display, and how we ensure current features related to the preview programs and to camera calibration are retained/integrated. The biggest question I have is: Which features are best to integrate into a scenery display for reduced complexity and maintenance? Which are best left in the React framework? Preview Program Features in Sidebar
Camera Detection Features in Sidebar
Space Management Features
Misc Features
Simplest Change to CameraThe simplest change would involve leaving as much of the React interface intact and replacing only the camera feed/area around the camera feed with a scenery display. Adding/removing Programs, markers, etc would exist as they are in the sidebar. I'm not sure how much complexity this adds in connecting the react components to the scenery display.
More complex and integrated displayWe could also try embedding more of the sidebar into the display. There's been interest in a "drag-n-drop" interface for papers, so this could be placed in the display itself. Then Preview Markers and whisker enabling could also appear there. |
We will be prioritizing enhancing the virtual experience. One solution we discussed in design meeting was to revamp the Camera screen itself to allow users to swap between the physical+virtual+camera or the virtual-only experience.
Ideas and mockups to go into this issue.
@brettfiedler to detail out needs for two-state screen and provide mockups
The text was updated successfully, but these errors were encountered: