-
Notifications
You must be signed in to change notification settings - Fork 0
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Frameless embedding with URL parameter #193
Comments
What about just making a "frameless" mode, so the user would create a layout that has a single panel and enable frameless mode to achieve the same thing? Extracting and rendering one panel from a layout seems a bit complicated. |
@jtbandes you're right, I was overthinking it. |
maybe avoid a double negative? e.g. |
I think frameless is fine, it's kind of a common term, whereas "framed" or "frameful" is not. |
Something to consider - we might want to do this on a different domain than studio.foxglove.dev. Typically it is bad form from a security perspective to allow your site with a user's credentials to be embedded in another site. In fact we plan to dis-allow embedding studio.foxglove.dev for this reason. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Use case: I would like to embed Studio in a blog post on https://foxglove.dev/blog to interactively visualize something I am talking about, such as markers in a 3D panel. To accomplish this, I am thinking about an iframe pointed to a URL of the form:
https://studio.foxglove.dev/?layout_url=...&data_source=...&panel_id=...~~Where
panel_id
uniquely references one of the panels that appears in the layout loaded fromlayout_url
(a remote JSON file). ~~EDIT:
https://studio.foxglove.dev/?layout_url=...&data_source=...&frameless=true
I would expect this to strip away most of the UI in Studio: the sidebar, and widgets for adding/removing panels or modifying the current panels.
The text was updated successfully, but these errors were encountered: