K_EXPORT_PLUGIN & KAboutData in .cpp vs .desktop / KPluginInfo

2013-09-26 Thread Milian Wolff
Hey all, why do we have to set much redundant information in .cpp/KAboutData which is already somewhat defined by the KPluginInfo i.e. .desktop file? Point in case: KPluginSelector e.g. shows the Comment entry of the .desktop file. If thats too long its elided and if I go to the about dialog, I

Re: K_EXPORT_PLUGIN & KAboutData in .cpp vs .desktop / KPluginInfo

2013-09-27 Thread Sebastian Kügler
On Thursday, September 26, 2013 22:08:32 Milian Wolff wrote: > why do we have to set much redundant information in .cpp/KAboutData which > is already somewhat defined by the KPluginInfo i.e. .desktop file? > > Point in case: KPluginSelector e.g. shows the Comment entry of the .desktop > file. If

Re: K_EXPORT_PLUGIN & KAboutData in .cpp vs .desktop / KPluginInfo

2013-09-27 Thread Milian Wolff
On Friday 27 September 2013 12:40:13 Sebastian Kügler wrote: > On Thursday, September 26, 2013 22:08:32 Milian Wolff wrote: > > why do we have to set much redundant information in .cpp/KAboutData which > > is already somewhat defined by the KPluginInfo i.e. .desktop file? > > > > Point in case: K