On Wed, 2006-12-20 at 18:32 -0500, David Moore wrote:
> Dear Damien and others on the libdc1394 list,
> I think there's a lot of work that needs to be done on libdc1394 before
> we can call it 2.0. It's become clear to me that the capture API as
> currently written is still too error prone and difficult to use
> correctly. I think a few minor changes to the capture start and stop
> API would help in this regard, and make it far more bulletproof and
> robust with resource allocation/deallocation.
> As such, I'd like to propose that the release date for 2.0 be slipped
> until January 31. I am volunteering to help get these API changes in
> place, but I'm going out of town in a few days until Jan 13, so I won't
> be able to contribute much time until then.
> How does that sound to people?
No big problem for me. I agree that recent discussions raised some
issues that should be resolved before 2.0. The end of 2006 was just a
target; I think we should release the library "when it's ready".
We have progressed on the last TODO list (27/11) but some items remain
and some new ones should be added:
5- Force the camera to a have a proper startup mode/framerate/
8- Check patch from Daniel Drake (branch prediction)
9- Add spec file for 2.0.0 (don't do it before to avoid 'wild'
11- Cleanup the control.h file (at least) and add more comments on each
function when necessary.
12- Produce some docs (doxygen etc.) I'm clueless here.
14- Update capture API (TBD)
15- Check S800 capture (maybe linux only)
If you have already some ideas about the capture cleanup/update let's
discuss it. I may have some time for coding during the holidays...
_ Damien 高原 Douxchamps, PhD
('- Post-doctoral investigator
//\ Image Processing Group, NAIST