I suppose it would not be a detriment. Where do you draw the line? Which platforms, what functions and types?
Here are some candidate types for constructors and conversion operators on their corresponding Qt types, which I can think of off the top of my head: Windows: POINT RECT HICON HBITMAP Darwin (OS X + iOS): CGPoint CGSize CGRect NSPoint NSSize NSRect CGImageRef CIImage NSImage NSString and CFArrayRef/NSArray <-> QList<T> ? I'm not sure about other platforms/environments like X11, Wayland, or perhaps GNOME. Jake Petroules Petroules Corporation (www.petroules.com) Email: [email protected] Telephone: +1 (970) 587-3821 On Mar 1, 2013, at 4:24 AM, Sorvig Morten <[email protected]> wrote: > > On Mar 1, 2013, at 8:27 AM, Jake Thomas Petroules > <[email protected]> wrote: > >> Why are we discussing adding conversion operators from/to native objects in >> QtCore/QtGui? The methods that did so were removed in Qt 5 in order to >> increase modularity, why would we go the opposite direction again? > > The argument for would be along the lines of: We went too far in the name of > modularity. Adding conversion operators to QtCore and QtGui makes it easier > to mix Qt and native development. It makes Qt better. > > I'm positive to the idea myself, and so far I haven't seen really convincing > arguments against. I don't think adjusting the course of Qt 5 is a big > problem. > > Morten > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
