Benjamin Meyer ben at meyerhome.net
Fri Feb 10 20:16:50 GMT 2006

On #kde4-devel there was some chatting about the idea of dropping the 
kde3support library.  Anything that is '3support' is not meant as a final 
solution, but only as a porting help (or to avoid porting too much).  The 
main reason for removing it is that the library is something that people wont 
be using for very long, developers probably wont want to work on it, is 
taking up time and resources, it is just another library taking up more 
memory.  kde3support main purpose was to help bootstrap applications into 
kde4 until they fully ported to kde4 (like qt3support).  This means that most 
(all?) developers wont link to kde3support for very long (or at all).  Rather 
then spending time (compile time, support, testing, bug fixing, packaging, 
regressions, i.e. maintaining) these spend the time making sure that the docs 
and porting tools are in better quality.  So far we have just been dumping 
old classes in there so there hasn't been too much work, but they aren't 
exactly being maintained and I doubt people will be at all excited about 
maintining them in the future.  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.

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?

-Benjamin Meyer

aka icefox
Public Key: http://www.icefox.net/public_key.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060210/e2f4afeb/attachment.sig>

More information about the kde-core-devel mailing list