Hi, Lets center in the technical aspects...
We should assume that Qt5 will have some kind of global icon cache, valid for every Qt application run in one machine, like KIcon has now. Am I Right? Then, without removing KIcon, it could be a thin layer (~1Kb) over QIcon. Why do not call QIcon::fromTheme() in KIcon constructors, and then nothing changes in the KDE land. > in fact, for qt5 we defined "source compatible" to mean "porting can be fully > automated". By the way, if "source compatible" means "porting can be fully automated" (I guess like in Python 2 to 3), you (Qt and KDE frameworks) MUST provide such a porting tool. Best Regards.
