templates's Introduction

Templates

Base framework for creating UI templates that are compiled for running both on server-side and client-side (in javascript).

Example template can be found in Index.html. Not prefixed html tags are outputed as they are, those with prefix are instantiated and processess dynamicly. Beside html tags, also syntax in form {Binding Abc} is processed dynamicly. And special meaning has also prefixed html attributes, which are processed as extensions (or observers) on the original html tag.

More details about template processing can be found on our WIKI

templates's People

Contributors

Watchers

templates's Issues

Create content parser using Microsoft.Html.Core

From master, create an implementation of IContentParser using Microsoft.Html.Core.

This library has support for invalid/uncomplete HTML and so is ideal for use in the editor.
Skip curly tokenizer and value parsers for now.

VS Editor could be hosted as a separate process

Inspiration in RazorHost.
https://github.com/aspnet/Mvc/tree/38e1e7d14ea2375ebf8427d8764e54a73d213a47

Next generation UI templates

Next generation templates for UI should not only String Builder for HTML.
We should use progressive enhancement.

1) String Builder mode

As in original version, we should support generating HTML to string and than pasting it into the DOM. This mode will be compatible for both server and client rendering mode.

2) Manual DOM manipulation

A views can have named controls. These controls can that be accessed after rendering is completed. Such controls can than modify DOM. Eg.: TextBox can read and write current value.
This mode will be available in client mode. Also, we should try to support rebuilding javascript instance of view from server rendered HTML.