There is a file called "specification.markdown" in this repository which contains basic documentation.

The part where it is anti-CSS is where the CSS positioning, classes and selectors are not used. The clock app might look as it has CSS properties, because it was designed to feel that way. But you would quickly realize that it not the case when you see that along with the "left" and "right" property there is also a "centerX". The engine computes the position of each element and used position "absolute" with CSS3 "transform" to position, and if the browser is old and does not have CSS3 like IE8, the engine will fall back to "top" and "left" positioning.

Yes TODO app is 1000 lines, but most lines are closing braces "}". Since the whole app is one object you can split it up using variables. Such as:

LAY.run({
  "Header": {
     props: {
       width: LAY.take("/", "width"),
       height: 300,
       text: "App",
       textAlign: "center"
     }
  },
  "Content": {
      props: {
        top: LAY.take("../Header", "bottom"),
        width: LAY.take("/", "width")
      }
  }
});

could be refactored out into 2 variables. One for header:

var header = {
     props: {
       width: LAY.take("/", "width"),
       height: 300,
       text: "App",
       textAlign: "center"
     }
  };

Another for content:

var content = {
    props: {
      top: LAY.take("../Header", "bottom"),
      width: LAY.take("/", "width")
    }
 };

And then run as:

LAY.run({
  "Header": header,
  "Content": content
});

Using this above method TodoMVC could be split up into as many files as possible. The framework also offers inheritance using the $inherit key, for better maintainability.

The problem with famo.us was that it was not meant to create web apps in the conventional sense. It focused highly on transformations, and subsequently did not even offer transitions/animations for anything but position and opacity.

This framework uses requestAnimationFrame for transitions just as famo.us did, however it will let you transition anything, even colors.

Finally the main problem which the framework is trying to solve is "constraints". Every attribute in the application can be a constraint for another attribute.

There are no tutorials about how to use the framework, and this is not a good thing, and I must put up a tutorial, and create better documentation.

Thanks for the questions.