[Development] HTML5/CSS vs Qt QML and QtCreator / Assistant
cristian.adam at qt.io
Fri Jun 28 12:05:06 CEST 2019
> -----Original Message-----
> From: Samuel Gaist <samuel.gaist at idiap.ch>
> Sent: Friday, 28 June 2019 11:56
> To: Cristian Adam <cristian.adam at qt.io>
> Cc: development at qt-project.org
> Subject: Re: [Development] HTML5/CSS vs Qt QML and QtCreator / Assistant
> > On 28 Jun 2019, at 11:32, Cristian Adam <cristian.adam at qt.io> wrote:
> > Hi,
> > Some of you might have been familiar with white papers such as Qt QML v
> HTML5 – a practical comparison.
> > Qt Creator already ships with QML support, why not transform the HTML
> offline documentation into QML?
> > Does it have to be HTML5/CSS?
> > Having the documentation as QML will have no additional constrains for Qt
> Creator. No 76MiB Qt5WebEngineCore.dll file, no memory increase, no startup
> > QML is supported on all platforms, right? Builds with MinGW on Windows, and
> so on.
> > Cheers,
> > Cristian.
> > _______________________________________________
> > Development mailing list
> > Development at qt-project.org
> > https://lists.qt-project.org/listinfo/development
> While I find the idea interesting in itself, as silly as it may sound, it has one main
> constraint: OpenGL.
> On my old Mac, using QtQuick triggers the high end graphic card which drains
> the battery and make my machine heat go up.
> I (and I know am not the only one) usually start Qt Creator with all QtQuick
> related plugins disabled to avoid that when possible.
> So this use case would make the documentation not accessible for these people.
> Best regards
Qt Creator bundles on Windows an OpenGL Software Renderer (opengl32sw.dll 16,7MiB).
We could bundle the Software OpenGL Renderer on all platforms, and use it for documentation,
so that you won't have this problem.
The size of the Software OpenGL Renderer can be reduced if we would share the LLVM code
that we use for clang tooling.
More information about the Development