[Rock-dev] Cleaning up camera stack

[Sylvain Joyeux]

On Mon, Mar 2, 2015 at 11:38 AM, Alexander Duda <Alexander.Duda at dfki.de> wrote:
>> drivers/camera_ids
>> drivers/camera_firewire
>> drivers/camera_unicap
>
> All basic camera access can be done with opencv. If you are looking for
> more advanced cameras you should use cameras supporting GeniCam.

The idea of having a GeniCam orogen component is awesome, given that
GeniCam really seems to become the standard API for industrial
cameras. But this does not have to be a either-or, just a "and". I
don't see a problem with keeping the orogen components for the cameras
that are not supported by genicam. Stop supporting them personally if
you want, and someone else (Matthias ?) can decide to become their
maintainer if he wishes to. I see *NO* need whatsoever to have a
common camera interface for all cameras on the earth. As you mention
it yourself in the shortcomings of the current approach, that leads to
a lot of layering and complexity.

Which leads to the following remarks (based on the wiki):

   -  implement new orogen/camera_base

Why ? Why not only orogen/camera_genicam ? You start again with some
kind of an "interface" !

   - string based setter and getter for camera features

I assume that you mean "operation" ? Why not properties instead ?
Operations are not logged and cannot be set in configuration files
(and you can change properties dynamically nowadays if you wishes to)

Sylvain