Converting a library to work with 2.0+?

zen.webb

Converting a library to work with 2.0+?

in Contributed Library Questions • 26 days ago

I'm looking at updating a library (SurfaceMapper) that currently only works with Processing 1.5.1, and I'm curious about what is necessary to make it work with 2.0+? I haven't been able to track down any good articles about what needs to be done, so I'm curious if someone can give me some tips about what needs to be done in general.

Replies(2)

PhiLho

Re: Converting a library to work with 2.0+?

25 days ago

I would say that basically, you would need to follow the instructions to make a library for 2.0, removing the obsolete calls, adapting some, and so on. I suppose it is a case by case process, there is no magical recipe, alas.

andres

Re: Converting a library to work with 2.0+?

25 days ago

Hello, I second what PhiLho said, there is no general recipe for porting libraries from 1.x over to 2.0. However, the notes from the changes page in the wiki could be useful, specially those about event handling in 2.0, which went through a major overhaul. The github wiki page about library development also has relevant information.

I took a quick look at the SurfaceMapper source, the additional problem here is that it relies on GLGraphics, which is a library that only works for 1.5. Most of GLGraphics functionality is now part of the core opengl renderer (P2D and P3D), for example you should be able to re-implement GLGraphics' filters using the PShader class ( this tutorial goes into the details of the new shader API in Processing 2.0 ), with PImage handling the OpenGL textures automatically. What will be a bit trickier to reproduce is the GLTextureWindow functionality, which allowed to put the contents of an image on a separate window. I started working on a small utility library for creating native gl windows, which we plan to include as a core library in the next stable release. This might be able to offer an alternative to GLTextureWindow.

Top Reply