Re: Moving stuff upstream (was: A Qt replacement for KGlobal::ref and deref)

2011-02-16 Thread Stephen Kelly
David Jarvie wrote: >> >> Anyway, I've started a page to document such things at >> http://community.kde.org/KDE_Core/QtMerge , feel free to add stuff there. >> David Jarvie, could you add something to the KDateTime entry? > > Done. I hope it contains enough explanation - if you think it needs mo

Re: Moving stuff upstream (was: A Qt replacement for KGlobal::ref and deref)

2011-02-16 Thread Stephen Kelly
John Layt wrote: > On Monday 14 February 2011 22:35:13 Stephen Kelly wrote: >> You might think in terms of how much a typical KDE application ends up >> using, but I'm thinking in terms of how much a typical Qt application >> ends up using. Gregory is not going to end up using KLocale KConfig >> K

Re: Moving stuff upstream (was: A Qt replacement for KGlobal::ref and deref)

2011-02-16 Thread David Jarvie
On Wed, February 16, 2011 11:57 am, John Layt wrote: > The thing is, most of what is in kdecore date classes really does belong > in the Qt classes, these are standard things on all platforms that Qt just > hasn't > implemented. QLocale is bizarrely incomplete in places. Why wouldn't Qt > want >

Re: Moving stuff upstream (was: A Qt replacement for KGlobal::ref and deref)

2011-02-16 Thread John Layt
On Monday 14 February 2011 22:35:13 Stephen Kelly wrote: > You might think in terms of how much a typical KDE application ends up > using, but I'm thinking in terms of how much a typical Qt application ends > up using. Gregory is not going to end up using KLocale KConfig KDateTime > etc just becaus