On Wednesday, January 07, 2015 20:31:57 Albert Astals Cid wrote: > > Albert has said he's fine with KDE Applications depending on Plasma (I > > think) > > http://mail.kde.org/pipermail/kde-frameworks-devel/2015-January/021332.htm > > l > > I said "I'm fine with KDE Applications depending on Plasma to improve > workpsace integration" or something like that. > > BUT libkscreen and libmm-qt don't seem > workpsace-integration-improvement-libs to me but basic libs to access > system stuff.
libkscreen is mainly for reading and settings X configuration. That's quite workspace-specific. For use-cases typical for apps, there's way easier API (QScreen, for example). libmm-qt ... I dunno, why would an app use it? (I can construct a weird use- case, but in the end, information about modem setup is a system / workspace- specific feature, not something typically done in apps. There are no hard boundaries, much depends on interpretation, but given it's debatable, I think keeping these things together in kde/workspace makes sense. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
