[Releasing] [Development] Starting preparations for Qt 5.1

Jake Thomas Petroules jake.petroules at petroules.com
Tue Mar 19 17:16:03 CET 2013

I think we should just postpone the extras 'till 5.2, yes.

QtWindowsExtras needs a ton more work - Ivan Vizir's big Windows 7 features commit is still not ready and likely won't for a while. I believe he said he is planning a second commit with more of them since thumbnail toolbars were left out of his first one for reasons of time. Like Morten said, QtMacExtras needs a lot more polish too. Unfortunately he and I are the only ones working on it.

As for the operators, I remember there was a discussion on IRC suggesting we simply declare the methods and operators and forward declare the types necessary in QtCore/QtGui, and implement them in QtWindowsExtras/QtMacExtras. Then the former need not link to any additional libraries.

My vote is for constructors and conversion operators on (the all caps types are Win32 types):

QString <=> NSString
QPoint <=> CGPoint, NSPoint, POINT
QSize <=> CGSize, NSSize, (there's no `SIZE` afaik)
QRect <=> CGRect, NSSize, SIZE
QMargins <=> MARGINS

Darwin has a lot of image types. UIImage converters are not strictly necessary since UIImage has easy methods to/from CGImageRef since iOS 2.0. However, something like: `inline UIImage* QImageToUIImage(const QImage &image) { return [UIImage imageWithCGImage:QImageToCGImage(image)]; }` would save typing so I think we should add them anyways. Similar story with CIImage (except there's no CIImage -> CGImageRef and can't be from the looks of the API).

QIcon <=> HICON
QImage/QPixmap <=> HBITMAP, CGImageRef, NSImage, UIImage, CIImage
QString <=> CFStringRef, NSString

Anything else?

After all this, though, I think we should still implement the constructors and operators in terms of free functions so that the converters are also usable by Qt 4.

Are there any objections to this? Can we start adding constructors and operators to QtCore and QtGui?
Jake Petroules
Chief Technology Officer
Petroules Corporation ยท www.petroules.com
Email: jake.petroules at petroules.com

On Mar 19, 2013, at 2:52 AM, Sorvig Morten <Morten.Sorvig at digia.com> wrote:

> On Mar 18, 2013, at 5:05 PM, Knoll Lars <Lars.Knoll at digia.com> wrote:
>> On 3/18/13 4:58 PM, "Laszlo Papp" <lpapp at kde.org> wrote:
>>> On Mon, Mar 18, 2013 at 3:52 PM, Thomas McGuire <thomas.mcguire at kdab.com>
>>> wrote:
>>> QtSensors needs to be added to qt5.git, but couldn't yet, due to CI
>>> failures.
>>> See https://codereview.qt-project.org/#change,48905.
>>> + QtSerialPort: https://codereview.qt-project.org/#change,49157
>> + Mac and X11 extras. Yes, these are known.
> QtMacExtras is currently not in a releasable state. It's missing documentation, some examples and needs some general polish and bug fixes. 
> I think we also need to resolve the "native type" converters discussion to know which API's goes into QtMacExtras. 
> Since we are running out of time for 5.1 - should we postpone it to 5.2?
> Morten
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20130319/2c3a397b/attachment.html>

More information about the Releasing mailing list