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 tag: 'Ampersand.js'. Clear
Scoop.it!

Amoklauf - A demo WebApp built with AmpersandJS & RiotJS

Amoklauf - A demo WebApp built with AmpersandJS & RiotJS | JavaScript for Line of Business Applications | Scoop.it

This is just a demo but at least a functional one. 

  • It shows a Login page (enter anything)
  • uses a real, JSON-based remote service (JSON Test)
  • has a Menu structure
  • has a Movie-list built with RiotControl and AmpersandJS Model & Collections
  • a Todo-List
  • and a Contact Form

It also can serve as a boilerplate because is very easy to replace/remove parts which are not of interest (or buggy?).

No comment yet.
Scoop.it!

Fission - The Reactjs Toolkit doing MVC

Fission - The Reactjs Toolkit doing MVC | JavaScript for Line of Business Applications | Scoop.it

Easy to use
Fission lets you focus on the app, not worry about designing the core system behind it.


Efficient
Fission uses React for extremely efficient rendering, with the best parts of Ampersandjs, model and state.


Customizable API
Fully modifiable API enables swapping out of core elements, such as Sync, for a mulit-service application


Open Source
Fission is, and will always be Fully Open Source.

No comment yet.
Scoop.it!

Opinionated Rundown of JS Frameworks

Opinionated Rundown of JS Frameworks | JavaScript for Line of Business Applications | Scoop.it

In doing our trainings and in writing my book, Human JavaScript and within our team itself we’ve come to realize there is a huge gap between picking a tool, framework, or library andactually building a complete application.

Not to mention, there are huge problems surrounding how to actually build an app as a team without stomping on each other.

There are sooooo many options and patterns on how to structure, build, and deploy applications beyond just picking a framework.

Few people seem to be talking about how to do all of that, which is just as big of a rabbit hole as picking a framework!

No comment yet.
Scoop.it!

RactAmp - RactiveJS components with AmpersandJS models

RactAmp - RactiveJS components with AmpersandJS models | JavaScript for Line of Business Applications | Scoop.it

As a performant view layer Ractive lets you decide how and by using which of the available "frameworks" you're gonna control backend logic. And as a "non-frameworky framework" AmpersandJS is an ideal choice to utilize only certain parts of a (probably) much bigger machinery to solve discrete problems.

No comment yet.
Scoop.it!

Building an app with Ampersand.js

Building an app with Ampersand.js | JavaScript for Line of Business Applications | Scoop.it

The corner-stones of Ampersand is the statemodel, and view modules. There's no "core" module or anything. If you just want some basic view layer you could pull in just the view module for example.

As I mentioned before, Ampersand does not come with any "core" module. Which isn't really mentioned anywhere in the docs — that confused me for a while. So, we'll need to setup something of our own. First, let's lay out the things we need:

  1. A way to map "code" to a "url". Ie. we need a router and some way to structure that code.
  2. A way to keep track of global state. This might be a user's session for example. Things that doesn't really fit within a model.
  3. A way to manage instantiated models. So that we can make sure we're not running around with duplicates.
  4. Someway to manage the app chrome (navigation bars and what not — stuff that is not part of one special page).


No comment yet.