JavaScript for Line of Business Applications
596.1K views | +0 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...

Popular Tags - Filter using the Funnel

Current selected tags: 'Frameworks', 'Tutorial'. Clear
Scoop.it!

Writing a JavaScript Framework - Project Structuring

This post is a tutorial for writing a next-gen JavaScript Framework & solving problems regarding extendibility, dependency injection and private variables.

 

In this chapter, I am going to explain how NX is structured, and how I solved its use case specific difficulties regarding extendibility, dependency injection and private variables.

The series includes the following chapters.

  1. Project structuring (current chapter)
  2. Execution timing
  3. Sandboxed code evaluation
  4. Data binding (part 1)
  5. Data binding (part 2)
  6. Custom elements
  7. Client side routing
No comment yet.
Scoop.it!

Web Design and Development

Web Design and Development | JavaScript for Line of Business Applications | Scoop.it
Topics for web, mobile design and development.

Really well fed Blog with a Collection on free Tutorials and News Panels for the Front-End Developer.

Jan Hesse's insight:

discovered it and found a lot of value in it

No comment yet.
Scoop.it!

Large-scale JavaScript Application Architecture

Large-scale JavaScript Application Architecture | JavaScript for Line of Business Applications | Scoop.it

Developers creating JavaScript applications these days usually use a combination of MVC, modules, widgets and plugins for their architecture. They also use a DOM manipulation library like jQuery.

Whilst this works great for apps that are built at a smaller-scale, what happens when your project really starts to grow?

In this talk, I present an effective set of design patterns for large-scale JavaScript (and jQuery) application architecture that have previously been used at both AOL and Yahoo amongst others.

You'll learn how to keep your application logic truly decoupled, build modules that can exist on their own or be dropped into other projects and future-proof your code in case you need to switch to a different DOM library in the future.

Jan Hesse's insight:

kinda old but still worth a look to get a refreshed overview

No comment yet.
Scoop.it!

Learning JavaScript: Great libraries

Learning JavaScript: Great libraries | JavaScript for Line of Business Applications | Scoop.it
underscore – going the functional route

Why: JavaScript is a functional language but its standard libraries miss a lot of the functional goodies we are used to from other languages. Here underscore comes to the rescue.


when.js – lightweight concurrency

Why: Concurrency is hard. Callbacks can get out of hand pretty quickly even more so when they are nested. Promises make writing and reading concurrency code simpler.


require.js – modules (re)loaded

Why: Your scripts need to be in modules, cleanly separated from each other. If you don’t have an asset pipeline want to load your modules asynchronously or just want to manage your modules from your JavaScript require.js is for you.


bower – packages managed

Why: Proper dependency management is a tough nut to crack and it is even harder to be pleasantly used (I am looking at you, maven).


grunt – the worker

Why: Repetitive tasks need to be automated. If you plan to use grunt and bower consider using yeoman which combines both into a workflow.


d3 – visualizations

Why: There are tons of chart or visualization libraries out there but d3 takes a more general approach. It defines a way of thinking, a way of manipulating the document based on data and data alone. It treats the DOM as part of your web application. Your visualization is a part of your document and not just a component you can forget about after creating it. This general approach allows you to create arbitrary visualizations not just charts.


last but not least: jQuery

Why: jQuery is almost ubiquitous and this is not by chance. It provides a great foundation and helps in many common scenarios.

No comment yet.
Scoop.it!

Tested various Javascript MV* frameworks

Tested various Javascript MV* frameworks | JavaScript for Line of Business Applications | Scoop.it

I wanted to try and compare some other popular Javascript MV* frameworks. I am aware that TodoMVC exists for this, but I wanted to implement the same thing (with encrypted local storage) that previously was created with AngularJS.

What to implement:
* Create a view that has a input[type=text] field
* When the user enters some text in the input, encrypt the text and save it in localStorage
* Instantly display the encrypted text and the decrypted text

 

The following code samples seems to do the right thing / achieve the same results. I have just included the code samples here, with a small summary for every frameworks with my own pros and cons.

 

* KnockoutJS
* VanillaJS (simple)
* VanillaJS (MVC style)
* BackboneJS
* EmberJS
* AngularJS

No comment yet.