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).

Difference between revisions of "Component Model Methodology"

From WHATWG Wiki
Jump to navigation Jump to search
 
Line 32: Line 32:
* Study popular patterns in existing Web frameworks and '''pave the cowpaths''' when appropriate;
* Study popular patterns in existing Web frameworks and '''pave the cowpaths''' when appropriate;
* Encourage '''each building block to stand on its own''' merits.
* Encourage '''each building block to stand on its own''' merits.
=Implementation Sequence=
Since the component model is composed of several building blocks, it is possible to implement it incrementally, gaining more insight with each step. Here's one possible sequence (tabulated against the [[Component_Model_Use_Cases | use cases]] and approximate percentage of satisfying them):
{| cellpadding="10" cellspacing="0" style="border-collapse: collapse;"
|- valign="top" style="border-bottom: 1px solid LightGray;"
! align="left" | Step
! align="left" | [[Component_Model_Use_Cases#Layout_Manager | Layout Manager]]
! align="left" | [[Component_Model_Use_Cases#Widget_Mix-and-Match | Mix-and-Match]]
! align="left" | [[Component_Model_Use_Cases#Rendering_Form_Controls_with_SVG | SVG Controls]]
! align="left" | [[Component_Model_Use_Cases#Contacts_Widget | Contacts Widget]]
! align="left" | [[Component_Model_Use_Cases#Like.2F.2B1_Button | Like/+1 Button]]
! align="left" | [[Component_Model_Use_Cases#Media_Controls_For_The_Video_Element | Media Controls for the Video Element]]
! align="left" | [[Component_Model_Use_Cases#Details.2FSummary_Elements | Details/Summary Element]]
|- valign="top" style="border-bottom: 1px solid LightGray;"
| [[Component_Model#Shadow_DOM | Shadow DOM]]
| 25%
| -
| 34%
| 100%
| 25%
| 100%
| 50%
|- valign="top" style="border-bottom: 1px solid LightGray;"
| [[Component_Model#Content_Element | Content Element]]
| 25%
| -
| -
| -
| -
| -
| 50%
|- valign="top" style="border-bottom: 1px solid LightGray;"
| [[Component_Model#Constructable_DOM_Types | Constructable DOM Types]]
| 25%
| 50%
| 33%
| -
| 25%
| -
| -
|- valign="top" style="border-bottom: 1px solid LightGray;"
| [[Component_Model#Registering_Elements | Registering Elements]]
| 25%
| 50%
| 33%
| -
| 25%
| -
| -
|- valign="top" style="border-bottom: 1px solid LightGray;"
| [[Component_Model#Confinement_Primitives | Confinement Primitives]]
| -
| -
| -
| -
| 25%
| -
| -
|}

Latest revision as of 17:35, 23 August 2011

Here are the guidelines for understanding the problem of and developing specification for the Component Model.

Approach

  1. Capture requirements as use cases;
  2. Study use cases and extract a set of desired properties for these use cases;
  3. Come with a design that satisfies all desired properties;
  4. Extrude building blocks out of the design;
  5. Write specification draft(s) for the building blocks;
  6. Cultivate implementation feedback:
    • Provide experimental implementation(s) for the building blocks;
    • Seek feedback from the use case audiences;
    • Incorporate feedback into specification.
  7. Write a test suite.
  8. Iterate until success criteria is reached.

Success criteria

  • The use cases:
    • reasonably cover a set of component model needs on the Web.
  • The properties:
    • completely describe the set of use cases;
    • are orthogonal to each other.
  • The building blocks:
  • The specification:
    • is a complete set of requirements for all building blocks and corner cases, discovered during implementation;
  • The test suite:
    • provides coverage for each requirement in the specification.

Design Principles

  • Reuse existing mechanisms as much as possible, gently extending them if necessary;
  • Study popular patterns in existing Web frameworks and pave the cowpaths when appropriate;
  • Encourage each building block to stand on its own merits.