On Wednesday 11 April 2012 23:34:18 Stephen Kelly wrote:
> So here's my proposal:
>
> * kplotting should be renamed and repurposed as kwidgetsaddons (tier1), a
> framework which depends only on QtWidgets. The widgets in there should be
> self-contained and not rely on any 'KDE stuff' (This is one o
On Wednesday 11 April 2012 18:59:26 Stephen Kelly wrote:
> David Faure wrote:
> > Actually, KIcon* should be in kguiaddons, not in kwidgets, I think.
>
> That would make kguiaddons depend on QtWidgets, which may not be what we
> want (QIcon is in widgets).
It's really an unfortunate decision on th
On Wednesday 11 April 2012 20:44:32 Alexander Neundorf wrote:
> So, what I currently have in mind of how "KDE frameworks libraries" will
> install and how they will be usable:
>
> * each KDE frameworks library will install a KFooConfig.cmake file
> * by using find_package(KFoo CONFIG_MODE) this Con
On Thursday 05 April 2012 11:23:12 Stephen Kelly wrote:
> I looked into the CMakeLists for kwindowsystem today too and it seems to
> query X11_XFixes_FOUND etc without calling find_package(X11) or anything
> (That is, it doesn't build standalone).
Woops, my mistake!
> I have no idea about X11 or
On Wednesday 04 April 2012 12:22:58 Stephen Kelly wrote:
> Kevin Ottens wrote:
> > For this one, I'm pondering between either having it in the Qt 5.x pages
> > or start a new epic page just for it. Early on, we had those cases in the
> > Qt 5.x pages (KSaveFile was tracked there for instance). I'd
On Wednesday 11 April 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Saturday 10 March 2012, Alexander Neundorf wrote:
> > ...
> >
> >> Also, this means the term "KDE frameworks" doesn't actually mean a lot.
> >> I mean, what would make a library a "KDE frameworks library" ?
> >> Be
