Re: [Utopia] KDE Volume Manager

[Jerome Lodewyck <lodewyck clipper ens fr>]

On Fri, 20 Aug 2004, David Zeuthen wrote:

> Hi,
>
> (side item: care to point me to some (generic perhaps?) instructions on
> how to compile it? I'm staring at a configure.in.in and no autogen.sh
> etc. Thanks.)

Actually, the CVS compiling intructions are in the README file. The
INSTALL file is for releases. However, compiling it requires some hacking
in the dbus-qt bindings because they do not provide main loop integration
(http://freedesktop.org/pipermail/dbus/2004-August/001449.html ). I will
try to make a complete patch tomorrow.

> > check for tracks and eventually play it. But for VCD, it is much more
> > complicated since xine (I haven't checked other players) doesn't play
> > mounted VCD's. So the steps are : mounting, checking for tracks,
> > unmounting and playing. Quite tricky and lengthy. So a volume.disc.is_vcd
> > would be much more convenient.
> >
>
> Yup, we kind of discussed what the hal daemon should and shouldn't do on
> the hal mailing list on freedesktop.org a while back. I think the
> conclusion was that HAL should stay out of policy and only care about
> presenting the device objects it sees in a somewhat abstract way with
> minimal interference to the system (e.g. don't do any invasive polling
> etc. that breaks existing software).

I agree. However, a non-ivasive polling for VCD would be nice... Is there
a VCD expert on this list ?

> And since it involves policy (mounting/unmounting) I think kvm/gvm is
> the right place in the stack to do this. It would be cool, however, to
> share some of this code between gvm and gvm though; one thing to do
> would be to stick it in a library libhal-volume (could have native Qt
> bindings) and ship it with hal?
>
> Another reason for doing this is that we could share code (and, perhaps
> more important, policy) for actually selecting the icons representing
> the volume and the name representing the volume, see
> http://freedesktop.org/~david/gnome-vfs-take3-1.png for how GNOME VFS
> does this when built with --enable-hal. The result would be greater
> integration between e.g. Konqueror and Nautilus and some standardisation
> on the icon names. Heck, even fstab-sync could use this library for
> creating mount point names.

I really like the idea of a shared naming policy. Furthermore, making a
desktop independent library for this should be quite straightforward
(except for internationalization). But for icons, this would require much
prior work, since gnome and kde don't share icon names and icon set.

Jerome