CorMVC is a jQuery-powered Model-View-Controller (MVC) framework that can aide in the development of single-page jQuery applications. It evolved out of my recent presentation, Building Single-Page Applications Using jQuery And ColdFusion, and will continue to evolve as I think more deeply about this type of application architecture.
CorMVC stands for: Client-Only-Required Model-View-Controller, and is my laboratory experiment in application architecture held completely seperate from server-side technologies.
Building frameworks in jQuery (or any other language for that matter) is very new to me; I don't claim to be any good at it. In fact, when I started looking into jQuery-based frameworks, I had no intention of creating my own. As I started to do my research, however, I quickly encountered two major problems with what was avilable:
I didn't even know how to begin learning. So, rather than wade through what was available, I decided to try and create something from scratch. What I came up with is corMVC. The philosophies that I put into the corMVC framework are those that were hopefully a remedy to the problems I encoutered above:
While I want to keep the corMVC framework as small as possible, I am sure that as I begin to more fully understand the various needs of single-page applications, the framework will have to evolve as necessary. In the end though, I want the corMVC framework to be an aide and not a constraint- affording the programmer the freedom to pile their own jQuery magic on top of this foundation.
When dealing with Javascript and "progressive enhancement enthusiast," someone always asks how this should work / degrade if the end user does not have Javascript enabled. While this might be a contentious answer, if your target user does not have Javascript enabled, then I don't think they should be using a single-page application. That's like asking how a user should navigate a FLEX application if they don't have Flash installed; it doesn't make sense. I'm not talking about building "pamphlet" sites here - I'm talking about building complex, user-experience-oriented applications.
The contacts section is meant to demonstrate more complex interactions that involve the application's service layer (part of the Model) and potentially (thought not required in this demo) communication with the server.
Please fill out the contact information below.
This is the documentation page.
Coming soon....
This is the resources page.
Coming soon....
Sorry, but the page you requested could not be found.
Try going back to the home page.