On Thu, 2 Dec 2010, IOhannes m zmölnig wrote:
the only thing i think you could possibly mean, is that it would be better to have [pix_v4l2] and the like, but i think it is one of the strengths of Gem that it allows a patch regardless of the OS.
You can achieve that with abstractions. Make [pix_video] an abstraction that picks [pix_v4l1], [pix_v4l2], [pix_ds], etc.
these people will now be relieved to learn that they can now finally control (most) parametesr.
congrats ! (that was one of the big reasons why I avoid using [pix_video] when I can)
another problem is, several devices using the same v4l2 backend expose different parameters. there are some standard ones (e.g. "saturation") but there are also custom parameters.
that's not a problem.
the "@" syntax is borrowed from max/msp where they have been around for ages (for object arguments, don't know about messages though) it is basically the same as miller's cmdline-arg-like interface as seen in e.g. [soundfiler]. i have to admit, that i don't like this interface at all - everytime i use it i shudder.
The @-syntax is also used in Flext. _______________________________________________________________________ | Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
_______________________________________________ GEM-dev mailing list [email protected] http://lists.puredata.info/listinfo/gem-dev
