From kde-core-devel  Sat May 26 22:18:55 2007
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: Sat, 26 May 2007 22:18:55 +0000
To: kde-core-devel
Subject: Re: Forthcoming changes for libsolid
Message-Id: <200705261618.56077.aseigo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=118021798512446
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart3078255.ETfL64dT3Y"

--nextPart3078255.ETfL64dT3Y
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Saturday 26 May 2007, Kevin Ottens wrote:
> 1) solid_isDeviceInterface.patch (monday 28th may)
> It simply renames Solid::Device::queryDeviceInterface to
> Solid::Device::isDeviceInterface. This method is not widely used outside =
of
> libsolid, the template convenience is more commonly used. This is a small
> cleanup, but necessary IMO to improve the discoverability of this API, th=
is
> way the class fully follow the is/as metaphor.

a definite readability improvement =3D)

> 2) (kdelibs|kdebase)_no_Solid_DeviceList.path (monday 28th may)
> Get ride of the useless DeviceList typedef. It's really unnecessary IMO, I

this should probably be consistent throughout kde's libs... if this goes in=
,=20
i'll probably end up changing libplasma to do similarly.

the nice thing about having typedefs such as this is that if the collection=
=20
class type ever changes, which is pretty much a "can't happen" in a public=
=20
lib, it makes it so much easier to port code =3D)

> My current plan is to move the eject() method to the OpticalDrive
> interface, where it actually makes sense (for instance this interface

of course there are many devices which also do eject that aren't optical: t=
ape=20
drives, some floppies (legacy hardware, admitedly) and other magnetic media=
=20
most of which is also legacy (jazz/zip for instance)

> 4) I'd need to rework a bit a few classes, mainly AudioHw, Camera and
> PortableMediaPlayer (monday 4th june). They need to be consistent in the

as an aside, there have been a few requests made at conferences i've spoken=
 at=20
this year for both still and video camera detection. solid seems to have a=
=20
nice interface for the former (which often can also do video too, as you no=
te=20
in the API docu) but i'm not sure how detection of webcams, DV sources, etc=
=20
are handled?

=2D-=20
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

=46ull time KDE developer sponsored by Trolltech (http://www.trolltech.com)

--nextPart3078255.ETfL64dT3Y
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBGWLJQ1rcusafx20MRAs+DAKCjcjXSAewb62CetDB7h55TsDNplQCgmdZu
yNR8bDuty1ZoxWqQH57Ze4k=
=9FDk
-----END PGP SIGNATURE-----

--nextPart3078255.ETfL64dT3Y--