JavaScript for Li...
Follow
Find tag "mvp"
439.5K views | +318 today
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!

Riot.js — The 1kb client-side MVP framework

Riot.js — The 1kb client-side MVP framework | JavaScript for Line of Business Applications | Scoop.it
An incredibly fast, powerful yet tiny client side framework for building large scale web applications.

 

Riot.js is a client-side Model-View-Presenter (MVP) framework that weighs less than 1kb. Despite the unbelievable size, all the building blocks are there: a template engine, router, event library and a strict MVP pattern to keep things organized. Your views are automatically updated when the underlying model changes.

Riot.js is faster and simpler — in fact, on a completely different scale — and applications built with it are also faster and simpler. For real.

Let's go deeper...

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

Learning JavaScript Design Patterns

Learning JavaScript Design Patterns | JavaScript for Line of Business Applications | Scoop.it

Here you get a complete reference of JS Programming Patterns that may help structureing your code for better independency and reuse.

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

Scaling Isomorphic Javascript Code

Scaling Isomorphic Javascript Code | JavaScript for Line of Business Applications | Scoop.it

Design patterns are the bread and butter of application development. They encapsulate and outline the concerns of the application and the environment of the in which it exists. Between the browser and the server these concerns can vary widely:
* Is the view ephemeral (e.g. on the server) or long-lived (e.g. in the browser)?
* Is the view reusable across different use-cases or scenarios?
* Should the view be annotated with application-specific tags or markup?
* Where should the bulk of the business logic reside? (in the model? in the controller?)
* How is the application state persisted or accessed?
Lets explore some of the existing patterns and how they answer these questions:
* Model-View-Controller
* Model2
* Model-View Presenter and Model-View-ViewModel
* Modern Javascript Implementations
* Real-time Implications
* tl;dr? Introducing Resource-View-Presenter
* Conclusion

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

MVVM vs MVP vs MVC: The differences explained

MVVM vs MVP vs MVC: The differences explained | JavaScript for Line of Business Applications | Scoop.it
A set of bullet points explains the basics of MVVM, MVP, and MVC as well as guidelines for using each architecture with proper technologies.
more...
No comment yet.