removed about zebkit

[barmalei]

A: Integrated JQuery support.
Never :) I don't need one more framework and I don't need to bring "dead code" support for all old-browser stuff in zebra. And also DOM/CSS manipulation has to be minimized whenever it is possible. Also Zebra is for HTML5 based browser only, many things are more well standartized and archaic stuff is blown away.

A: Layer
I cannot understand completely your suggestion. I am going to improve painting. But not in a week o so. Everything will be done in context of Zebra PaintManger. Zebra uses layers, but it is not layer in term of DOM elements. Layer is UI panel that stretched over full size of canvas and can catch control. Every time a new event occurs Zebra asks layers from top to buttom whether a layer wants to take control or not. First found active layer take the control.

From the UI point of view Layer is standard UI panel, that are children UI component of zCanvas UI component. Every time a repaint method is called Zebra paints whole hierarchy of zCanvas UI component including layers. Paint manager cares about re-painting only "dirty" area, not the whole collection. Also it tries optimize background painting, also it is responsible for repainting scheduling. In this context of performance improvement it makes sense to use double buffering for layers. That means every layer will create and use HTML Canvas to render its content. So if a layer (with own UI components) doesn't have a dirty area it can just paint its buffer as is.

Video player in this new approach can be implemented as layer that sits under UI layer. In this case video rendering will not disturb UI. From the code point of view it will look as follow:

var canvas = new zCanvas();
// add Video on own layer
canvas.insert(0, new BaseLayer("video", new VideoPan("movie.m4")));

// build UI for player
canvas.root.properties({
    layout: ...,
    kids : [
       ...

    ]
});

from zebkit.

[barmalei]

by the way you can build source (combine it and minimize), it is described in readme