[Development] Feature freeze date?

Thiago Macieira thiago.macieira at intel.com
Fri Jan 6 20:08:53 CET 2012


On Friday, 6 de January de 2012 15.45.13, lars.knoll at nokia.com wrote:
> >- Go over the modules and factor out platform stuff like:
> >
> >#if defined(Q_WS_WIN)
> >
> >         SystemParametersInfo(SPI_GETDROPSHADOW, 0, &shadow, 0);
> >         shadowWidth = shadow ? 0 : 6;
> >     
> >     }
> >
> >#elsif defined(Q_WS_MAC)
> >
> >   shadowWidth = ....
> >
> >#endif
> >
> >The API needs to be as flexible as possible (QVariant themeHint(enum
> >what)). Still, if the feature freeze happens before finishing the
> >reorganization or important stuff that needs to go to those plugins is
> >discovered later on, there is a chance for source compatibility breakage.
> 
> Same as above. I agree with you in an ideal world, and the more we can do
> here for 5.0 already the better. But if we don't get it all done and do
> have some platform dependencies in there, it's most likely not the end of
> the world for 5.0 :)

Any and all Q_WS_* outside the platform plugins must be gone by the time of 
5.0 release. They are dead code.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
     Intel Sweden AB - Registration Number: 556189-6027
     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120106/3eca7ac3/attachment.sig>


More information about the Development mailing list