Mario,
a very technical question: Does the Chromium version used in IMatch apps already support ES6 modules and the corresponding import/export statements?
My first experiments were unsuccesful, but it is entirely possible that this was due to mistakes in my own coding.
This may depend on the Chromium version I currently ship with IMatch and probably some flags I need to set during compilation or initialization.
ES6 is from 2014 and I use ES6 constructs all the time. Modules are a different thing. What does MDN say about browser support for these?
Well, seems to be very recent.
Chrome: 61 onwards (I have 62)
Firefox: 54 onwards (but hidden behind a configuation option)
Edge: 15 onwards (but depicted as Experimental)
Maybe it is too early to use it all over. At the moment, I successfully use rollup.js for conversion to "standard" JS. Works, but using a transpiler for a small app is a bit of overkill and makes sharing Apps more difficult.
The current version of IMatch were still based on CEF/Chromium 59. The next release includes the latest 62 Version.
Since it is quite task to install, configure, built and include Chromium I'm not updating so often.
There is now a new endpoint named v1/imatch/info (and the IMatchInfo() function in the IMatch wrapper class) which not only returns version info about IMatch and ExifTool but also the Chromium and CEF releases IMatch has been built with.
Quote from: Mario on December 01, 2017, 07:56:05 PM
Since it is quite task to install, configure, built and include Chromium I'm not updating so often.
Understood.
Thanks for the info!
I'm still working on this. There are some changes which even may require me to implement and run a sub-process for CEF now...sigh,
Sorry to hear that. I hope it is worth the effort...