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")
My 2 c, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts
smime.p7s
Description: Firma crittografica S/MIME
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
