Hopefully everyone had a good few days off. Before the holiday break, I did some app-building on top of the ASP.NET MVC framework. Actually rather than building some sort of fancy app, instead I was prototyping some features on top of the framework bits slated for an initial release. I've shared out the sample code, sample app and tests - yes, sorry for another tease :-)... but stay tuned... and you'll soon have actual bits to play with as well. Until then, you can download the sample code and browse it locally, and follow along the rest of the post. In particular there are two projects within the solution: TaskList (the web app) and AjaxMVC (a class library with Ajax extensions).
One of the prototypes is around bringing some basic Ajax functionality - basically to get post-back-less partial rendering and some behavior-like extensions to associate with DOM elements - sort of like ASP.NET Ajax but in a manner that fits with the pattern around how controllers and views are written. I should say that eventually Ajax functionality will exist out-of-the-box, so you can think of this as an early experiment, and by no means complete. In the spirit of experimentation, feedback and suggestions are welcome.
A Super-simple Task List Application
I know, the task list application has been beaten to death, but it’s a simple enough that it allows focusing on the Ajax features. Below is the screen-shot of the application that you get when browsing /TaskList on the site.
For a great intro to MVC, to get a sense of what is involved, the application structure etc, check out Scott's intro post if you haven't already done so. I won't repeat that material here, but like Scott's product catalog application, the TaskList application has a controller to handle the incoming requests, a set of classes making up the model representing a collection of task items, and a set of views used to render the user interface.
I'll point out some basic aspects of the application as it exists before I start adding some Ajax functionality.
One of the prototypes is around bringing some basic Ajax functionality - basically to get post-back-less partial rendering and some behavior-like extensions to associate with DOM elements - sort of like ASP.NET Ajax but in a manner that fits with the pattern around how controllers and views are written. I should say that eventually Ajax functionality will exist out-of-the-box, so you can think of this as an early experiment, and by no means complete. In the spirit of experimentation, feedback and suggestions are welcome.
A Super-simple Task List Application
I know, the task list application has been beaten to death, but it’s a simple enough that it allows focusing on the Ajax features. Below is the screen-shot of the application that you get when browsing /TaskList on the site.
For a great intro to MVC, to get a sense of what is involved, the application structure etc, check out Scott's intro post if you haven't already done so. I won't repeat that material here, but like Scott's product catalog application, the TaskList application has a controller to handle the incoming requests, a set of classes making up the model representing a collection of task items, and a set of views used to render the user interface.
I'll point out some basic aspects of the application as it exists before I start adding some Ajax functionality.
Comments