Webui.js

Webui.js is a Model-View-Controller implementation for Single-Page-Application in a browser

Introduction

Writing the client part of a business application can be a complex piece of software, and the best way to tame such a complex thing is to have high cohesion for robustness, reliability, reusability. and loose coupling for encapsulation, so changes in one place does not affect other places.

Mvc architecture is implemented by using the observer pattern where the model and view are subjects and the controller is an observer.

How is data mapped to html elements?

Image you have a person defined by this class:

class Person {
  constructor(name,addess,zipcode,town) {
    this.name = name;
    this.address = address;
    this.zipcode = zipcode;
    this.town = town;
  }

  ...    
}

Then name property is mapped to an html element like this input element:

<input data-class="Person" data-property="name">

or all the properties is mapped to input elements in a form element like this:

<form data-class="Person">
  <input data-property="name">
  <input data-property="address">
  <input data-property="zipcode">
  <input data-property="town">
</form>

Here the html input elements inherits the data-class information from the parent element. The view has html fragment which it is responsible for, and which is shown on demand from the controller.

How is data flowing?

The data flows between MVC elements by events to have loose coupling. The event is defined like this:

class Event {
  constructor(sender, name, body) {
    this.sender = sender;
    this.name = name;
    this.body = body;
  }
}

The view sends the following events when:

a input element has changed , the name of event is propertyChanged, with the name of the property and the new value in the body
an anchor element is clicked, the name of the event is click, with url information in the body
a button is pressed, the name of the event is the data-property from the button

The model sends the following events when:

data is available from an asynchronous/rest call, the name of the event is ok with the data in the body
the asynchronous/rest call fails, the name of the event is fail with information in body

How is the data flow controlled?

A controller overrides the handleEvent method and can thereby reacts to events send to it, and transforms them to method calls on the model or the view. Manage the state of the controller can be complex, so to help with this, you can use a state machine to do that.

How is the application controlled?