No problem dominique.
a - I've attached the PolygonFinder.java source file (and Points.java helper class) that we are/were using to access the javacv stuff outside of the WPI API.
b - I've attached the WPIImageWrapper.java class which we are using to get access to the underlying IplImage object associated with each WPIImage object. To use this wrapper class, you construct a instance passing in a WPIImage object to the constructor. You can then use the getIplImage() method to gain access to the underlying IplImage.
NOTE: There appears to be a fix to the WPI image processing classes in the SmartDashboard that takes care of the memory leak. See
this post.
The PolygonFinder.java file attached has two entry points (one that takes a WPIBinaryImage and one that takes a IplImage).
Hope that helps,
Paul