The way I use my Views is that the HTML isn't already in the page. I don't really like leaving a skeleton of a popover box, and cloning it, then filling up various DOM nodes with information. Being able to insert easy to main HTML, with the ability to easily place various information, was my goal.
My usage is meant more for a web app, where its more forgivable to require JavaScript be enabled. On Wed, Nov 10, 2010 at 8:53 AM, Olivier El Mekki <[email protected]>wrote: > > 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. >
