Proposal to use QIcon in APIs in KF5.

[todd rme]

On Thu, Sep 8, 2011 at 10:59 AM, Aaron J. Seigo <aseigo at kde.org> wrote:
> On Thursday, September 8, 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.
>
> no, they absolutely will be deprecated. it will be like libkde3support, which
> will be going away in Frameworks 5 (due in large part to the Qt3 support going
> away in Qt5).

The original email explicitly said it would not be deprecated, so
there appears to be some disagreement on this issue.

"I do not (anymore) recommend any other changes at this time, such as
removing, changing or deprecating KIcon, because it seems to be
(surprisingly to me I must admit) a contentious issue."

-Todd