Luca Del Tongo's profile - activity

Given that it was quite simple to reply to this question I did it :-) Feel free to delete it as it's not related to opencv and break site rules...

You should use EmguCv classes and C# features. Here is a small toy example that replicate what you want to do :

         using (MemStorage storage = new MemStorage()) //allocate storage for contour approximation         
     {
         Contour<Point> contour = new Contour<Point>(storage);


             contour.Push(new Point(0, 0));
             contour.Push(new Point(0, 10));
             contour.Push(new Point(10, 10));
             contour.Push(new Point(10, 0));

         double area0 = contour.Area;
         Contour<Point> approxContour = contour.ApproxPoly(contour.Perimeter * 0.05, storage);
     }

Hope this helps, Luca

I take a look at your wrapper and made a simple toy example with it and it works fine. The additional benefit of your wrapper and the only thing that seems more difficult to automate is GC management, other than that it seems possible to create a generator that produce an output similar to yours.

Great news from you !!!! Maybe the best thing for the whole community would be to join your effort into pull request for C# automatic wrapper https://github.com/Itseez/opencv/pull/604

@Jean-Francois Thanks a lot for your comment. I agree with you, I developed more than one year ago my master thesis using Emgu (and some youtube tutorials) and it's the best wrapper for .NET developers. I see only some potential issues: 1) only one developer 2) Being an hand made wrapper this can introduce another layer of bugs 3) it's not always up to date with opencv, especially lately with new opencv development cycle

Maybe it could be an interesting project to insert into gsoc2014 :-)

Thanks a lot Kirill for your detailed explanation. As you underline, latest opencv c++ api is really more OO, so it makes sense to simply wrap it. EmguCV is really good but one of its major issues is licensing. I agree with you on your performance concerns about using IKVM + JNI calls. It' just an idea but maybe the best strategy could be the one defined by sharpdx, i.e create a tool to autogenerate wrapper from opencv headers.

I read latest Opencv roadmap presentation and I'd like to have some more info on c# bindings.

I'd like to know if they will be shipped with final Opencv 3.0 release or not. It would be also interesting to know if it will be a simple wrapper or more object oriented following the approach proposed by EmguCV.