Embeddable grid in iframes

[mofojed]

• Pull in @deephaven/embed-grid for iframes
• Navigate to http://localhost:10000/iframe/table?name= to load a table with the name tableName
• Embed in another page using an iframe, e.g. http://localhost:10000/iframe/table?name=basic
• Add permissions canCopy, canDownloadCsv to enable specific functionality
• Use JS to send filter/sort commands:

Filtering

Command: filter
Value: { name: string; value: string }[] - Provide an array of column name and quick filter values to set.
Example: document.getElementById('my-iframe').contentWindow.postMessage({ command: 'filter', value: [{ name: 'A', value: '>50' }, { name: 'B', value: '<4' } ] }, 'http://localhost:4010')

Sorting

Command: 'sort'
Value: { name: string, direction?: 'ASC' | 'DESC' }[] - Provide an array of column names to sort on, and optionally the sort direction (defaults to 'ASC');
Example: document.getElementById('my-iframe').contentWindow.postMessage({ command: 'sort', value: [{ name: 'A' }, { name: 'B', direction: 'DESC' } ] }, 'http://localhost:4010')

[devinrsmith]

Very cool. I think we might want a way to encode a generic ticket (so, we can fetch application mode tickets, etc); probably something like ?ticket=<hex-or-base64url-encoded>?

This does get into the realm of URIs that I'm hoping we can support more thoroughly server-side (resolve("<uri>")); in which case, maybe we want to support encoded URIs instead of tickets directly: ?uri=...

[devinrsmith]

Does it make sense to break out the static media as it's own package that can be further depended on? Looks like we are duplicating about 15M of content:

15M     /usr/share/nginx/html/iframe/table/static/media
15M     /usr/share/nginx/html/ide/static/media

[devinrsmith]

Alternatively, should we have a single entrypoint into our npm pack that specifies code-studio and embed-grid?

[mofojed]

The hex ticket can be a follow up ticket.
The static media between the two packages is not all the same, though the fonts are duplicated. It's possible we could do code-splitting on routes and that would help with that some, but that would require some changes on the web-client-ui side. Could be a separate ticket?

I'll make one entrypoint to our npm pack and re-post.

[devinrsmith]

Just verifying - we expect code-studio and embed-grid to always be in-sync with their versions?

[mofojed]

Yes, they should.