Version 2.0.0-alpha.2

• BREAKING CHANGE: When rerendering a view in collection binding with new model data, the view is not destroyed/rerendered from scratch but the new models are passed to the view and its refresh method is called so that the view can refresh only DOM elements that really change. All internal bindings work that way but any user defined views that work with models or the DOM explicitly must implement the refresh method to rebind changed models and project changes into the DOM.
• A new method kff.View#refreshAll does cascading refresh of the view tree.
• Better algorithm for diff collection and bindings refreshing/rerendering. No more superfluous rerendering of views. A new template kff.View#refresh method is used to update the view. Note that it's up to the view to determine if it needs to refresh.
• Data bindings work with plain JS object as well. Plain object bindings are not watched, any change have to be manually rerendered by the refreshAll method.
• Collection binding can work with plain arrays. The new ':each' modifier must be used to indicate 'array as collection' binding, because array can be also used as attribute value (for example in multiple select). Array binding is not watched, any change have to be manually rerendered by the refreshAll method.
• Helpers (parsers and formatters in views) can now be passed to individual views in constructor using DI. Old global register method is now obsolete. Helpers also have their own scope in view hierarchy similar to the model scope, so any subview has immediate access to helpers from any parent view.
• A new binder modifier :evf (eventFilter) to process DOM events through a function. The filter function must be registered in helpers view option. The filter function must accept two arguments: 'fn' - the original event handler and 'event' - the original DOM event. When the event is accepted, the function must call the original handler: fn.call(this, event).
• A new binding modifier ':nopreventdef' to suppress calling event.preventDefault in DOM event handler.
• A new binder (kff.CallBinder aka :call) that calls a method of a model with arguments. The attribute part of model path must be a valid model method. Arguments can be plain strings (processed by implicit type conversion) or models from the current scope (prefixed with @ char).
• Implicit conversion of basic data types from bindings. Used to process any values from binding attributes. It is not used to process DOM values (such as input value). Conversions are as follows:
  • "null" => null
  • "true" => true
  • "false" => false
  • "42" => 42 (convert number in string to number)
• New binders (kff.IfBinder - :if, kff.IfNotBinder - :ifnot) that insert/remove view element to/from the DOM. They work like the 'insert' binder with a new cleaner syntax. These binders destroy all subviews when removing view element from the DOM and rerender them when inserting. They do not render any subviews during the initial render phase. Both :if and :ifnot binders have default condition value true.
• A new :classnot binder that works like the :class binder but works in opposite way - it removes the class when the value is true. Both :class and :classnot binders now have default condition value true.
• Primitive types (string, number and boolean) can be used as models (it has only limited use case such as fast rendering of long list of values)
• A new option called 'regions' is now available in views. It should be a plain object that contains key-value pairs in form of 'css selector': 'html template string'. When the page view is rendered (before render method), each html template is inserted into the DOM node(s) matching the css selector. If the node is not empty, its content is cached in a temporary document fragment and it is inserted back to the node when the view is being destroyed. So the overlaying page views can even overwrite regions of previous views without damaging entire app. A special selector self is used to insert HTML template directly into the view element. The self selector is always rendered before any other regions so that they can reference DOM elements from the 'self' template.
• Page views and app can be bound to any DOM element, not just body and document.
• Added ability to destroy app, front controller and state handler.
• Eliminated dependency for document and window objects in views. Removing dependencies for global browser objects is an important step for server side rendering in node.js environment. Document and window objects are now passed in env object as a option in views, app and front controller. Note that the globals are still used in polyfills, but these are not used in node.
• Implemented a simple module dependency system for resolving "static" dependencies like class extends. Function kff.define defines a module with dependencies. kff.require returns module while resolving and injection all the dependencies. It works in similar way like the AMD but can be used together with DI container. Service container now tries to resolve any dependency using kff.require with fallback to global object look up when it fails.
• Preliminary support for routing "middlewares" (experimental feature)
• Added simple debug mode. When the kff.debug property is set to true, then some warnings are logged into console (such as missing views).
• Merged kff.BindingView class into kff.View class. Collection binding methods were moved into a separate class.
• Implemented a new dispatch binder operator that passes DOM binding events to some sort of global dispatcher instead of pushing to the model directly (inspired by the Flux pattern). This allows things such as using immutable data without two-way binding instead of model and collection classes. This feature is still in experimental state and will change in the future.
• Numerous fixes and optimizations