User Extensions workflow for multiple developers

Hi,

We are a team of 3 developers starting a new project and we need to implement a few reusable user extensions to share within the same project.

I am trying to wrap my ahead around the workflow of creating AUX files reading the tutorials online, oh boy... not fun stuff:

1. You have to code the reusable control by hand or using Architect as a helper tool to get the JS logic implemented, so far so good, but I still have to create defintion files, edit package.json by hand... DONE.

2. You need use a test system to ensure that Architect loads the extension, if it doesn't you have to edit these definition files until it works. At this point if something goes wrong you will be probably working with 2 copies of the same source code..the original development code and the one you are trying to get to work in the test system... DONE.

3. Now you have to package into an AUX file by clicking the extension name and choosing the option to generate AUX file... CONFUSED.

Am I now supposed to be doing development work (package the AUX file) in the TEST system???

Now here is my question for the experts... It looks to me that this is too much work to maintain all developers in sync with the latest fixes and improvements that will surely happen as we progress... I mean edit code, repackage extension outside the architect workflow, redistribute AUX files, etc...

Wouldn't it be easier if all developers go to Edit->Preferences and point their User Extension folder to a common folder under source control? This way developer A edits the user extension then developers B and C get the latest code from source control and their Architects would automatically load the latest extension code.

Would that work? It there a simpler approach?

Thank you

User Extensions workflow for multiple developers