Online version

[Timothée Giet]

Le 26/03/2020 à 08:09, Aleś Bułojčyk a écrit :
> Hi Timothée.
>
> About "browser" version again. Did you
> see https://wiki.qt.io/Qt_for_WebAssembly ? Looks like WebAssembly is
> fully supported from qt 5.13, i.e. from 2019.

I checked again this link, and I confirm it would not work.

Just seeing in the "Platform Notes" part of that page. It explicitly
says it has limitations, the port is incomplete, some modules (that are
required for GCompris) are not supported... and the list goes on, but
those already make it a no-go.


> I'm not expert in qt, so, I can't say how much work requires to do it.
> But probably you can understand it much faster.
>
> BTW, does Android version requires some specific devices ? Google Play
> says "unsupported device" on
> the https://play.google.com/store/apps/details?id=net.gcompris.full for
> my Samsung A50.
>
The latest version (0.97) requires android api 22+ (so from android 5.1);

though their is still older packages for older android versions available...

Which android version is running on your Samsung A50 ?

Note that you can also try to install from F-Droid, maybe that will work
better from there for this phone.

Timo.


> WBR, Alex.
>
> On Wed, Mar 18, 2020 at 5:59 PM Timothée Giet <animtim at gmail.com
> <mailto:animtim at gmail.com>> wrote:
>
>     Le 18/03/2020 à 15:44, Aleś Bułojčyk a écrit :
>     > Hi All !
>     >
>     > New version of GCompris(with Qt Quick) looks great.
>     >
>     > Are you planning to create some kind of browser version ? Since
>     > activities implemented using JavaScript, and there are some QML
>     > declarations can be translated to HTML(like via QmlWeb), it can be
>     > possible.
>     >
>     > WBR, Alex.
>
>     Hi Alex,
>
>     Thanks for your comment.
>
>     We do not plan to create a "browser" version, it would be more
>     complicated than you think: we have some part of the core in C++,
>     and I
>     don't know how good QmlWeb would work with our extensive use of Qml.
>
>     I can read on https://community.kde.org/QmlWeb : "QmlWeb is not
>     intended
>     to run native QtQuick applications using QmlWeb without migration
>     effort" , so considering the huge size of our code base, it would
>     be too
>     much work to port, and more to maintain both versions with the ongoing
>     development.
>
>     Also, there was an attempt to port some activities to HTML+JS
>     before the
>     start of the new Qt-based version, but this experiment shown us that
>     porting to QtQuick was much more appropriate for performance and
>     convenience reasons.
>
>     Regards,
>
>     Timothée
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/gcompris-devel/attachments/20200326/eb8e8764/attachment.html>