[Development] Suggestion on QML portability
André Pönitz
andre.poenitz at mathematik.tu-chemnitz.de
Mon Jul 16 20:37:15 CEST 2012
On Mon, Jul 16, 2012 at 01:50:42PM +1000, Alan Alpert wrote:
> On Mon, 16 Jul 2012 03:18:02 ext André Pönitz wrote:
> > On Mon, Jul 16, 2012 at 10:02:33AM +1000, Alan Alpert wrote:
> > > The theory is that you're not trying to maintain a single codebase
> > > for both QML1 and QML2.
> >
> > [Maybe it's about time to run reality checks on certain theories
> > anyway...]
>
> It's a major version change, what did you expect? It's a pain to
> maintain even a QWidget application for a single Qt 4 and Qt 5
> code-base, [...]
This is incidentally one of those theories in need of a reality
check I was refering to.
The assumption is wrong, as proven by the example of Qt Creator.
After some initial effort to make it compile with Qt 5 at all
(mostly due to the modularization and the Gui/Widget schism) it
compiles rather nicely with Qt 4 and Qt 5 from a single code base
without much #ifdef hackery.
It is definitely maintainable in that form. Good old Qt stuff.
Create once, deploy everywhere.
Andre'
More information about the Development
mailing list