Please have a look at this link from Oracle which talks about how we can add HTML Content to JavaFX Applications. As we are already using JavaFX in our IGB code, we can build a plugin which will only wrap the BioViz-CyVerse web app inside IGB.

https://docs.oracle.com/javafx/2/webview/jfxpub-webview.htm

https://dzone.com/articles/htmlcssjavascript-gui-java-0

This sounds like a great idea, as it would allow users to access their CyVerse data from a browser or from within IGB, and we would only have to maintain a single site. Once the cyverse.bioviz.org site is near enough to completion, we should examine this idea further and attempt to implement it.

This module can possibly be implemented in JavaFX WebView and WebEngine. However, in the preliminary testing with WebView, BootStrap 4 (embedded to the website) is not being rendered. May need to investigate the possibilities to implement that. One of the possibilities may include downloading the bootstrap 4 library to the Bioviz Connect project. The image shows basic WebView connecting to connect.bioviz.org

Regarding bootstrap 4 rendering:

• I think it would be worthwhile looking into that a bit more. Could you investigate a bit further on that?

Upon further investigation, in JavaFX WebView application, I was not able to render Bootstrap 4 from a CDN into the application but upon downloading the bootstrap to the BioViz Connect project the css is rendered correctly. However, we also rely on FontAwesome library for our icon needs which is accessed from a CDN as well. Downloading FontAwesome libraries entirely will not be necessary for our purposes. In IGB, App Manager GUI is rendered by injecting css from a downloaded bootstrap library as well in the App Manager plugin.
The best possible option is JxBrowser library for IGB as mentioned in Shristi Tiwari's comment above. It renders CDN served libraries. The JxBrowser library is however licensed and only has a 30-day trail period before payment starts.

Please refer to Images above.

https://www.teamdev.com/jxbrowser

I checked the licenses. If we purchase a license, it is a "perpetual license" which means we get to use the code forever. If we want updates, we pay again, I guess. If we do this, probably the "project" license is the right option for us, since it is meant for a team working on a single product - IGB, in this case.

However, I think we are going to need more than 30 days to evaluate whether this is right for our use cases.

I have a couple questions:

• Is there API documentation we can look at?
• How would the "view in IGB" aspect work?

cc: Nowlan Freese and Karthik Raveendran