Hello ofCommunity,
I configured a couple of gulp tasks for my own projects, which parse an addons.json file and clone the listed addons to my project dependent local addons. Then checkout the specified commit.
This way I can have different versions of the same addon and working simultanously on multiple projects, whitout having conflicts. This also makes the setup much easier for collaborators.
I am planning to port this to oF, removing the glup dependency and implementing some npm like functions to remove and add addons to the config file, or install addons globally.
Should we have a public register and using just addon ids, instead of just working with absolute urls? Can such a service be integrated in ofxaddons?
Do you guys have similar tools and scripts or how would you approach this? Would this be even useful for others?
Which is the preferred data format? JSON, xml or using the already existing addons.make.
I would like to know your opinions on this.
Thomas
