3 ms·

I'm always excited to structure my projects in a different more effective way - well, it's more of a struggle - anyway, this sounds interesting. Can someone ela

by babby 13y ago

I'm always excited to structure my projects in a different more effective way - well, it's more of a struggle - anyway, this sounds interesting. Can someone elaborate on the file structure and structure of files and the way they connect? I'm rolling with a MVP structure that frankly is becoming cumbersome with my current project's size.

tegeek 13y ago
What I've done myself and found it pretty scalable is as follows: appShell/ views/allbaseviewshere viewmodels/controllers or viewmodels for the core views services/baseservices moduels/ account /views/ /viewmodels/ /services/ order /views/ /viewmodels/ /services/ /controllers/ static /css/ /js/ /images/ AppShell contains the app starter page, controllers and util services (showing popups, utility functions etc.) AppShell/Views contains all the UI Skelton for the app (bootstrap main page, etc) Every folder inside "modules" contains views, controllers (viewmodels) and services belongs to only that module. Account folder contains views for user registeration, sign in, change user profile, etc. etc. This way you can keep building new moduels in their respective folders without touching the frozen code (already built modules). Each module talk to outside world using "services". No module can touch anything belongs to other modules but with "services".