--===============0663083074==
Content-Type: multipart/signed;
  boundary="nextPart1373617.QUFonWKUHc";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1373617.QUFonWKUHc
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 4 May 2009 21:53:48 Aaron J. Seigo wrote:
> I'm putting together a "where are we now, where are we going" snapshot of
> as many of the "big pieces" in KDE 4 as possible, and I'd like some input
> from you on Solid.

And I finally get to replying this mail (huzzah!).

> In particular, what I'm looking for are 2-4 bullet items for each of these
> two questions:
>
> * What have been the defining achievements in the last year?

Regarding libsolid it has been mainly about polishing the integration in=20
applications. It's hopefully getting pervasive now and doing its job (I'm=20
seeing more uses of it in our apps, and received no hate mail so we should =
be=20
doing ok). :-)

Regarding libsolidcontrol, it's been mainly about completing the APIs=20
themselves and about having default desktop apps using them. The most notab=
le=20
efforts there are PowerDevil+Plasma battery applet and the coming network=20
management applet. From the user point of view we're closing the gap with K=
DE=20
3.5 there, and that opens the door for new features (especially in the netw=
ork=20
management space I think).

> * What are the main focus points and or goals for the project in 2009?

I can't talk too much for libsolidcontrol as I don't contribute to it much=
=20
directly. I mainly monitor the situation and raise my grumpiness level when=
=20
it's not going in a direction I like (which almost never happens thanks to =
the=20
nice bunch we have there).

As for libsolid, for 2009 I plan to keep the API stable as usual. I'd expec=
t=20
only a few new classes. Most of the work will be internal, and the main foc=
us=20
for me will be: open the door to have several backends running in parallel.=
=20
That's a necessary move to kill some of the limitations we have right now, =
but=20
also to broaden the libsolid focus by making it able to also report about=20
networked devices like any other devices (think UPnP there).

> If you're feeling extra helpful, you might want to also provide some input
> on:
>
> * What are the major pain points in your project right now?

Overall we're doing ok on the technical front. On the community front I thi=
nk=20
I haven't been doing great with the UPnP efforts as apparently there some=20
things happening and I've a hard time being kept in the loop here (major ri=
sk=20
then being having some work done twice, two competing solutions, etc.).

> * Outside of the core libs (kdecore, kdeui, kio, kfile) what are the most
> critical pieces of KDE technologies that your project is relying on?

=46or libsolid itself: Qt, Qt and only Qt. At runtime we use some optional =
kded=20
modules, and some of the default apps in the Solid ecosystem are plasma=20
applets.

Regards.
=2D-=20
K=E9vin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le ma=EEtre sans disciple, Ni le disciple sans ma=EEtre,
Ne font reculer l'ignorance."

--nextPart1373617.QUFonWKUHc
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkoaPxwACgkQB0u7y43syeI3NQCdGdzE8bOu0kITX3DzOl0Z5XPV
+Y8AoIn5uDgmZLpo3nidQ7D9iaDLeOYZ
=FTPh
-----END PGP SIGNATURE-----

--nextPart1373617.QUFonWKUHc--

--===============0663083074==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-hardware-devel mailing list
Kde-hardware-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-hardware-devel

--===============0663083074==--