RPath is a sequence of commands lineTo, quadTo or bezierTo.  moveTo is not part of the commands since this command just creates a new path.

RContour is just a sequence of polygons vertices (as in a polygon without holes).  In the long run I would like to drop all this differentiation between contours and paths, and contours would just become RPath with only lineTo.

However I think you would rarely need RGroup, RPolygon RContour, etc.

Normally RShape and RPath should be sufficient, the other classes are mostly there for backwards compatibility and for performance (e.g. if you know you are often going to draw the same shape to the screen and you know the backend is OPENGL then the best is to transform to RPolygon only once and then just draw the RPolygon as many times needed, but this is just due to limitations of the OPENGL backend and not good for other backends such as PDF where you want to draw the shape using the commands beziers, quads, etc.).

RGroup existed before in order to represent a hierarchy of shapes, but I have modified the library so that it is more similar to PShape, this would allow to easily switch from one to the other.  So now only RShape is needed and has a field called children which is an array of children shapes.  It also has all the methods that RGroup used to have (e.g. contains).

And finally RG which is a static class containing a procedural API very similar to Processing's is preferred to the classes for loading RSVG and RFont or the RShape and RPath constructors.

These are the major differences from the old Geomerative and the new one.  However I tried to keep the new one as backwards compatible as possible in order not to break existing sketches.

ricard

Quote:


This is already possible using the RG.setPolygonizerXXX() methods.  Check the Tutorial 07 that is in the tutorials directory in the library folder.
In any case for faster preview and if you don't need equally spaced vertices I would use:
Code:

RG.setPolygonizer(RG.ADAPTATIVE);
RG.setPolygonizerAngle(angle); 

where setPolygonizerAngle() is used to set the angle tolerance of consecutive segments when evaluating the vertices.

I know this is not the best name for the methods, but setSegmenterXXX() which was used before was not better.  Recommendations for better names are very welcome.

Quote:


These would definitely be nice to have.  I have also needed this in the past and ended up doing it manually, I'll see if I can add these to Geomerative in the coming days.

Quote:


Hm... I actually haven't used the library for a lot for 3D stuff.  Only in Cascade On Wheels of Steph Thirion and in Casas Tristes.  In both cases I did 3D extrusion of shapes but I didn't need to flip the back faces, I guess because in both cases there was no needed to see the back side.

I will do a little test and see what method could be helpful for this task.