JavaScript for Line of Business Applications
555.2K views | +35 today
Follow
JavaScript for Line of Business Applications
Keeping track of current JavaScript Frameworks that help design your clientside Business Logic Layers.
Curated by Jan Hesse
Beam to my Inbox:
Your new post is loading...
Your new post is loading...
Scoop.it!

Backbone vs. Knockout

Backbone vs. Knockout | JavaScript for Line of Business Applications | Scoop.it
If you are asking yourself, which Javascript framework should I use for my next application, then this is the article for you.
more...
No comment yet.
Scoop.it!

The Case For Marionette.js

The Case For Marionette.js | JavaScript for Line of Business Applications | Scoop.it

Building large web applications using Backbone.js can be hard. Backbone is a great tool, but it's designed to be minimalist and useful in a wide variety of situations. As a result, you get less guidance and support from the tool as you scale up than you do from more opinionated frameworks like Angular and Ember. When a Backbone application grows, maintaining it requires adding structure, either through a custom set of conventions and components, or based on somebody elses framework. There are a lot of different Backbone frameworks out there, but I want to make the case for using Marionette.js.

more...
No comment yet.
Scoop.it!

Which Javascript framework to use? Angular vs. Ember vs. Marionette

Which Javascript framework to use? Angular vs. Ember vs. Marionette | JavaScript for Line of Business Applications | Scoop.it

So you've got a new project you want to build and you're going to pick a front-end javascript framework. First make sure you absolutely need the single page application. Chances are you can do without it. However, let's say you want to do a lot of javascript client-side intensive stuff, then how should you decide what framework to use? I've been in this same scenario myself multiple times, so I decided to blog about it. I have a love-hate relationship with all 3 of these frameworks because I have used all of them on work and personal projects. I only focus on client side frameworks here, not server side, e.g. meteor, sailsjs, express. I only included the frameworks I have experience with.

more...
No comment yet.
Scoop.it!

Why I Chose Ember.js

I have finally made the plunge to really dig into Ember.js. But, if you are familiar with the vast landscape of Javascript frameworks, you may wonder why I chose Ember.js. This isn't a light decision and Ember.js is thought to have quite a steep learning curve. However, I think that there are some reasons behind this that I will cover in a later post.

So to start, let's look at the various frameworks and my own relations to them in my track to eventually set upon Ember.js.

more...
No comment yet.
Scoop.it!

Introducing Marionette-Require-Boilerplate for Your Single Page Application

Introducing Marionette-Require-Boilerplate for Your Single Page Application | JavaScript for Line of Business Applications | Scoop.it

Marionette-Require-Boilerplate (MRB) is a simple boilerplate I created to help get Single Page Applications off the ground with a small starter project. It incorporates a number of great tools and best practices to save time in the early stages of a project.

MRB integrates such cutting edge libraries as Backbone, Marionette, Require, Grunt, Jasmine, Bootstrap, and jQuery Mobile, among others. These libraries work together to help you start your project off with a rock-solid foundation, with a powerful module system, composite architecture, simple build process, and unit tests.

more...
No comment yet.
Scoop.it!

Unsuck your backbone // Speaker Deck

Unsuck your backbone // Speaker Deck | JavaScript for Line of Business Applications | Scoop.it

Backbone.js is a popular, super lightweight JavaScript framework which helps you structure your code MVC style. If you're building JavaScript applications of any reasonable size, you might have heard of it and you might have even given it a try. But if you have used it in anger, then you may have found that a backbone only gets you so far. As your application gets bigger, so does the complexity of your boilerplate code and structure. Let's kick this complexity to the curb, and string up our backbone on a marionette(.js).

more...
No comment yet.
Scoop.it!

Polymer Web Components with Marionette.js

Polymer Web Components with Marionette.js | JavaScript for Line of Business Applications | Scoop.it

I first developed the idea of making Polymer components play along with Marionette.js for a talk on architecture and components I gave at the inauguralNodevember conference in Nashville, TN.* If you would like to watch my talk, you can view it onYouTube.

Toward the end of my talk, I demoed creating a custom name tag element. Furthermore, I showcased the ability to wrap that custom element with a custom Marionette view type and keep model data synced with a regular Marionette ItemView. I would like to go into more detail the steps I took to create this custom Marionette view type and how I was able to keep model data synced.

more...
No comment yet.
Scoop.it!

Components with Backbone.js and Marionette.js

Components with Backbone.js and Marionette.js | JavaScript for Line of Business Applications | Scoop.it
Build and use reusable components in Backbone.js and Marionette.js to make clean and modular code.

Components are critical to scaleable applications because they encourage separation of concerns. Each piece of an application, including components, should have one responsibility and not heavily depend on the other pieces. Applications with tightly coupled modules or a lack of division of work will become incredibly more difficult to maintain and amend with newer features. Adding a single feature could require changing code in several places. Altering a function here breaks a function there, which then requires this other function to handle another parameter.

more...
No comment yet.
Scoop.it!

Complex Single Page Application Architecture with Backbone

Complex Single Page Application Architecture with Backbone | JavaScript for Line of Business Applications | Scoop.it

Over the past few months we've been developing the 2nd (and much improved) generation of the SOOMLA dashboard.  Though we use myriad front-side technologies, the jewel in the crown is Backbone.js.  Much has been written about Backbone, though still I find that most articles focus on HOW-TOs of models, views and events.  In this post, I’ll describe our dashboard’s Backbone architecture, with an attempt to zoom out a bit and understand the fundamentals of building complex, heavy single page applications (hereinafter SPA) with Backbone.  Disclaimer: this post is not about code, but about architecture concepts.  Therefore, the code examples won't be detailed to the bits and bytes, but they are all documented sufficiently to understand the idea.

We use:
* Require.js for dependency management and modular code.
* Backbone.js - for basic application structure and separation of concerns.
* Marionette.js - for composite application architecture and saving lots of Backbone boilerplate.
* underscore.js for general object, array and function utilities.
* undescore.string for extended string manipulation functionality.
* Handlebars.js - for client side templating.
* jQuery for DOM manipulation, AJAX, promises, and much more.
* These jQuery plugins: Qtip, SlimScroll, Isotope, jQuery UI sortable and jQuery validations.
* imagesloaded - for capturing and synchronizing image load events.
* Less - for CSS pre-processing.
* grunt.js - for build automation (tasks like pre-compilation, minifying and concatenating code).


more...
No comment yet.
Scoop.it!

Init.js: A Guide to the Why and How of Full-Stack JavaScript

Init.js: A Guide to the Why and How of Full-Stack JavaScript | JavaScript for Line of Business Applications | Scoop.it
Have you explored the full JavaScript stack? Init.js lets you instantly initialize and deploy apps built with Backbone, Node, Mongo, Grunt, Mocha, and more.

The core of the idea is to have a single project to start them all, to let the developer or the technical founder make all of these essential decisions at once, and receive an appropriate starting template based on those decisions. I know what detractors are going to say, “One solution can’t apply to every problem” (haters gonna hate). And they might be right. But we can do our best to create an approximate solution, and I think Init comes pretty close.

To best achieve this objective, we have to keep a few key ideas in mind. When developing Init, I considered:

* Components

* Ease of Development

* Community

Keeping these goals in mind, I’ll next show you how I made my own decision decisions in creating Init...

more...
No comment yet.
Scoop.it!

Marionette-Require-Boilerplate for Your Single Page Application

Marionette-Require-Boilerplate for Your Single Page Application | JavaScript for Line of Business Applications | Scoop.it
A lightweight Marionette and Require Boilerplate project to get your single page application off to a quick start on a solid foundation.

 

MRB integrates such cutting edge libraries as Backbone, Marionette, Require, Grunt,Jasmine, Bootstrap and jQuery Mobile, among others. These libraries work together to help you start your project off with a rock-solid foundation, with a powerful module system, composite architecture, simple build process, and unit tests.

Jan Hesse's insight:
Best Tools plus Best Practices
more...
No comment yet.