Am Freitag, 3. September 2004 11:48 schrieb PUYDT Julien:
> Hi,
>
> now that the flaming is over:
>
> 1) any device plugin should accept to open things under as many names as
> possible (user-friendly, devices or whatever) ;
This may be a point to discuss:
Lets assume you have a unique identifier (this has not to be stable, see
below), which identifies the device on the operating system level (/dev/dsp0,
hw:0 for alsa, /dev/video0 - dont know Windows) and is a string, and each of
these identifiers has an userfriendly name assossiated with it.
So either you do the matching in the library/plugins (ie I want to
open("webcam"), or in the application.
I think doing the matching in the application is the best way, GUI programs
can show the devices in a list with a unique userfriendly name (if you have
doubles, suffix the name with "(1)", for example, if you dont have a
userfriendly name, use the id), the user chooses the wanted device, and the
app requests the library via the id to open the device. For command line
arguments, you can do a string or substring matching.
I think this approach gives every application the possibility to do what it
wants. I think implementation is simple and straightforward.
> 2) any device plugin should probably avoid giving the same device
> several times under different names: it should give it under the most
> convenient name (I know I'm hiding the issue behind "convenient", but
> the point is: no duplication) ;
>
> 3) at least one device plugin already has no link to a /dev file: the
> AVC plugin just knows about a device number on the IEEE1394 bus (if I
> remember well), and hides it by getting the name of the device ;
Same is true for ALSA, afaik. I think doing the id/ufname translation should
be done in the application.
> 4) if you[Craig] really look forward to see GM on win32, perhaps you can
> help Damien to shake Xavier Ricco, who volunteered to do the port, said
> he could get it running, but didn't give any details on neither how to
> make it compile/run (patch or some such) nor how well it worked, before
> he left for vacation ;-)
>
> 5) it isn't exactly about the flaming subject, but since it was about
> pwlib's plugins and the win32 port was mentioned: pwlib lacks a video
> input plugin on MOSX, and that's as far as I know the only thing that
> prevents a GM port on MOSX...
So it should work with the fake plugins? Where is it?
BTW, on the QT pages [1] (I know, the evil, ugly toolkit :-), there was a
article about application deployment on OS X.
Stefan
[1] http://doc.trolltech.com/qq/qq09-mac-deployment.html
--
Stefan Brüns / Kastanienweg 6 - Zimmer 1206 / 52074 Aachen
mailto:lurch gmx li http://www.kawo1.rwth-aachen.de/~lurchi/
phone: +49 241 169-4206 mobile: +49 160 3797725
Attachment:
pgpYgM0wK92Vs.pgp
Description: PGP signature