EDIT: I hope I didn't come across to rough here ... was written after hours on the road driving
But, to complete my thought, and throw in some encouragement, to increase the priority for making C2 projects more easily reusable:
As a beginning C2 developer, I was not aware of the limitations in reusing assets from one project to another. I therefore happily developed 8+ carefully crafted little game apps. Creating little reusable apps is a software engineering best practice, and would be good practice in C2 also. And my plan was to then mix and match the game apps in various ways to develop larger "story lines".
This is something I can not do right now, without carefully reviewing each little game app, with re-usability and current C2 limitations in repackaging games in mind. I will just have to "bite the bullet", and spend the time on essentially restarting all game apps, to make them more reusable, while our project clock continues to tick, and users are waiting to be participatorily tested. And I foresee running into such code reuse problems again, since its hard to anticipate what new game assets one will need, and how such needs would ripple through various games variants I will further need to develop, that are built on a common base. And, manual managing these ripple task is time intensive and error-prone.
While new functionality is indeed a high priority, support for sound software engineering practices is also essential for the creation of maintainable and evolvable software code. Its not by chance that technologies such as object-orientation, and software architectures have gotten the tremendous attention over the last two decades, to specifically tackle the complexities of software development, maintenance, change and evolution.
As an aside, it would also have been good to be apprised of C2's limitations in reusing code, earlier in the "game", so that I could have arrange game resources in a more favorable manner.
C2 is a fantastic environment, and I really want to use it for the current proof of concept and much beyond too, and I am looking much forward to see it become an even better tool.
</end of ramble>