On 10/14/11 10:36 AM, "ext Girish Ramakrishnan" <[email protected]> wrote:
>Hi Guys, > >On Mon, Oct 10, 2011 at 6:15 PM, Girish Ramakrishnan ><[email protected]> wrote: >> Hi, >> >> On Mon, Oct 10, 2011 at 3:58 PM, Joerg Bornemann >> <[email protected]> wrote: >>> On 08/10/2011 09:08, ext Girish Ramakrishnan wrote: >>>> My suggestion to rename Gui was more practical. >>> [...] >>> >>> Another way would be to provide a (very simple) qt4support module that >>> maps the old headers to the new names. >>> Then you must have a Qt4/Qt5 section in your .pro file though to use >>> that module. >>> >> >> Yes, one approach to have compat headers. I think we that approach >> though it's hard to see which is the "latest" and which is >> "deprecated" (this is unlike the qt3support where things had a Q3 >> prefix) >> #include <QtGui/QLabel> // compat header by qt4support >> #include <QtGui/QWindow> // new header >> >> Or is there a better approach than above? >> >> There's a lot of apps out there that use <QtGui> and <QtGui/*>. I >> think we should be considerate and not have them change it all to >> QtWidget for no real benefit. Here's some stats: >> http://codesearch.google.com/#search/&q=%23include%20%3CQtGui%3E&type=cs >> >>http://codesearch.google.com/#search/&q=%23include%20%3CQtGui/%5Cw*%3E&ty >>pe=cs >> > >Did we reach any conclusion on this? Is this idea of renaming gui to >something else: >a) Awesome but nobody cares though to do it (...in which case I volunteer) >or >b) Good but it's too late. We are going to make the world change the >include headers and we are probably going to have a qt4to5 script that >makes this change? (...I do think this change is unnecessary though) >or >c) Just plain horrible (If there is a problem with the above idea, >please let me know) We've been discussing that, but the conclusion was to stick with QtGui. The problem is that whatever you do, you'd break something (since we do split up the old QtGui). The best thing we could think of are Qt4 compatibility headers, ie. a Qt4 compatible directory structure for headers that you can enable with a switch in your profile. But someone would need to do the work in syncqt and probably a few other places to enable it. I however found out that a script for fixing the headers is not that big a problem. Only place where this wouldn't work is if you want one code base to support both Qt4 and Qt5. Cheers, Lars _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
