JavaScript for Line of Business Applications

I will question the usefulness of MVC (MVC as in todays MV* implementations in JS frontend frameworks), the most established design pattern in frontend development. Let me make it clear that it is not my intention to invalidate MVC in general. Rather, I think it's importance as a design pattern for very interactive web applications is overstated.

This post here is ballsy, since MVC is baked into the heads of frontend people. It's ubiquitous. It's the biggest consensus amongst devs I've ever seen, and MVC is widely considered "best practice". Basically, people don't question MVC anymore. However, I personally think the concept doesn't apply optimally to complex web apps (I might be wrong though).

Lets learn about emberjs together on your way to building ambitious web applications. I aim to make the videos very short and concise so you get to learn a new thing each time.

IMVVM is designed to complement the React library. A Facebook and Instagram collaboration.

To further quote the React website, "lots of people use React as the 'V' in MVC". Well I thought, why not use React as the 'V' in MVVM, and keeping inline with React's philosophy on immutability, lets make it use immutable data. So I created IMVVM.

This is my take on MVVM and immutability using javascript. IMVVM tries to resemble a React application. So it not only feels like your developing in the same environment, but if your coming from React, you should be able to pick up IMVVM quickly.

Functional Programming is great. It allows for simpler programs which are easy to test and reason about. Unfortunately, not all languages are created equal. I've been writing a bit of Clojure and really enjoying myself. As I've ported my learnings and approaches to Javascript, I've encountered a handful of issues which I'd like to talk about.

Once you begin working with functions, you'll begin passing references of them to other functions. These are called Higher Order Functions and you may already be familiar with them. Take, for example, jQuery.fn.each:...

A demo of a directive which add a fancy search bar to filter data. It can filter / search from promises sources and preloaded sources. For the promises demo, I used Web SQL, so it's Chrome/Safari only compatible (but 100% compatible with the SQLite Cordova plugin :D)

AngularJS is turning out to be one of the best frameworks for building mobile apps across all major platforms.

One reason that Angular fits so well into the mobile developer toolbox is its features for interacting with backend web services and external data sources. Since most apps today are data-driven, it makes sense to use a tool built from the ground up to solve this problem.

Beyond that, AngularJS comes with some of the most modern and advanced software development practices ready-made and easy to use. You'll find that building mobile apps with Angular is highly efficient and results in solid code that will scale up as you pile on the features.

* Three-way data binding

* Reusable logic

* Testability

* Among Friends

* Mobile UI with Ionic

* Go forth and build

Enter Duck Angular: a framework specifically designed to help JavaScript developers test DOM interactions when working with AngularJS in a nearly immediate feedback loop at dev time.

Seven Reasons to Love The Duck
* It runs insanely quickly inside of KarmaJS, allowing development time fast feedback on JavaScript changes. The team’s test suite runs ~ 600 tests in around 50 seconds (and could be faster with some easy optimization)
* Binds your apps HTML templates (or just HTML files) with your controller and renders the result
* Duck is barely any code at all (293 lines), as it leverages Angular’s internals to provide a full-fledged DOM in your tests so that you can make assertions about DOM interaction
* It’s open source and available on GitHub at https://github.com/asengupta/duck-angular
* Works with Jamsine, mocha, Karma, phantomJS, RequireJS, chai, many of the “as promised” libraries, and much more.
* Allows you to flexibly inject your own dependencies, mocked or otherwise
* You can simulate user interactions with a handy helper function interactWith that can specify an element to interact with and a specific interaction

In the following tutorial we’ll create a simple Ember.js app for logging your water intake. Besides learning the basics of Ember.js, you will also learn how to use Ember App Kit.

EAK is the basic building block of your app. It helps you to rapidly start the development with features such as the ES6 module transpiler, automatic reloading, the Grunt task runner, the Bower package manager…

Sometimes programming is just using the right tool. This may be a framework, library or as it happens in my case CSS preprocessor. You probably don't realize it, but LESS or SASS have a lot of constraints. I managed to change that by writing my own CSS preprocessor. I stopped writing CSS and moved everything into the JavaScript world. This article is about AbsurdJS: a small Node.js module, which changed my workflow completely.

If you write a lot of CSS you probably use preprocessor. There are two popular - LESS and SASS. Both tools accept something, which looks like CSS, do some magic and export normal, pure CSS. What I did is just to replace the instrument and the input format. I didn't want to invent a new language or syntax, because this is connected with a lot of things like parsing and compiling. Thankfully, Node.js is here and I decided to use it. Also, I had a lot of LESS type projects, which means that I already use Node.js to compile my styles. It was much easier to replace a module instead of adding something completely new.

The idea is to dynamically generate a tabbed navigation using Angular and UI Bootstrap.

I’ve done this before, but this time around I needed the ability to deep link into a tab. That is, if a user bookmarks /someapp/tab2, then the 2nd tab should be active with its content showing.

Instead of using ngRouter, which is a bit simplistic, I decided to use UI Router. UI Router is not without quirks and bugs, but it does give the opportunity to setup multiple, named “states” for an application, and can manage nested states and routes through associated URLs. One of the first steps in working with UI Router is configuring the known states