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!
Until recently, multiple vendors, including Microsoft, Adobe and Oracle/Sun, were competing to provide rich Internet application (RIA) frameworks for creating applications that could be delivered via the Web. However, this led to some fragmentation of the market. Some of the main challenges of these platforms included the need for special plug-ins, security risks and increased power requirements. HTML5 has emerged as a standard framework for providing most of the features and functionalities of these RIA frameworks. As a result, vendors like Microsoft have started investing more effort in supporting this vendor-neutral standard. Silverlight has not gone away, but Microsoft is investing more attention in this emerging Web standard, and has advocated various steps developers can take to transition their existing Silverlight applications to HTML5.
Scoop.it!
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!
Scoop.it!
Dataset is a JavaScript client-side data transformation and management library. Dataset makes managing client-side data easy by handling loading, parsing, sorting, querying & manipulating data from all sorts of sources. In addition to helping load and parse data, Dataset makes it easy to query and select subsets of data, creating "views" that automatically update when the underlying data changes. By binding to events, it's easy to create interfaces onto realtime or user-manipulated data. Dataset provides some standard computations such as min and max and derivatives such as groupings and moving averages.
|
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
Scoop.it!
The first installment discussed what Knockout.js is, why and how it evolved, and how it fits into Web development. This month, the discussion dives into best practices for Knockout, extending it and creating custom bindings. To get the most utility out of Knockout's components, the need for the Model-View-ViewModel (MVVM) design pattern must be understood. This architectural pattern arose out of Microsoft's implementation of Martin Fowler's presentation model design pattern to support Windows Presentation Foundation (WPF) and Silverlight.
Scoop.it!
This article compares Silverlight and KnockoutJS by looking at the implementation of the same application with both frameworks and tries to answer the all-important question "which framework is best?
Scoop.it!
Are you converting a .Net Application that heavily relies on Linq? This project might cure the pain of replacing it with "for" loops.
$linq is a Javascript version of .NET's Linq to Objects, with some query operations inspired by MoreLinq (an extension to Linq to Objects).
|
