Jan Potoms

Let's close it, we've been using the current implementation long enough and I don't feel like there are issues with it.

The Toolpad team is exploring imperative APIs for interacting with dialogs. If this is something that interests you, I invite you to read and comment on the [RFC](https://github.com/mui/mui-toolpad/discussions/3379). _Toolpad Core...

> Should we just disable being able to create connections for now in the demo connections are a server side thing and will become when more so when we make...

> Another option would be to expose a React component that I can render inside the Zendesk extension (rather than an iframe), on which I can then apply CSS overrides...

I propose we improve the story for iframe embedding as part of MVP. - Removes both Toolpad chrome, and top-level Container from the page. - ways of disabling: - Query...

👍 "Toolpad shell" it is then. Right, data attributes won't work then. My only concern with using query parameters to pass toolpad options to the application is that they may...

I think we can close this, given that https://github.com/mui/mui-toolpad/issues/1001 has been closed

I opened a discussion which allows to collaborate on this under threads https://github.com/mui/mui-toolpad/discussions/1376

> May I ask how to open this scope explorer(dialog in the video)? go to [retool.com](https://retool.com/), and sign up for an account 😄

Closing this issue as we have replaced the runtime with `vite` and are now compiling only the libraries that are being used. See https://github.com/mui/mui-toolpad/pull/1881