[eluser]jwright[/eluser]
Just to clarify, I have got Doctrine working within a module using wiredesignz Modular Separation code and I don't think I'd have a problem getting it working with his HMVC code either (since it's from the same codebase according to wiredesignz).
I'm trying to figure out the best application architecture using these two. I'd like to achieve a few features...
- one Doctrine installation powering multiple modules
- ability to use the migrations feature of Doctrine (in/with multiple modules)
- each module can load other modules and there can be module dependencies (meaning modules depending on other modules)
- the above while maintaining the modularity of the modules, meaning that we can still copy a module folder into the modules folder of any HMVC/Doctrine/CI install and it can work with little or no configuration of the module
I know this is all a bit fuzzy and incomplete talking about it without concrete examples. Articulating it in this post has helped me see a little clearer how it might all fit together.
Hopefully I can put something together soon and share it for review and improvement/alternative suggestions.
