Since 5.5 Qt has dropped QtWebKit and along with it, the QtWebkit bridge. Its' replacement - QWebChannel - is basically a mini-server which only the qt app can access. Sounds like it will be a) slower (as not directly exposing a qobject) and b) has less functionality.
This would mean that MapThing either languishes in a narrow subset of Qt, or we switch to a fully open source alternative - Electron.
The mapthing architecture would become somewhat simpler through electron as we dont need to worry (necessarily) about C++ or setup a 'dummy' C++ window. Electron will handle it.
Doing work in C++ may also be supported in a much simpler manner by using nbind
Plugins can be supported by this package or we could roll our own system.
Since 5.5 Qt has dropped QtWebKit and along with it, the QtWebkit bridge. Its' replacement - QWebChannel - is basically a mini-server which only the qt app can access. Sounds like it will be a) slower (as not directly exposing a qobject) and b) has less functionality.
This would mean that MapThing either languishes in a narrow subset of Qt, or we switch to a fully open source alternative - Electron. The mapthing architecture would become somewhat simpler through electron as we dont need to worry (necessarily) about C++ or setup a 'dummy' C++ window. Electron will handle it.
Doing work in C++ may also be supported in a much simpler manner by using nbind
Plugins can be supported by this package or we could roll our own system.
@yitang