You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Iframe embedding of Appbox Frames has highly extensibility. though the pure reason for us to implement frames on appbox is to prevent code duplication, which is still current on console.bridged.xyz. this is due to frame only supports frame url via src query as a built-url for loading actual code source, which console is more of a content first service than url.
Console internally creates an url to provide js url, but that is local Blob url, so which cannot be used with Frame's src query. (Haven't tested, pretty sure won't work this way)
So.. we'll need to port Frame as React component supporting both iframe url embedding and, React component usage in other fully-standalone-operating applications (a.k.a console)
The text was updated successfully, but these errors were encountered:
Iframe embedding of Appbox Frames has highly extensibility. though the pure reason for us to implement frames on appbox is to prevent code duplication, which is still current on console.bridged.xyz. this is due to frame only supports frame url via src query as a built-url for loading actual code source, which console is more of a content first service than url.
Console internally creates an url to provide js url, but that is local Blob url, so which cannot be used with Frame's src query. (Haven't tested, pretty sure won't work this way)
So.. we'll need to port Frame as React component supporting both iframe url embedding and, React component usage in other fully-standalone-operating applications (a.k.a console)
The text was updated successfully, but these errors were encountered: