> -----Original Message----- > From: Giuseppe D'Angelo <giuseppe.dang...@kdab.com> > Sent: Monday, 1 July 2019 16:10 > To: Konstantin Tokarev <annu...@yandex.ru>; Ville Voutilainen > <ville.voutilai...@gmail.com> > Cc: Cristian Adam <cristian.a...@qt.io>; development@qt-project.org > Subject: Re: [Development] HTML5/CSS vs Qt QML and QtCreator / Assistant > > Il 01/07/19 15:56, Konstantin Tokarev ha scritto: > > If we include assumption #4, we can just render document paragraph-by- > paragraph, encode > > resulting images of paragraphs to PNG and send to UI process. > > All of this "cross platform" (possibly), "efficient" (on the spot PNG > compression through local sockets is everything but efficient), > "flicker-free" (I'll believe it when I see it). > > So, where's this magic code? > > > (And all of this instead of adding 1px table borders and maybe other 2-3 > features to QTextDocument; and developing a layout engine in Qt Quick. > Not to mention it makes for a great user story for Qt, "Yes, the QtHelp > module requires Qt Quick. No don't worry, it doesn't use OpenGL, it uses > the software rasterizer, but no, not directly! It spawns another process > and pushes frames through a local socket") > >
I was thinking at the full LLVM OpenGL Software Renderer. But what about Qt Quick 2D Renderer? Could that simply work only in the help plugin, without necessarily needing an external process? Cheers, Cristian. _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
