JavaScript for Line of Business Applications

Angular, a super heroic MVC framework, and Polymer, polyfills and enhancements for custom elements built on top of Web Components, can live harmoniously in the same app. This post shows you how to connect Angular-controlled components to Polymer-controlled elements via data binding. And we do it all in Dart.

There are some similar features between the two libraries. Both libraries implement a data binding solution (which we cover below). Angular is beginning to build on top of emerging web standards (like Shadow DOM). I expect that, over time, more and more of Angular will take advantage of the Web Components family of specifications.

We can interop Angular and Polymer via the DOM, as well as via data binding.

With testium you can write integration tests that:
* use a familiar BDD syntax
* are written in CoffeeScript/JavaScript
* have a synchronous API
* can leverage Selenium

Why Create a New Tool?
Since the beginning of our transition to Node.js, we have been looking for a great way to include integration testing in our Node.js applications. In Ruby on Rails, we had a Cucumber setup that could run tests in real browsers via Selenium. The relationship with testing tools was not strongly defined for Node.js (the platform) or even Express (the underlying framework).
That lead us to look for other existing tools we could adopt. We tried a couple of tools, but they just didn’t fit our needs for different reasons.

A tutorial on getting started with building Windows Store apps using TypeScript. It shows you how to use frameworks you already know, like jQuery and Knockout.

In this tutorial we’re going to build a very simple Windows Store application that uses jQuery and Knockout to get some data from the internet and show this in a GridView. I’ll show you how you create a new project, get all the the TypeScript definitions you need, get data from a web service and bind that to the GridView control. I’m assuming you have at least a little TypeScript knowledge. 

If you've ever tried connecting to MS SQL Server from Node.js, then you know that the modules currently available are incomplete and immature. Microsoft released an official SQL Server driver. However, it is still "preview" technology with a number of missing features and outstanding issues that haven't been addressed since its release.

One compelling alternative I have discovered is Edge.js. Edge.js is a Node.js module that allows .NET code and assemblies to run in the same process with Node.js. This potentially enables a Node.js developer to leverage technologies that have traditionally been very hard or impossible to use in the past. For example:
* SQL Server
* Active Directory
* Nuget packages (currently 18K+ packages available)
* PC or Server hardware (e.g. webcam, microphone, and printers)
* Legacy .NET code

The number one question I see over and over with programmers new to angular is “how do I organize my code?”. I think that this is because the way you organize sample code is completely different than simple code, which again, is totally different than a complex application, and those transitions are not self-evident.

* Sample Code - aka One Big File
* Simple App - aka The Angular-Seed Method
* Splitting your application up into modules
* Angular and Require.js
* Choosing what is right for your project

Awesome, It Works!
RequireJS Is The Best

Please Tell Me More About AMD

Is That It?
Nope, There Are Many Ways To Define an AMD Module

Check Out More Module Definitions

Free web application framework for building Web sites and Web applications using JavaScript, HTML and CSS.

Helping you select a cross-platform mobile framework - Apps using jQuery Mobile, Sencha Touch, Titanium and more

Some of the frameworks deliver a native user interface, whereas others construct a native-like interface using HTML5 technologies. When selecting a framework it is important to test the end-user experience that the framework delivers and ensure you are happy with any compromises.

The code-sharing which can be realistically achieved with each framework varies considerably. To aid in this comparison there is a build script which produces code metrics for guidance. Although, as developers I am sure you are aware that lines-of-code metrics are flawed.

It is also worth investing quite a bit of time familiarising yourself with tools provided by each framework. The cost and quality of these varies considerably.

Sigma is a JavaScript library dedicated to graph drawing. It makes easy to publish networks on Web pages, and allows developers to integrate network exploration in rich Web applications.

Sigma provides a lot of built-in features, such as Canvas and WebGL renderers or mouse and touch support, to make networks manipulation on Web pages smooth and fast for the user.

Sigma provides a lot of different settings to make it easy to customize how to draw and interact with networks. And you can also directly add your own functions to your scripts to render nodes and edges the exact way you want.

Almost every day, we see new libraries, frameworks and tools being released in the JavaScript community - many of which simply reinvent the wheel.

This regular stream of solutions, which opt to create something new rather than improve an existing solution is what we at TodoMVC refer to as ‘Yet Another Framework Syndrome’ - or in more general terms NIH (Not Invented Here). Whilst innovation is something we should all welcome, YAFS can lead to confusion and frustration for users because there’s a big risk of it introducing more noise than value. Just one example is MVC.

Developers often just want to start writing an app but don’t want to manually evaluate 300 different options in order to select something maintainable. There’s currently however almost too much choice when it comes to what to use for structuring your JavaScript application. Part of this problem is fueled by how different JavaScript developers interpret how a scalable JavaScript application should be organized — everyone feels their way is the best. As a community we seem to prefer creating our own silos over improving existing solutions.