Welcome Guest, Not a member yet? Register   Sign In
How the heck should I structure a HMVC project?
#1

[eluser]gunnarflax[/eluser]
Hi!

I'm trying to create a backend and a frontend for a HMVC project and this is my first time working with a HMVC structure. What feels most logical to me is to have the frontend controllers in the controller folder and the backend in the modules folder.

Code:
-- application
---- models
---- views
---- controllers
---- modules
------ backend

Then it seems to me that it would be best to have all backend-related modules in it's own module directory within the backend module, but I don't even know if it's possible to nest modules.

If I don't have it like above how shall I build it? Should I have only one controller in the backend module which handles all the navigation and "puttogetherness" of all the other modules? Should the frontend utilize the same modules as the backend so I wouldn't really need to nest modules?

As you can see I have absolutely no idea how to do this. Please come with suggestions Smile


Messages In This Thread
How the heck should I structure a HMVC project? - by El Forum - 08-12-2011, 07:53 AM
How the heck should I structure a HMVC project? - by El Forum - 08-12-2011, 11:42 AM
How the heck should I structure a HMVC project? - by El Forum - 08-12-2011, 11:47 AM
How the heck should I structure a HMVC project? - by El Forum - 08-14-2011, 11:39 AM



Theme © iAndrew 2016 - Forum software by © MyBB