A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Component Model Declarative Syntax: Difference between revisions
Jump to navigation
Jump to search
m (→Requirement) |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Declarative Syntax provides the way to define new components using HTML markup. | Declarative Syntax provides the way to define new components using HTML markup. | ||
= Requirements = | = Requirements, Desirable properties = | ||
* It should be embeddable into HTML. | * It should be embeddable into HTML. | ||
* It should be separately definable and loadable. | * It should be separately definable and loadable. | ||
* It should have equivalent representation in imperative (JavaScript) form and vice versa. | * It should have equivalent representation in imperative (JavaScript) form and vice versa. | ||
* It should allow compilation to single file. (asset pipelining) | |||
* It should fallback gracefully. | |||
* Script text can be unobtrusive. We should have a way to write script separately from markup. | |||
* Each component definition can be self-contained. | |||
Latest revision as of 09:00, 6 October 2011
Declarative Syntax provides the way to define new components using HTML markup.
Requirements, Desirable properties
- It should be embeddable into HTML.
- It should be separately definable and loadable.
- It should have equivalent representation in imperative (JavaScript) form and vice versa.
- It should allow compilation to single file. (asset pipelining)
- It should fallback gracefully.
- Script text can be unobtrusive. We should have a way to write script separately from markup.
- Each component definition can be self-contained.