JavaScript for Line of Business Applications

In this article, I’ll talk about the high-level technologies and pros and cons to go from a fully client-side to server-side rendered application with a supplementary Backbone.js app on top. This article draws on about a year of experience using both techniques on production apps at YouNow.

If you’ve ever built a fully client-side rendered app (I only have experience with Backbone.js), you are probably aware of its downfalls: slow loading/render times, and no useful search engine indexing of your pages.

Despite the downfalls, these apps are pretty straightforward to build...

This article shows Databinding and Templating using Knockout in the ASP.NET Web API. In this article we use the Knockout.js file. Knockout contains a JavaScript library and this library helps for creating a responsive display and editor user interface under laying of the data model.

Use the following procedure to create a sample.

Chained is an experiment and a prototype library for Javascript I developed in the past weeks. It is meant to show a concept and to provide some limited but useful functionality. All the examples below are written in Coffeescript (and I guess that this makes me a hippie, right?).

Chained allows to chain functions explicitly — both those that return promises and those who don’t — without using then-based constructs.

Mojo.js (alpha) is a JavaScript framework for building Single Page Applications, or static websites in Node.js. It's inspired by Angular.js, Derby.js, Knockout.js, Meteor.js, Ember.js, jQuery, Backbone.js, and many other JavaScript, and non-JavaScript frameworks. Much of the design was inspired by Backbone.js, and Node.js. The core is small, while third-party modules allow you to customize Mojo depending on your requirements. Mojo was built initially to phase out old code, and itself - hence the modularity. The philosophy behind Mojo is to allow you to build on top of your old code base, and slowly strangle out your old application until you have a new, highly maintainable application.

The goal of this blog post is to give you a brief introduction to Meteor which is a framework for building Single Page Apps. In this blog entry, I provide a walkthrough of building a simple Movie database app.

What is special about Meteor? Meteor has two jaw-dropping features:

* Live HTML

* Latency Compensation

The goal of this blog post was to provide you with a brief walk through of a simple Meteor app. I showed you how you can create a simple Movie Database app which enables you to display a list of movies and create new movies.

I also explained why it is important to remove the Meteor insecure package from a production app. I showed you how to use Meteor Methods to insert data into the database instead of doing it directly from the client.

I’m very impressed with the Meteor framework. The support for Live HTML and Latency Compensation are required features for many real world Single Page Apps but implementing these features by hand is not easy. Meteor makes it easy.

AngularJS is a sweet web app framework. It comes with decent official documentation and samples, it looks superior among a large number of frameworks in an almost-real-world application test (the famousTodoMVC project), and there are cool presentations and screencasts about it all over the web.

But for a developer who has not used frameworks similar to Angular before, and has mostly worked withJavaScript libraries like jQuery, there may be some difficulty in shifting from the jQuery mindset to the Angular mindset. At least there was for me, and I’d like to share some notes–maybe this will be useful to someone.

* Not a Library
* Declarative, rather than Imperative
* Two-way Data Binding
* Dependency Injection
* Data Access

I'm attending HTML5DevConf this week. During this conference, I attended a talk titled " JavaScript Insights " provided by Ariya Hidayat  of Sencha (a front-end component library provider) and Ann Robson of Yammer (an enterprise social network).

Their discussion was centered around how their two very different approaches to developing front-end software in JavaScript really had a centrifugal component of quality and confidence for their code being released into production.

They defined three (3) main topics which I had to share with our internal teams and I thought I'd share them with our Code@ community.

* Code Structure Validations

* Test Coverage of the Code

* Code Complexity Valuations

inputEx is an open-source javascript framework to build fields and forms for web applications using the YUI3 library.

Treema is a jQuery plugin that builds interfaces for editing large, complex, well-defined JSON data. It runs on tv4, which implementsJSON-Schema validation.

In today’s world of Javascript Application frameworks, design philosophy is the key differentiating factor. If you compare the popular JS frameworks, such as EmberJS, AngularJS, Backbone, Knockout, etc. you are sure to find differences in their abstractions, thinking models, and of course the terminology. This is a direct consequence of the underlying design philosophy. But, in principle, they all do one thing, which is to abstract out the DOM in such a way that you don’t deal directly with HTML Elements.

I personally think that a framework becomes interesting when it provides a set of abstractions that enable a different mode of thinking. In this aspect, react, the new JS framework from the folks at Facebook, will force you to rethink (to some extent) how you decompose the UI and interactions of your application. Having reached version 0.4.1 (as of this writing), React provides a surprisingly simple, yet effective model for building JS apps that mixes a delightful cocktail of a different kind.

In this article, we’ll explore the building blocks of React and embrace a style of thinking that may seem counter-intuitive on the first go. But, as the React docs say: “Give it Five Minutes” and then you will see how this approach will become more natural.