> On the client though, I find that what we do is slightly different. I like > to think of each of my widgets as a micro-MVC, and my main.js file as a > bootstrap.
That's quite what I do too, my files are organized by widget in the first level, then in each widget directory there are the controller, the view and the model when needed. When I speak about mvc, it's not about creating a Model class, a Controller class and a View class from which each other classes will inherit, but mostly to seperate a widget in those three kinds of classes. > The closest thing to a domain controller that I can think of is a Domain > Dispatcher/Observer object, which delegates costume events between separate > Classes. Again - this is a very generic operation with Events, which is a > very important piece in what make Mootools such a strong development > platform. Totally agree, this would make not much sense in a widget seperated design. Still, clearly separating the event related code from a widget in seperated classes/files can help building more maintainable apps, don't you think so? -- Olivier El Mekki.
