Commit ace32f95 authored by addyosmani's avatar addyosmani

updating readme

parent 30fe8316
#TodoMVC - A Common Demo Application For Popular MVC Frameworks
#TodoMVC - A Common Demo Application For Popular MVC Frameworks (0.1 pre)
Over the past year, we've seen interest in lightweight JavaScript MVC frameworks continue
to increase steadily. Backbone, Spine, SproutCore 2.0, YUILibrary, JavaScriptMVC...
......@@ -16,19 +16,23 @@ compared.
You may know that many frameworks now come with their own variation of the 'Todo' example.
It's a simple demo that illustrates how models, views and controllers may be used to write
a completely functional list-based application. Whilst many frameworks do attempt to include
a version of the 'Todo' example, there are some problems here:
a completely functional list-based application.
Implementations are inconsistent - there's no standard or specification around how the Todo
application should be written - indeed, some may ask if a demo app even needs one. Regardless,
This is why although some frameworks will implement the example with similar features and
a look/feel consistent with their peers, others will stray away from this quite heavily. This
is an issue because if you're attempting to directly compare how one framework might achieve
a task vs another, very disparate implementations make this significantly more difficult to do.
#Whilst many frameworks attempt to include a version of the 'Todo' example, there are issues here:
Some developers may claim that it's merely just adding or removing items from a list, there's not much more to it, is there?. When you actually delve into framework demos you might be surprised at just how much they can actually differ. Some solutions will opt for a completely different MVC structure to the application, others will opt for JavaScript templating to insert new items whilst some will prefer cloning HTML markup to insert new 'rows' instead. Again, the lack of what we consider a consistent experience causes problems here.
#Implementations are inconsistent
There's no standard or specification around how the Todo application should be written - indeed, some may ask if a demo app even needs one.
Lack of a Todo example altogether - I can't speak for all developers, but after reviewing the feature list on such solutions, my first port of call is usually to look for their Todo app as I find this the quickest way to determine whether I'm going to like using their brand of MVC for structuring my apps. This isn't in any way stating an incapability of determining this from code samples in a frameworks docs, but rather, I prefer to review differences in a complete application. I know that other developers feel the same about this too.
When you actually delve into framework demos you might be surprised at just how much they can actually differ. Some solutions will opt for a completely different MVC structure to the application, others will opt for JavaScript templating to insert new items whilst some will prefer cloning HTML markup to insert new 'rows' instead. Again, the lack of what we consider a consistent experience causes problems here.
Regardless, this is why although some frameworks will implement the example with similar features and a look/feel consistent with their peers, others will stray away from this quite heavily.
#This is an issue because if you're attempting to directly compare how one framework might achieve a task vs another, very disparate implementations make this significantly more difficult to do.
#Lack of a Todo example altogether
I can't speak for all developers, but after reviewing the feature list on such solutions, my first port of call is usually to look for their Todo app as I find this the quickest way to determine whether I'm going to like using their brand of MVC for structuring my apps. This isn't in any way stating an incapability of determining this from code samples in a frameworks docs, but rather, I prefer to review differences in a complete application. I know that other developers feel the same about this too.
So, I had an idea (which you may or may not find useful):
Why not create a centralized fork of the various framework Todo examples,
......@@ -49,8 +53,6 @@ which include:
<li>KnockoutJS (MVVM)</li>
</ul>
####Code samples:
***coming soon
####Screenshots:
**coming soon
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment