$ go get -u tower.pro/renderer

Start API server:

$ renderer server -watch -components ./examples/
$ # With routes
$ renderer server -watch -components ./examples/ -routes ./examples/routes.yaml

Render using API:

API responds with JSON only when Accept header contains application/json, by default it writes HTML response.

# GET with component in URL
# http://127.0.0.1:6660/?name=dashboard.components&context={"components":[{"name":"example number one"}]}
# Or with POST method and component in body
$ curl -XPOST --data '{
  "name": "dashboard.components",
  "context": {
    "components": [
      {
        "name": "my.example.component"
      }
    ]
  }
}' http://127.0.0.1:6660/

Some example components can be found in dashboard/components directory.

JSON representation of an example.root component:

{
  "name": "example.root",
  "main": "file://component.html",
  "styles": [
    "https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css",
    "https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap-theme.min.css",
    "file://component.css"
  ],
  "scripts": [
    "https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js",
    "https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js",
    "file://application.js"
  ]
}

Example of including components: movies.movie with movies.video component that can be rendered using {{ video_component }}:

Additionaly this component extends movies.root so after this component will be rendered, result will be included in movies.root under {{ children }} value.

{
  "name": "movies.movie",
  "main": "file://component.html",
  "extends": "movies.root",
  "require": {
    "video_component": {
      "name": "movies.video",
      "with": {
        "title": "{{ movie.title }} ({{ movie.year }})"
      }
    }
  }
}

Rendering admin.domains component with a list of domains in context.

{
  "name": "admin.domains",
  "context": {
    "domains": [
      {"name": "test.pl", "links": ["test.pl"]},
      {"name": "test2.pl", "links": ["test.pl"]},
      {"name": "test3.pl", "links": ["test.pl"]}
    ]
  }
}

All data can be embed in component.json:

• http:// and https:// urls are allowed
• file:// should be relative to component.json
• text:// for plain text (non templates)
• template:// will be executed as template

{
  "name": "example.root",
  "main": "template://<h1>{{title}}</h1>",
  "styles": [
    "template://h1 { color: {{ color }}; }",
    "text://some text here"
  ],
  "scripts": [
    "template://console.log('{{ message }}');",
    "text://console.log('test');"
  ]
}

So what a compiler is:

• Has 3-rd party storage interface
• Gets components from this storage
• Compiles components for rendering
• When asked for a component looks in storage
• Compiles components on demand
• Caches compiled results

File system storage and watching for changes

• Components are very lightweight so full in-memory storage is fine along with file system replication
• Compiler itself does not have to watch for changes in files when a file system storage may be in-memory cached and on-change caches can be cleared.

Apache 2.0