--nextPart1291626.T1G9Vj4O88
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Tuesday 03 November 2009 9:50:19 am Jacopo De Simoi wrote:
> On Tuesday 03 November 2009 02:15:20 Trever Fischer wrote:
> > On Monday 02 November 2009 6:45:18 pm Jacopo De Simoi wrote:
> > > On Monday 02 November 2009 23:56:14 Jacopo De Simoi wrote:
> > > > > So you /don't / have to use UDIs (unless you're manually adding to
> > > > > the list) to use the feature.
> > > >
> > > > I believe we need to get rid of the UDIs and provide some more not
> > > > just user-friendly, but "human-friendly" strings.. Having to deal
> > > > with them even in some cases is not really acceptable. I'll try to
> > > > have a look into this to see how we can sort this out
> > >
> > > Just quickly playing with the solid minibrowser I have a few
> > > suggestions
> > >
> > > First of all, show whichever icon solids give to the device, it really
> > >  really helps to figure out what we are talking about even before we
> > > start reading.
> > >
> > > The volume property info.product is quite uninformative (usually
> > >  Volume(ext3)), but if you jump back to the closest relative which has
> > > a info.product property you will find quite interesting things, such =
as
> > > ExpressCard, or stuff like that.
> > >
> > > Then I'd compose a string with the following field (with parent I mean
> > > the closest device in the hierarchy which has the infos required)
> > >
> > > parent.info.vendor parent.info.product volume.info.product (size)
> > > Some real-life examples:
> > >
> > > Seagate FreeAgent Go Backup_HD (160 Go)
> > > ST325082 0A MediaHD (250 Go)
> > > Lexar ExpressCard ssdhome (5 Go)
> > > Lexar ExpressCard ssdroot (3 Go)
> > > SD02G Volume (ext3) (2 Go) (with SD icon)
> > > Kingston FCR-HS219/1 MicroSD (2 Go) (I'm cheating here... MicroSD is
> > > the volume label)
> > >
> > > Still, as you can see there's room for improvement, in particular the
> > >  second guy was giving quite debatable information about itself
> > > (however still better than
> > > /org/freedesktop/Hal/devices/volume_uuid_ECBF_30CC)
> >
> > Nonetheless a good idea. I added it to the GUI.
>=20
> Ok, now this looks much better; what about this, now, to make it look even
>  better;
>=20
> If (and only if) there exists more than one volume with the same parent,
>  group them with the parent; then the parent will be shown with vendor()
>  and product() and total size (should be available with
>  storage.removable.media_size) and then each child (partition) would just
>  show description() and size This is visually better since it removes
>  redundant information for partitions of the same drive. and makes it
>  easier to browse.
>=20
> On the other hand, if a volume is an only child, then don't add another
>  node and use the long description we talked about yesterday.
>=20
> Also, imho the informations should be refreshed even if it's already
>  present in the .rc file whenever possible; besides; who is responsible to
>  fill in the devices in the .rc file? the daemon I suppose; would it be
>  possible to save the pretty name we have found for our device at the
>  daemon level? so that whenever you connect the drive, the user would find
>  it with its pretty name in the disconnected devices node as well. Having
>  it set up at the daemon level could make the kcm part merely read it from
>  the .rc since it will be automagically updated.
It does that. The only reason for having the code to generate a name is for=
=20
the condition where a new device is plugged in and the daemon hasn't writte=
n=20
the name to the .rc yet. I'm sure there's a much better way involving dbus=
=20
signals or using dbus to just ask the daemon for the list of devices.
>=20
> Moreover, I believe that the Add device button is useless; nobody would
>  really enter the udi of a device.
>=20
> Nice job!
> @Albert, what  do you think about the ui fixes?
>=20

=2D-=20
Trever Fischer (tdfischer)
=46edora Ambassador, KDE Hacker
http://wm161.net
GPG: C40F2998 hkp://wwwkeys.pgp.net

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

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

iEYEABECAAYFAkrwTDcACgkQNg53/sQPKZjPVgCfQgjN6YDIJ/ZR+OkFQW2lJF0W
SYUAn0u2DM59j9ot1h2cbNh9tDZ9B2NH
=9FPf
-----END PGP SIGNATURE-----

--nextPart1291626.T1G9Vj4O88--