[libdc1394-devel] Minor API tweaks

[David M. <dcm@MIT.EDU>]

Hi Damien,

I'd like to make a few more tweaks to the API prior to 2.0 release:

1.  I'd like dc1394_camera_new(dc1394_t *dc1394, dc1394camera_id_t id)
to be changed back to dc1394_camera_new(dc1394_t *dc1394, uint64_t
guid).  This function will just imply a unit number of 0.  For those
very rare cases when a user has a unit other than 0, we will have a
separate function:
dc1394_camera_new_unit (dc1394_t *dc1394, uint64_t guid, uint16)

2.  I would like to make dc1394_t an opaque structure.  The user should
never need to peer inside without using functions such as
dc1394_enumerate_cameras().

3.  I would also like to make dc1394_camera_t an opaque structure.  This
is probably more controversial because many of these fields are often
read by folks.  However, I think we can add a simple function
dc1394_camera_get_info() which will return a struct of useful read-only
values such as port, node, etc.  Many of the values in dc1394_camera_t
are probably unsafe to expose directly to the user as they may change
asynchronously.

4.  Let's delete dc1394_find_cameras() and dc1394_camera_list_free()
from the API.


I suggest a final rc release before the final 2.0 so we can make sure
folks are happy with the new camera initialization API.  Maybe we can
aim for a deadline of this coming weekend to finish the last rc?

Also, I prefer gtk-doc to doxygen for creating docs.  Here's some sample
output:
http://library.gnome.org/devel/glib/unstable/index.html

I will try and make some time this week to implement some of the above
changes.  I also want to clean up the internals a bit, and make some of
the platform-specific internal API match the new camera initialization
API better.

Regards,

David