You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, this is really a larger issue to discuss with the open frameworks community, but i've noticed that both Processing and Arduino (with it's new Tre, etc) are going in the direction of "certified" addons and libraries. This has me thinking about doing the same for ofSketch. Certification may be the wrong word -- perhaps it's "curation". Basically the goal for something like this would be to better enforce adherence to the of the ofxAddonTemplate which makes a world of difference when trying to incorporate addons programatically.
The pros are that we could potentially eliminate a whole class of bugs and frustrations getting started with ofSketch. For some developers, "certification" may be a motivation, for others it may be a deterrent.
The major cons would be -- creating a "hierarchy" that might turn off some newer coders eager to contribute but unable to commit the extra time to ensuring cross platform compatibility etc. Additionally, there would have to be a gatekeeper or scoring system or automated build system that could test for inclusion -- automation would be the best in my mind, but not trivial to build such a system.
Anyway, the ultimate goal here is to make the introductory user experience with ofSketch and openFrameworks painless without causing some addon developers to feel like their work (while potentially incomplete) is not appreciated.
The text was updated successfully, but these errors were encountered:
So, this is really a larger issue to discuss with the open frameworks community, but i've noticed that both Processing and Arduino (with it's new Tre, etc) are going in the direction of "certified" addons and libraries. This has me thinking about doing the same for ofSketch. Certification may be the wrong word -- perhaps it's "curation". Basically the goal for something like this would be to better enforce adherence to the of the ofxAddonTemplate which makes a world of difference when trying to incorporate addons programatically.
The pros are that we could potentially eliminate a whole class of bugs and frustrations getting started with ofSketch. For some developers, "certification" may be a motivation, for others it may be a deterrent.
The major cons would be -- creating a "hierarchy" that might turn off some newer coders eager to contribute but unable to commit the extra time to ensuring cross platform compatibility etc. Additionally, there would have to be a gatekeeper or scoring system or automated build system that could test for inclusion -- automation would be the best in my mind, but not trivial to build such a system.
Anyway, the ultimate goal here is to make the introductory user experience with ofSketch and openFrameworks painless without causing some addon developers to feel like their work (while potentially incomplete) is not appreciated.
The text was updated successfully, but these errors were encountered: