I can definintely understand if people don't want pixel depenencies in their QCoreApplication.
But I cringe a labeling it GUI. It's graphical but it's not necessarily User and definately not interface. I'd call it "graphics" or something. If you say GUI I'm thinking a display device and input device (mouse, keyboard, touch screen)
Sent: Monday, May 21, 2018 at 11:46 AM
From: "Konstantin Shegunov" <kshegu...@gmail.com>
To: "Christoph Feck" <cf...@kde.org>
Cc: "Interests Qt" <interest@qt-project.org>
Subject: Re: [Interest] QDatastream, QMap, QImage serialization
From: "Konstantin Shegunov" <kshegu...@gmail.com>
To: "Christoph Feck" <cf...@kde.org>
Cc: "Interests Qt" <interest@qt-project.org>
Subject: Re: [Interest] QDatastream, QMap, QImage serialization
On Mon, May 21, 2018 at 5:46 PM, Christoph Feck <cf...@kde.org> wrote:
Maybe for Qt6 we could have a thin QtGuiCore library, which manipulates image data and colors, but does not have a dependency on GUI servers (OpenGL, X11, etc.)
This makes most sense to me. I wouldn't really want the core, which is already pretty big, to get yet another big portion of code to accommodate the cases, that I feel, are not that common, albeit I would think they're really rare as well.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
