MVVM pattern for javascript

[GoogleCodeExporter]

Software and Version
********************
KnockoutJS v 2.1.0

Reason for change
*****************
- With a MVVM pattern we will be able to separate the client logic from the 
User Interface design in an easy way.

This makes it easier to:
1) Test the client logic
2) Update the user-interface layout without affecting the client logic.
- "what´s the business case ?" - is it worth the investment?

Impacts
*******
- License cost
None

- Education
See www.knockoutjs.com for great tutorials.

- Migration / adaption of existing software
Medium work to re-write existing client scripts/web pages.

- Risks
Not possible to determine.

Does this replace some existing, already approved, software
***********************************************************
No approved framework for MVVM exists.

Earlier experiences of the suggested software
*********************************************
I have been working with knockoutjs for a year and it works great.

Original issue reported on code.google.com by rickard....@gmail.com on 10 Sep 2012 at 4:08

[GoogleCodeExporter]

In respect to our guidelines we decline this request.
http://code.google.com/p/oppna-program/wiki/Governance#Guidelines

We take this decision in respect to used technologies in other projects. 

Use the recommended Javascript framework JQuery

Original comment by Hans.Gyl...@gmail.com on 11 Sep 2012 at 10:13

• Changed state: Declined

[GoogleCodeExporter]

We will give answers to your guidelines below to try to convince the board that 
knockoutjs is a complement to existing technologies, and is based on approved 
VGR technologies (JQuery).

Please visit http://en.wikipedia.org/wiki/Model_View_ViewModel which summaries 
quite a lot.

Guidelines
When approving changes to selected frameworks and technologies (new or 
upgrades) the following aspects are taken into consideration:

Well established and proven technology
-It is well established the pattern itself was introduced 21 november 2006 by 
Microsoft in its .NET 3.0 release.  

Easy to recruit developers with solid experience of the technology
- It is easy, if you recruit a developer with javascript skills. The 
encapsulation and implementation of the MVVM pattern is based on JQuery itself.

"Average programmer complexity" - easy to adapt and learn
Visit www.knockoutjs.com and browse through the tutorial. It is easy to bind 
elements to viewmodels data. There is no competition in JQuery itself without 
building widgets for controlling the data.

Expected long term durability
MVVM pattern has been on the market since 2006 and still growing in popularity. 
It is expected to have a long term durability.

Avoid overlapping / redundant technology compared to what is already approved 
within oppna-program
-Well you don't have a compititor - JQuery itself wont solve this without much 
more code - please show us an implementation based soley on JQuery that is as 
slick as knockoutjs. 

The technology must support good software engineering practices
- It does. MVVM pattern is good software engineering practices, at least up to 
what I know, please give us some more information about what you don't see as 
good software engineering practices in knockoutjs.

Testability (out of container driven tests e.g. using jUnit)
- That's one of the major benifits of using knockoutjs. We will be able to 
isolate the clientscript from the view, and thereby being able to test the 
javascript easily.

Dependency management (e.g. support for maven dependency management)
- We don't use Maven on .NET platform, nor is it specified in the guidelines 
for .NET at VGR.

Continuous integration (e.g. solutions based on the technology must be possible 
to build using Jenkins)
- N/A , .NET will be build with tfs build agents, and all the clientscripts 
will be included in the build. 

Original comment by rickard....@gmail.com on 11 Sep 2012 at 10:35