Feedback on Processing API

I'm new to Processing and created a Processing API for BoofCV. Was wondering some of you might be willing to look at it and provide feedback. Is it following standard practices and is reasonably intuitive? BoofCV is a computer vision library and I've already created several examples. The library will probably be hard to understand if you have zero experience in computer vision.

Thanks!

Comments

  • Nice. Awesome work. The examples look very clean, simple and nicely commented.

    In https://github.com/lessthanoptimal/BoofCV/blob/master/integration/processing/examples/DenseOpticalFlow/DenseOpticalFlow.pde you could use which = (frameCount / 12) % 2; No need for ticks.

    In https://github.com/lessthanoptimal/BoofCV/blob/master/integration/processing/examples/Contours/Contours.pde could we get the countour as vector data? Processing uses PShape for vector shapes.

    In general, it would be good to have access to the numbers and vectors (not only to a rendered image). This way we can decide what to do with the calculated values. We might want to turn it into music, or into 3D objects, instead of showing the default view :-).

    Types with _F64 don't sound very Processing like. I don't know if it's possible, but Processing has a PVector which might be used instead of Point2D_F64.

    Thanks for building a version for Processing!

  • Thanks for the feedback! I did consider using PVector but didn't like that it was 3D when the data was 2D. I noticed another library using PVector to store 2D data too. Maybe ease of integration with rest of Processing should override my sense of code ascetics in this case.

    Could you maybe give an example of where access to the "numbers and vectors" is missing? Technically you can access all that information, but might have to jump into the "lower level" BoofCV code to do so. I did try to provide access through the easy to use interface to data I thought might be of more 'artistic" interest.

    I'll do an official announcement a little bit later after the next stable BoofCV is out. Trying to do a low key introduction now to iron out the bugs so that there will be a good impression when the official release is done.

  • Hi, Your processing library links are not working. Are those links dead? Anyway on github you have a lot of folders. can you tell me which folder contains processing library?

  • The examples link goes to processing folder on github and seems to be working. Here's the path: boofcv/integration/processing/examples

    Boofcv.org appears to be very sluggish right now. No idea why that is. Worth trying again to see if it's back to normal.

    Alternatively you could do the following:

    git clone git://github.com/lessthanoptimal/BoofCV.git boofcv
    cd boofcv
    git submodule init
    git submodule update
    gradle processingZip
    

    Then the zip file will then be at integration/processing/boofcv_processing.zip

  • Can you tell me where to type commands ?

  • After installing github on windows I have typed the gradle command it says command doesnt found.

  • Please provide a working download. I would love to try this out.

  • Gradle is a build system that must be downloaded and installed on its own... Like Git, actually.

  • @PhiLho thanks :) After a little research I came to know that I need to install Gradle.

  • I figured out the problem with the link! The address for the zip was https instead of http. I edited the original post and have included the link below:

    Thanks again guys for looking at this!

  • edited June 2014

    The README.md on the latest Github code should also contain enough info on how to build everything. Thought it might be a bit too terse right now...

    There is one thing that is a bit tricker about building the processing code. You need to copy over 'core.jar'. This process is described in boofcv/integration/processing/readme.txt. Unforunately Processing isn't on Maven central so you have to do that manually.

Sign In or Register to comment.