-
Notifications
You must be signed in to change notification settings - Fork 47
DOCS-3729: Add visualize tab #4378
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for viam-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM % comments
{{% alert title="Tip" color="tip" %}} | ||
To visualize a component without moving any real-world hardware, configure a `fake` model to represent your component (for example, a [`fake` arm](/operate/reference/components/arm/fake/)), then follow the steps below using the fake component. | ||
{{% /alert %}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think move this to the end of the page. I'd expect most people would want to use this with real things?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They might want to start with a visualization that is not tied to real-world movement, because if they're moving in the real world, they might as well not use the viz tab and instead just use the control tab and watch their arm move. They may well want to visualize without potentially breaking their surroundings.
Co-authored-by: Naomi Pentrel <5212232+npentrel@users.noreply.github.com>
No description provided.