faure at kde.org
Fri Feb 10 20:15:49 GMT 2006
On Friday 10 February 2006 21:16, Benjamin Meyer wrote:
> To decide if we want a kde3support or not, we
> really should ask app developers. they're the ones who might possibly use it
> or not.
Yes I would also like to know if those who will port KDE-3 apps to qt4/kde4 in the future
(e.g. from extragear or out of svn, not the modules being incrementally ported)
would plan to use kde3support.
> So for those who have ported your qt3 apps to Qt4 I inquire as to what you
> did. Do you still use the support libraries, how long did you use them, were
> they usefull?
... however qt3support is an entirely different thing. IMHO it's very unlikely that
all the code in main kde modules will ever move away from qt3support, in the 4.x timeframe.
Don't forget the size of the code we're talking about. For every listbox or
listview somewhere in kde, I don't see us rewriting it to QListWidget/QTreeWidget,
as long as the qt3support solution works. Every Q3PtrList in every kde utility, every
Q3ButtonGroup in every piece of code.... qt3support is most certainly useful,
and not only for the initial port, there is no doubt about that.
In short: "would you use kde3support" is totally unrelated to "would you use qt3support".
The answer to the latter is: yes, without a doubt.
But kde3support has (and will have) a much smaller number of classes.
(I think however that e.g. K3IconView, K3ListView, K3URLDrag, K3MultipleDrag
might be quite useful when porting kde apps, even if not really well-maintained,
but let's see what app developers think)
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
More information about the kde-core-devel