JavaScript for Line of Business Applications

Yes, you can create sound in JavaScript – at least, in some browsers.

So for now, playing with creating sound in JavaScript should be considered something experimental but it is definitely fun to play with, just not for your super, awesome, must-work-in-every-browser game.

I found several sites that had build up complex libraries based on the Web Audio API. These weren’t the greatest things to learn the basics from, but I eventually was able to pare some of the code down to the bare minimum needed to create sounds in the browser. 

There are a few tutorials linked to from there as well, but none really covered what I was interested in, which is why I created this tutorial.

So, to get down to it, let’s create some noise.

A YouTube playlist on concepts like Monads and Buritos.

With JavaScript approaching near-ubiquity as the scripting language of the web browser, it benefits you to have a basic understanding of its event-driven interaction model and how it differs from the request-response model typically found in languages like Ruby, Python, and Java. In this post, I’ll explain some core concepts of the JavaScript concurrency model, including its event loop and message queue in hopes of improving your understanding of a language you’re probably already writing but perhaps don’t fully understand.

This post is aimed at web developers who are working with (or planning to work with) JavaScript in either the client or the server. If you’re already well-versed in event loops then much of this article will be familiar to you. For those of you who aren’t, I hope to provide you with a basic understanding such that you can better reason about the code you’re reading and writing day-to-day.

In this hands-on lab you will learn how to build a simple multiple view Single Page Application (SPA).

You will start by building a simple html page and add jQuery, RequireJS to make it dynamic. Then you will add Durandal and Knockout to extend the single html page into a SPA that has a shell and two additional views and a navigation menu to navigate between the two.

 this hands-on lab, you will learn:

In this post I’m going to provide an overview about how the application is organized, back-end options that are available, and some of the features it demonstrates. 

The Customer Manager application certainly doesn’t cover every feature provided by AngularJS (as mentioned the intent was to keep it as simple as possible) but does provide insight into several key areas. Here are a few of the features it demonstrates with information about the files to look at if you want more details:

* Using factories and services as re-useable data services (see the app/services folder)
* Creating custom directives (see the app/directives folder)
* Custom paging (see app/views/customers/customers.html and app/controllers/customers/customersController.js)
* Custom filters (see app/filters)
* Showing custom modal dialogs with a re-useable service (see app/services/modalService.js)
* Making Ajax calls using a factory (see app/services/customersService.js)
* Using Breeze to retrieve and work with data (see app/services/customersBreezeService.js). Switch the application to use the Breeze factory by opening app/services.config.js and changing the useBreeze property to true.
* Intercepting HTTP requests to display a custom overlay during Ajax calls (see app/directives/wcOverlay.js)
* Custom animations using the GreenSock library (see app/animations/listAnimations.js)
* Creating custom AngularJS animations using CSS (see Content/animations.css)
* JavaScript patterns for defining controllers, services/factories, directives, filters, and more (see any JavaScript file in the app folder)
* Card View and List View display of data (see app/views/customers/customers.html and app/controllers/customers/customersController.js)
* Using AngularJS validation functionality (see app/views/customerEdit.html, app/controllers/customerEditController.js, and app/directives/wcUnique.js)
* Nesting controllers
* More…

Google is in process of replacing JavaScript with Google Dart. Stating Dart is technically superior to Java Script. But having said that Dart is having some fundamental issues to look at. What will Google now do?

This book is not designed to teach you JavaScript, but it does recognize that you are likely to have taught yourself JavaScript and that there are some key concepts that you may have missed along the way. This section is particularly important if your primary language is Java as the syntactic similarities between Java and JavaScript belie the differences in their respective designs.

Table of contents:
* JavaScript Objects are Associative Arrays whose Keys are Always Strings
* There are Several Ways to Look Up a Value in an Object
* Single-quoted Strings and Double-quoted Strings are Equivalent
* There are Several Ways to Define an Object Literal
* The "prototype" Property is Not the Prototype You are Looking For
* The Syntax for Defining a Function is Significant
* What "this" Refers to When a Function is Called
* The "var" Keyword is Significant
* Block Scope is Meaningless

In this post I'm going to attempt to explain what exactly generators are and why their addition is such a big deal in JavaScript (and more particularly, Node). 

While generators themselves aren't overly complex, some of the concepts relevant to them aren't exactly common knowledge, so bear with me while we set some context.