Diablo

An experimental fork of yo-yo.js adding composable custom components.

Components

Components in Diablo are very similar to React.

Register a named component using x.component:

x.component('MyButton', {
  handleClick: function () {
    this.props.onClick()
  },

  render: function () {
    return x`
      <button onClick=${this.handleClick.bind(this)}>
        Cool Button: ${this.children}
      </button>
    `
  },
})

You can then create MyButton components by rendering ```x`template```` literals:

function sup() { alert('yo, sup?') }
x.render(x`<MyButton onClick=${sup}></MyButton>`, document.body)

When DOM is generated using template literals, placeholders for components are created which are not instantiated yet. For instance, x`<MyButton onclick=${sup}></MyButton>` will return a <co-mybutton /> DOM node which records the props you specified which has not been instantiated or rendered.

Component instances persist between re-renders. In the future, it should be possible to implement local component state and lifecycle methods similar to React.

setState

Components support a setState method, which behaves similar to React. The current state of a component is available as this.state within render() methods.

componentDidMount / componentWillUnmount

These methods, if defined on a component, will be called after a component is added to the DOM, and before it is removed from the DOM. Within these functions, component.getDOMNode() can be used to obtain a reference to the component's current top-level DOM element.

shouldComponentUpdate

Components support an optional shouldComponentUpdate(nextProps, nextState) method which they can use to skip rendering their subtree if their data hasn't changed.

Rendering

In Diablo, x.render(element, container) functions similar to React. It will render an element into a container. If the element was previously rendered in the container, the container will be efficiently updated via a DOM diff.