Check if it's better to make the app a container for iframe/webview.
ErniW opened this issue · comments
Maybe if Involt as Chrome App become the container for website within sandbox which transfers the data. It would work as fine as before plus it will reduce many limitations of Chrome App.
The data will be transferred with post message function: https://developer.chrome.com/apps/app_external
This could be useful when web support will be included so if user decides to open the app with the viewer, the app will work with serial/bluetooth instead of online communications.
The viewer could be available through Chrome app store so it will be like browser for local websites with involt interactions.
In this case working without loader will not only force autoconnection to default port but also could bind index.html file to the viewer.
It would be cool to have the Involt divided into 3 elements (in future)
- Involt - html framework based on online communication (not Chrome App or with the same api functions but not prepared as Chrome app - see next).
- Involt preview - standalone app for using serial and bluetooth communication with html prototype in Chrome App.
- Involt build (or any other name, maybe not Involt but something different) - app for adding interactions without coding
... and bonus: Involt paper for simple mockups
The involt object in javascript must be split to make the preview app handle the connection and the framework should be inside iframe.
However, maybe all involt functions should be included if user decided to work directly in preview window not using the iframe...
This issue is outdated but still I have to manage pagination within iframe, post message has some security issues because locally it has to use '*' permission - it's possible to use window parent to access variables of same source.