Fork of Control P5 and rewrite about controlp5 HOT 1 CLOSED

Hello Jeremy,

thank you for letting me know about your efforts in making adjustments to controlP5 and adding more features. just wondering, did you fork from this (github) repository or from the older code.google repo? the most up-to-date version is this github repository.

Some of the features you are mentioning, for example the PGraphics context, have been added over time. I haven't looked close enough into the compatibility of controlP5 with other processing implementations like Ruby or Python but there has been some activity and working results with the Python mode.

Browsing through your repo I noticed there was a change in package naming which might be a conflict if merged. The restructuring of the code base had been a consideration a while back but I decided to keep a flat hierarchy to avoid import issues (which package contains which files? which packages do I need to import? etc. this often causes confusion especially for beginners) and also to keep controlP5 backwards compatible. ControlP5 started almost 10 years ago as a small helper library and since did undergo various transformations and has grown quite large (not necessarily to the benefit of the library), introducing a change in structure at this point would be problematic and not a strategy I would like to pursue.

best,
Andreas

from controlp5.