Fwd: Plasma 5.2 bits for kdereview
lamarque at kde.org
Thu Jan 8 15:45:25 GMT 2015
ModemManagerQt is used by two KDE Applications, Plasma NM and KDE
Telepathy. The former uses it to retrieve information about mobile
broadband connections (operator and signal quality), unlocking modem's sim
card when activating 3G connections, listing available modems in mobile
connection wizard when creating 3G connections and, with NetworkManager <
0.9.10, Plasma NM also uses MMQt to setup a bluetooth connections (which is
process initiated by Bluedevil, so it is a feature indirectly used by
Bluedevil too). The later uses MMQt to read/send SMS using a cell phone.
Lamarque V. Souza
KDE's Network Management maintainer
On Thu, Jan 8, 2015 at 1:04 PM, Sebastian Kügler <sebas at kde.org> wrote:
> 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)
> > >
> > > 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
> case, but in the end, information about modem setup is a system /
> specific feature, not something typically done in apps.
> There are no hard boundaries, much depends on interpretation, but given
> debatable, I think keeping these things together in kde/workspace makes
> http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kde-core-devel