The following are the use cases for any visualization that we may develop, This issue focuses on the second item. Sofia can work on this but it needs to be considered with recent InfoMapper work.
Full JavaScript-based visualization. In this case the JavaScript files and surrounding HTML (index.html, etc.) are loaded onto a website with appropriate data files and the visualization is the primary interface, which is within a standard web page.
Embedded. For example, a third-party wants to embed the above visualization in their web page. We would advertise this by providing a code snippet that could be copied and pasted into someone's website, similar to how a Twitter tweet, or video is embedded. Tableau is a commercial visualization platform that allows embedding and might have some insight. See also Observable embedding, which is built on D3. It appears that Iframe approach is used.
Working Angular integration in the demonstration application. This is the place that pure JavaScript solution is developed into an integrated Angular version.
InfoMapper integration. This uses the results of the above to streamline integration into production applications.
If all of the above works, then we have flexibility in developing and deploying visualizations. The constraints will also likely cause the design of visualizations to become cleaner. A question is: Is it possible to deploy case 1 or 4 and allow third-parties to embed as in 2? Might we need to package the visualization differently than we are doing now to make it work? I hope to avoid redundant data and configuration files, but I can see how there may need to be pure JavaScript and Angular versions of visualization code to make this work. Or, we just have to deploy pure JavaScript version separately and have people embed that.
I will set up an Amazon S3 bucket so Sofia can deploy and do more testing in the cloud herself.
The following are the use cases for any visualization that we may develop, This issue focuses on the second item. Sofia can work on this but it needs to be considered with recent InfoMapper work.
index.html, etc.) are loaded onto a website with appropriate data files and the visualization is the primary interface, which is within a standard web page.If all of the above works, then we have flexibility in developing and deploying visualizations. The constraints will also likely cause the design of visualizations to become cleaner. A question is: Is it possible to deploy case 1 or 4 and allow third-parties to embed as in 2? Might we need to package the visualization differently than we are doing now to make it work? I hope to avoid redundant data and configuration files, but I can see how there may need to be pure JavaScript and Angular versions of visualization code to make this work. Or, we just have to deploy pure JavaScript version separately and have people embed that.
I will set up an Amazon S3 bucket so Sofia can deploy and do more testing in the cloud herself.