Pricing

Yes.  Galyleo is released under a BSD 3-clause license.

The connection between the dashboard and the kernel is given by the Galyleo client, which is currently a Python module.  So if the kernel can use Python modules, it can be used today.  The Galyleo module is very simple, so we expect to implement it in other languages.  Of course, it is also open-source, and the protocol is documented; so others are free to implement this as well.

The only dependence Galyleo has on Python is the galyleo Python module.  This can be invoked from R runtimes with Reticulate and from Julia with PyCall.jl

Yes.  The dashboard’s disk and wire format is a JSON document, and the format is specified in the interchange format section.

The underlying technology is lively.next, an MIT-licensed environment for developing browser-hosted graphical, interactive applications.  You can find its repo here: Lively Next

We’ve developed, and are in beta, with  a web application which  takes the URL for a Galyleo Dashboard document as the  parameter dashboard and renders the document in the browser.  The page is at https://galyleobeta.engageLively.com/galyleo/index.html.  That page can be served from any convenient web server, on the web or on an intranet.    So publication is as easy as storing the dashboard file on any resource that has an URL (e.g., in a github repo, or for that matter Google Drive with the appropriate permissions).

Following that, on our roadmap is a feature which will drop a complete web page as a directory into your JupyterLab directory, and from there you can export it to any convenient web page.

We’ve tested it on Chrome, Firefox, Edge,  and Safari.  We believe that a keyboard and mouse or touchpad are required to get the best use out of Galyleo Studio, so we recommend the use of a computer or netbook to build dashboards.  Dashboards can be viewed on any modern browser on any device.

At the moment, Galyleo uses the Google Chart library.  We plan to extend this to a large number of charting and mapping libraries.  In principle, Galyleo can use any JavaScript/HTML5 based charting, mapping, or image library.  We will be updating Galyleo to include Chart.js, Leaflet.js (for maps, including building and campus maps), OpenLayers, and cytoscape.js (for networks and graphs).

At the moment, no, because Google Charts can’t be downloaded and served locally.  However, once we introduce other chart types, dashboards that don’t use Google Charts will be able to be run in disconnected operation.

To all intents and purposes, no.

Yes.  Just build a JSON structure corresponding to the dashboard you want to build.  In the future, the galyleo module will be extended to provide convenience API calls to do most of this.