cabbagehead - 1:28 am on Dec 16, 2007 (gmt 0)

After reviewing a few JavaScript libraries for AJAX development, I've quickly come to realize the event model seems to imply use of the MVC pattern for development. Assuming you accept this premise, the next question is how to best implement this pattern.

Here are my thoughts and I'd appreciate any feedback/debate you might want to throw into the mix:

1. Model - pure domain-model Javascript objects that deal with the actual behaviors to be invoked.

1. View - a pure DOM (zero CSS or Javascript or styling info; purely a div-centric DOM definition.

2. Controller - Observer pattern implementation around the idea of even registration and listeners that observe those events.

So something I'm wonder is - should the controller code be in a seperate JS include from the model code for that "Page"? I could see where one could say that either (a) the controller code is the one set of javascript code that *does* belong in a script tag in the head of the DOM and acts to connect the DOM to the model objects. Or (b) that it belongs in its own events class, in a seperate file.

Any thoughts, suggestions, opinions, etc?

Thanks.
N