Re: [Interest] QDatastream, QMap, QImage serialization

On Tue, May 22, 2018 at 4:22 PM, Thiago Macieira wrote: > On Tuesday, 22 May 2018 05:07:05 -03 Konstantin Shegunov wrote: > > Wouldn't it be the same from the point of view of a GUI application, when > > the platform plugins are already loaded? > > And fail for console

Re: [Interest] QDatastream, QMap, QImage serialization

On Tuesday, 22 May 2018 14:35:28 -03 Jason H wrote: > Like screens, input methods, windows, sessions, clipboards, font, palettes, > etc. Maybe these things are lighter weight than I think they are > (particularly for the "offscreen" plugin ) You may be right that this is unneeded weight for the

Re: [Interest] QDatastream, QMap, QImage serialization

On Tuesday, 22 May 2018 14:45:53 -03 Jason H wrote: > But for people in my position, knowing that QGuiApplication with offscreen > platform the raster implementation we are looking for, is not immediately > obvious. It took you saying that for me to know that. I don't see how it > can be gleamed

Re: [Interest] QDatastream, QMap, QImage serialization

> On Tuesday, 22 May 2018 12:24:56 -03 Michael Jackson wrote: > > For Qt6 what I would like to see is QPainter abstracted out to just an > > interface and have the normal accelerated implementation that we have now > > in QtGui but also have a non-accelerated version living in QtCore or a > >

Re: [Interest] QDatastream, QMap, QImage serialization

On Tuesday, 22 May 2018 11:15:49 -03 Jason H wrote: > > > How about texture() and texturePixmap()? > > > > That is source-incompatible. > > But the source is "wrong'. ;-) Everything we are talking about is 6.0 stuff. > In the past code conversion tools have been provided. We can do

Re: [Interest] QDatastream, QMap, QImage serialization

On Tuesday, 22 May 2018 12:24:56 -03 Michael Jackson wrote: > For Qt6 what I would like to see is QPainter abstracted out to just an > interface and have the normal accelerated implementation that we have now > in QtGui but also have a non-accelerated version living in QtCore or a > library that

Re: [Interest] QDatastream, QMap, QImage serialization

> On Tue, May 22, 2018 at 3:15 PM, Jason H wrote: > > (...) > > Admittedly I don't understand the nuances of QPixmap. But I know working > > with a QImage should not require a windowing server. > > Where did you see QImage needs a windowing server ? > Which QPA plugin are you

Re: [Interest] QDatastream, QMap, QImage serialization

On Tue, May 22, 2018 at 3:15 PM, Jason H wrote: > (...) > Admittedly I don't understand the nuances of QPixmap. But I know working with > a QImage should not require a windowing server. Where did you see QImage needs a windowing server ? Which QPA plugin are you using for

Re: [Interest] QDatastream, QMap, QImage serialization

-Original Message- From: Interest on behalf of Jason H Date: Tuesday, May 22, 2018 at 10:16 AM To: Thiago Macieira Cc: Subject: Re: [Interest]

Re: [Interest] QDatastream, QMap, QImage serialization

> Sent: Tuesday, May 22, 2018 at 10:04 AM > From: "Thiago Macieira" > To: interest@qt-project.org > Subject: Re: [Interest] QDatastream, QMap, QImage serialization > > On Tuesday, 22 May 2018 10:38:46 -03 Jason H wrote: > > > How about just using different function

Re: [Interest] QDatastream, QMap, QImage serialization

On Tuesday, 22 May 2018 10:57:08 -03 Jason H wrote: > > > QStandardItem* > > > > It's GUI stuff, what's wrong with that? > > They are not. There's a good reason to use Qt Model View in a headless > server. There's need to render images and deliver to clients as byte > streams. Qt is extremely

Re: [Interest] QDatastream, QMap, QImage serialization

On Tuesday, 22 May 2018 10:38:46 -03 Jason H wrote: > > How about just using different function names instead? Like, you know, > > "texture" and "textureImage"? > > How about texture() and texturePixmap()? That is source-incompatible. > There is a difference. As you already stated, a QPixmap

Re: [Interest] QDatastream, QMap, QImage serialization

> Sent: Tuesday, May 22, 2018 at 8:08 AM > From: "Christian Gagneraud" > To: "Jason H" > Cc: "Jean-Michaël Celerier" , "Thiago > Macieira" , interest > Subject: Re: [Interest]

Re: [Interest] QDatastream, QMap, QImage serialization

> Sent: Monday, May 21, 2018 at 4:02 PM > From: "Thiago Macieira" > To: interest@qt-project.org > Subject: Re: [Interest] QDatastream, QMap, QImage serialization > > On Monday, 21 May 2018 15:50:02 -03 Jason H wrote: > > I don't think C++ has a good concept of what it

Re: [Interest] QDatastream, QMap, QImage serialization

On Tuesday, 22 May 2018 05:07:05 -03 Konstantin Shegunov wrote: > > For example, QImage::paintEngine() queries the platform plugin to see if > > it > > > > can provide a better image painter than QRasterPaintEngine (for HW > > acceleration, I suppose). That is only possible because QImage is in >

Re: [Interest] QDatastream, QMap, QImage serialization

On 23 May 2018 at 00:25, william.croc...@analog.com wrote: > >> To summarise: >> - Qt is a graphical toolkit > > > ...and I used it to create a graphical application. > But then my users wanted to create hard copy from > batch jobs running on our compute farm. Those

Re: [Interest] QDatastream, QMap, QImage serialization

To summarise: - Qt is a graphical toolkit ...and I used it to create a graphical application. But then my users wanted to create hard copy from batch jobs running on our compute farm. Those machines do not provide access to an X server and, as we have discovered, Qt needs an X server for a

[Interest] Removing focus rect on macOS through StyleSheets

Is the css property "outline: none;" supposed to work on macOS? I can programmatically use Widget.setAttribute(Qt.WA_MacShowFocusRect, 0); I was hoping to just use the CSS property (which the internet says I should be able to do).I have read the docs (maybe not the correct ones) and I am not

Re: [Interest] QDatastream, QMap, QImage serialization

On 22 May 2018 at 02:03, Jason H wrote: > Going through the list of Qt GUI classes, there are several that I think > should be moved: > QImage > QStandardItem* It's GUI stuff, what's wrong with that? > Matrix and Vector classes Definitely, I should be able to do 2D/3D/4D

[Interest] Deploying the output of a static lib

Hi, I’m using the following pattern to create a static lib for iOS: include(shared.pri) TARGET = shared TEMPLATE = lib CONFIG += staticlib CONFIG(debug, debug|release): { QMAKE_POST_LINK += cp $$OUT_PWD/libshared.a $$PWD/build/debug } else { QMAKE_POST_LINK += cp

[Interest] QML iOS - can we download content to be executed

Dear all, I am interested to do an app that downloads new content from a server using QML on iOS, do you know if it is possible to download content (in QML) and to execute it? is this possible from a technical point of view but is it also allowed by the apple policy? and for Android? Best

Re: [Interest] QDatastream, QMap, QImage serialization

On Mon, May 21, 2018 at 7:57 PM, Jason H wrote: > 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"