Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
I have to admit I was extremely skeptical when I first saw the concept of creating a view model in a browser. As much as I loved XAML’s data-binding it felt like a square peg and a round hole. What really concerned me the most was the extra work involved to take an ordinary JavaScript object (JSON) and turn it into a view model using things like ko.observable. This has been vastly improved and simplified, and as I began to adopt the strategy for the web I realized quickly it made sense. 
No comment yet.
Sign up to comment
Scoop.it!
While the allure of writing applications - and not just web sites - in HTML5 and JavaScript reaches a lot of developers, we've experienced that a number of developers are rather frightened by the idea of creating large applications in a dynamic language. In addition to the dynamic nature of JavaScript, the lack of a container-based GUI framework (which isolates causes and effects to individual controls, as it is done in the .NET Framework) and the general overarching flexibility and lack of guiding principles didn't make this environment too appealing for a lot of business developers. We think that AngularJS can change this and we'd like to present a small sample of AngularJS code, the underlying markup and the resulting mini-application. (We're not going to talk too much about the individual steps in this sample, as this would be the focus of the next chapter.)
|
Scoop.it!
This is a series of posts about AngularJS and our experiences with it while migrating the client of a complex enterprise application from Silverlight to HTML5/CSS/JavaScript using AngularJS as a framework. So far I have published the following posts: * AngularJS, Part 1
|
