Proposal to use QIcon in APIs in KF5.

[Alexander Neundorf]

On Thursday, September 08, 2011 10:58:49 AM Kevin Ottens wrote:
> On Thursday 08 September 2011 09:36:41 todd rme wrote:
> > Several people have proposed moving to a separate module classes that
> > are needed for existing applications but pose a problem for new
> > developers, are no longer needed, or clutter the API.  From what they
> > are saying, this seems to ease the porting efforts since KIcon will
> > not have to be changed to QIcon for any existing software, while
> > freeing the rest of the frameworks from dependence on this class and
> > making to clear to developers the QIcon should be used for any new
> > software.  This, from my reading, does NOT involve deprecating any of
> > the classes placed in the module, they will continue to be supported.
> 
> Thanks for pointing that out. It's definitely the point that got missed in
> those threads about KIcon ATM.
> 
> The plan in such a case is indeed
>  1) to introduce the new API replacing KIcon;
>  2) move KIcon in a new module (let's call it kde4support);

I guess it should be called "kdelibs4support", since the whole thing will 
still be KDE4, "just"  based on Qt5 and kf5 (or should it be kf 1.0 ?).

Alex