I have an application that is growing more and more. The address is: www.aquitanda.com [Brazilian Portuguese].
Basically, this is a website where you can buy and sell things yourself, which means that people can create their own online stores.
I have four large “interfaces” for this project. One of them is the commom interface, where everyone can view the browser, register as a user or as a store, and so on. I have another interface where people manage their settings, their profile, etc., This is the user interface. There is a store management interface where people add products, categories, check orders and so on. The latter is a store interface.
This means that I have a lot of code that uses the same models and the same controllers, but my controllers are getting huge, and the maintanence is getting harder and harder to do.
See, I have fat models. This is not because actions get to a lot of code. This is simply because I have a lot of activities.
So, I moved my code to plugins, but this no longer seems “right” to me, since I want to use plugins for other things instead of actions with interfaces.
Is there any suggestion to organize this better? Should I use prefixes and let my controllers huge? Should I stick with plugins [possibly with custom paths]? Will v.1.3 introduce anything new on this issue? Should I wait for a stable version? Any other alternatives?
Thanks;)