JavaScript for Line of Business Applications

IMVVM is designed to complement the React library. A Facebook and Instagram collaboration.

To further quote the React website, "lots of people use React as the 'V' in MVC". Well I thought, why not use React as the 'V' in MVVM, and keeping inline with React's philosophy on immutability, lets make it use immutable data. So I created IMVVM.

This is my take on MVVM and immutability using javascript. IMVVM tries to resemble a React application. So it not only feels like your developing in the same environment, but if your coming from React, you should be able to pick up IMVVM quickly.

How difficult is it to port Silverlight applications to HTML5? That is the question we hear every day at ComponentOne. Instead of speculating about it, we decided to sit down and try it. Today we will discuss the process and tools we used when doing so. The approach we took was to use the MVVM pattern (from Silverlight) when developing the HTML5/JavaScript version. By choosing this method we were able to port our data access and UI layers quite easily. We take advantage of tools like KnockoutJS and Wijmo to make the process even easier. Our developers were able to minimize the cost of learning new paradigms in this migration by reusing most of their knowledge. What we ended up with was nearly identical applications in Silverlight and HTML5. Come learn how you can smoothly transition to HTML5!

I have been looking into various design patterns and trying to architect client side applications using it. More often than not the MVC pattern fits the requirement in most of the applications. However, I have found myself using MVVM (Model View - View Model) pattern along with MVC. I use MVVM pattern particularly when I have to maintain the state of the model on the client side. AngularJS provides great support by allowing you to extend the markup and tying the model right within the view (the markup). It also provides components that can be used to structure the application the MVC way and hence it's appropriately termed as MVW or MV* framework. However, I use BackboneJS in most of my applications and I have been able to maintain the state of the model using the Backbone.Stickit plugin.

SUSE Studio has evolved a number of methods for performing dynamic client updates; in some places, we use Rails 2.0-style RJS - sending rendered partials along with JS code to be executed by the client. In other places, we're sending JSON data, and handling it via custom-written interactions. Most recently, we've experimented with client-side rendering of Mustache templates. None of these approaches is particularly robust or maintainable, and as a result we've ended up with a huge amount of fragile client-side code.
Luckily, we're not the only developers in this situation - every major web application faces the same challenges. As a result, a number of client-side frameworks have developed, applying common design patterns to build up a logical, maintainable framework for managing client-state and server interactions for web development. The problem is that everyone seems to have a solution, and that means navigating a number of projects to find a good fit.

In today's second Web Wednesday post (the post earlier today was actually last Wednesday's post, but I forgot to actually schedule it for publishing... Doh! So you guys get two posts today!

Almost everyone dealing with web technologies knows jQuery, or has heard of it, and while powerful it is not ideal for building Rich Internet Applications. And this is where Knockout.js shines through.

A Beginners Guide to KnockoutJS: Bindings Knockout provides a whole set of useful built-in bindings for the most common tasks and scenarios. Each of these bindings allows you to bind simple data...

A Beginners Guide to KnockoutJS: Templating and More There are four control-flow bindings: foreach, if, ifnot and with. These control bindings allow you to declaratively define the control-flow logic...