Geek Answers Handbook

ExtJS Architect: is it wise to split a large application into several projects?

I am starting to build a rather large application in ExtJS Architect, and I was wondering if it would be advisable to split the application into several projects (more precisely, projects, since Architect defines a project)?

I am currently the only engineer working on this application, but more engineers can be appointed in the future. What would be the questions if you would like to divide a project into small pieces or build one large project?

In addition: as far as I know, it is impossible to "share" a project in the Architect with more than one developer. It votes on the split of the project.

+4
source share
1 answer

Disclaimer: I did not use Architect to create the project. My idea is that if you are building an MVC project and want the architect to manage your controllers and views, you should keep everything together. Especially if you have cross-connectivity between modules. However, if you are 100% sure that your modules are completely autonomous, which means that they have nothing to do with each other and can be separate applications ... (maybe they should?) ... then you could to create them separately and weave them together, after you want to pierce the architect. Remember its one-way street, not the IDE. Combining modules should only mean that app.js now lists all your controllers for all modules, not just your module.

+1
source

More articles:


All Articles