Taking JavaScript “all the way” with MVC

In: web resources

21 Aug 2009

Peter Michaux posted about going all the way with a full client-server app view that looks like:

HTML:

  1.  
  2. <!DOCTYPE html>
  3.   <title>The App</title>
  4. </head>
  5.   <script src=“/static/js/the-app/bootstrap.js” type=“text/javascript”></script>
  6. </body>
  7. </html>
  8.  

Joel Webber then showed what the GWT Showcase example could look like (a touch different):

HTML:

  1.  
  2. <!DOCTYPE><html><body><script src=‘gwtShowcase/gwtShowcase.nocache.js’></script></body></html>
  3.  

This isn’t new but feels like it continues to gain ground. Bespin is pretty much this model….. the editor talks to a simple JSON API on the backend. Mobile Me uses SproutCore which touts this model. As do many other frameworks.

Jonathan Snook posted about JavaScript MVC at the same time. He sets up a mini-manual framework himself to show some concepts, and Kris Zyp comments:

It misses the strong MVC design in Dojo, YUI, ExtJS, etc. because MVC is not in name)

MVC is one of those patterns that wars are started on. Some think of it as broad, others jump back to the smalltalk roots and look to specifics.

If you think that view source / semantic markup is a great feature of the Web platform, then this kind of world is a touch worrying, but major apps have been doing this for years.

Comment Form

About this blog

This blog delivers stylish and dynamic news for designers and web-developers on all subjects of design, ranging from: CSS, Ajax, Javascript, web design, graphics, typography, advertising & much more. Our goal is to help you communicate effectively on the web with an engaging website or functional interface.