Component Model Use Cases - Revision history

Annevk at 15:46, 10 November 2012

2012-11-10T15:46:59Z

← Older revision		Revision as of 15:46, 10 November 2012
Line 1:		Line 1:
	~~<span style~~=~~"color:Red">This page is deprecated. New work is here:~~ http://www.w3.org/2008/webapps/wiki/Component_Model_Use_Cases~~</span>~~		{{obsolete\|see=http://www.w3.org/2008/webapps/wiki/Component_Model_Use_Cases}}

	These use cases represent a set of problems we are trying to solve by implementing a [[Component_Model \| component model]] for the web.		These use cases represent a set of problems we are trying to solve by implementing a [[Component_Model \| component model]] for the web.

Dglazkov at 18:12, 29 November 2011

2011-11-29T18:12:37Z

← Older revision		Revision as of 18:12, 29 November 2011
Line 1:		Line 1:
			<span style="color:Red">This page is deprecated. New work is here: http://www.w3.org/2008/webapps/wiki/Component_Model_Use_Cases</span>

	These use cases represent a set of problems we are trying to solve by implementing a [[Component_Model \| component model]] for the web.		These use cases represent a set of problems we are trying to solve by implementing a [[Component_Model \| component model]] for the web.

Rolandsteiner: /* Custom Controls */ Add "entry-helper"

2011-11-02T16:41:20Z

Custom Controls: Add "entry-helper"

@@ Line 150: / Line 150: @@
 |-
 ! align="right" valign="top" | Purpose
 | Make it easy for Web authors to create charts and diagrams using table markup.
 |-
 ! align="right" valign="top" | Examples
@@ Line 174: / Line 173: @@
 |-
 ! align="right" valign="top" | Purpose
 | Make it easy for Web authors to spruce up time zone selection (or similar).
 |-
 ! align="right" valign="top" | Examples
@@ Line 185: / Line 183: @@
 * [[Component_Model#Extensibility | Extensibility]] -- Basically extending &lt;select&gt;. Should fall back to a simple &lt;select&gt; where components are not supported.
 * [[Component_Model#Consistency | Consistency]] -- Extend the &lt;select&gt; API for item selection.
 |}

Rolandsteiner: /* Custom Controls */ Add time zone selector use case

2011-10-11T06:25:47Z

Custom Controls: Add time zone selector use case

@@ Line 161: / Line 161: @@
 * [[Component_Model#Composability | Composability]] -- one should be able to make chart by creating a table, imperatively or declaratively.
 * [[Component_Model#Performance | Performance]] -- no FOUC or blocking load when charts are loaded.
 |}

Dglazkov: /* Like/+1 Button */

2011-09-29T19:56:50Z

Like/+1 Button

@@ Line 137: / Line 137: @@
 * [[Component_Model#Confinement | Confinement]] -- a way to completely isolate the widget implementation from the document in which it is being embedded.
 * [[Component_Model#Performance | Performance]] -- don't block the page load.
 |}

Rolandsteiner: "... all contents or
..." -> "... all contents of
..."

2011-08-24T06:03:08Z

"... all contents or <details>..." -> "... all contents of <details>..."

← Older revision		Revision as of 06:03, 24 August 2011
Line 174:		Line 174:
	==Details/Summary Elements==		==Details/Summary Elements==

	Implement [http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-details-element details] and [http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-summary-element summary] elements. According to the spec, the first <code>summary</code> element found in the flow content is used to represent a summary or legend of details. In case a <code>summary</code> element is not found, the UA is supposed to auto-generate some fallback content. The <code>details</code> element itself needs to have a marker indicating whether <code>details</code> element is open or closed - i.e., whether all contents or <details> are shown, or only the summary.		Implement [http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-details-element details] and [http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-summary-element summary] elements. According to the spec, the first <code>summary</code> element found in the flow content is used to represent a summary or legend of details. In case a <code>summary</code> element is not found, the UA is supposed to auto-generate some fallback content. The <code>details</code> element itself needs to have a marker indicating whether <code>details</code> element is open or closed - i.e., whether all contents of <details> are shown, or only the summary.

	Just like media controls, the implementation should not be accessible by the consumer of the elements. For example, the reordering of flow content to position <code>summary</code> element as first item in the disclosure widget should be imperceptible to DOM traversal methods.		Just like media controls, the implementation should not be accessible by the consumer of the elements. For example, the reordering of flow content to position <code>summary</code> element as first item in the disclosure widget should be imperceptible to DOM traversal methods.

Dglazkov at 20:12, 19 August 2011

2011-08-19T20:12:46Z

← Older revision		Revision as of 20:12, 19 August 2011
Line 1:		Line 1:
	These use cases represent a set of problems we are trying to solve by implementing a component model for the web.		These use cases represent a set of problems we are trying to solve by implementing a [[Component_Model \| component model]] for the web.

	=Custom Controls=		=Custom Controls=

Dglazkov: /* Rendering Form Controls with SVG */

2011-08-19T19:28:58Z

Rendering Form Controls with SVG

← Older revision		Revision as of 19:28, 19 August 2011
Line 83:		Line 83:
	! align="right" valign="top" \| Desirable Properties		! align="right" valign="top" \| Desirable Properties
	\|		\|
	* [[Component_Model#~~Composability~~ \| ~~Composability~~]] -- the controls should act just like any other DOM elements.		* [[Component_Model#Consistency \| Consistency]] -- the controls should act just like any other DOM elements.
	* [[Component_Model#Encapsulation \| Encapsulation]] -- the document shouldn't be able to accidentally mess up the rendering of the controls.		* [[Component_Model#Encapsulation \| Encapsulation]] -- the document shouldn't be able to accidentally mess up the rendering of the controls.
	* [[Component_Model#Performance \| Performance]] -- load quickly, avoid [http://en.wikipedia.org/wiki/Flash_of_unstyled_content FOUC]-like symptoms when using controls.		* [[Component_Model#Performance \| Performance]] -- load quickly, avoid [http://en.wikipedia.org/wiki/Flash_of_unstyled_content FOUC]-like symptoms when using controls.

Dglazkov at 18:46, 19 August 2011

2011-08-19T18:46:39Z

← Older revision		Revision as of 18:46, 19 August 2011
Line 31:		Line 31:
	* [[Component_Model#Composability \| Composability]] -- a method to compose layouts with both UI primitives and DOM elements.		* [[Component_Model#Composability \| Composability]] -- a method to compose layouts with both UI primitives and DOM elements.
	* [[Component_Model#Extensibility \| Extensibility]] -- a way to build on layout primitives to create new ones.		* [[Component_Model#Extensibility \| Extensibility]] -- a way to build on layout primitives to create new ones.
			* [[Component_Model#Encapsulation \| Encapsulation]] -- styles, defined to hold layout in place should not be in danger of being stomped on by the author stylesheets.
	* [[Component_Model#Performance \| Performance]] -- layouts built with layout manager should appear quickly, avoiding re-flows and [http://en.wikipedia.org/wiki/Flash_of_unstyled_content FOUC]-like symptoms.		* [[Component_Model#Performance \| Performance]] -- layouts built with layout manager should appear quickly, avoiding re-flows and [http://en.wikipedia.org/wiki/Flash_of_unstyled_content FOUC]-like symptoms.
	\|}		\|}
Line 82:		Line 83:
	! align="right" valign="top" \| Desirable Properties		! align="right" valign="top" \| Desirable Properties
	\|		\|
	* [[Component_Model#~~Extensibility~~ \| ~~Extensibility~~]] -- ~~a way~~ to ~~override appearance~~ of ~~native form~~ controls.		* [[Component_Model#Composability \| Composability]] -- the controls should act just like any other DOM elements.
			* [[Component_Model#Encapsulation \| Encapsulation]] -- the document shouldn't be able to accidentally mess up the rendering of the controls.
			* [[Component_Model#Performance \| Performance]] -- load quickly, avoid [http://en.wikipedia.org/wiki/Flash_of_unstyled_content FOUC]-like symptoms when using controls.
	\|}		\|}

Line 106:		Line 109:
	\|		\|
	* [[Component_Model#Encapsulation \| Encapsulation]] -- means to ensure style of the document does not affect the widget, and widget's logic is kept to the widget.		* [[Component_Model#Encapsulation \| Encapsulation]] -- means to ensure style of the document does not affect the widget, and widget's logic is kept to the widget.
			* [[Component_Model#Composability \| Composability]] -- easily added anywhere in the DOM tree.
	\|}		\|}

Line 132:		Line 136:
	* [[Component_Model#Encapsulation \| Encapsulation]] -- means to ensure style of the document does not affect the widget, and widget's logic is kept to the widget.		* [[Component_Model#Encapsulation \| Encapsulation]] -- means to ensure style of the document does not affect the widget, and widget's logic is kept to the widget.
	* [[Component_Model#Confinement \| Confinement]] -- a way to completely isolate the widget implementation from the document in which it is being embedded.		* [[Component_Model#Confinement \| Confinement]] -- a way to completely isolate the widget implementation from the document in which it is being embedded.
			* [[Component_Model#Performance \| Performance]] -- don't block the page load.
	\|}		\|}

Dglazkov: /* Layout Manager */

2011-08-19T18:41:25Z

Layout Manager

← Older revision		Revision as of 18:41, 19 August 2011
Line 31:		Line 31:
	* [[Component_Model#Composability \| Composability]] -- a method to compose layouts with both UI primitives and DOM elements.		* [[Component_Model#Composability \| Composability]] -- a method to compose layouts with both UI primitives and DOM elements.
	* [[Component_Model#Extensibility \| Extensibility]] -- a way to build on layout primitives to create new ones.		* [[Component_Model#Extensibility \| Extensibility]] -- a way to build on layout primitives to create new ones.
			* [[Component_Model#Performance \| Performance]] -- layouts built with layout manager should appear quickly, avoiding re-flows and [http://en.wikipedia.org/wiki/Flash_of_unstyled_content FOUC]-like symptoms.
	\|}		\|}

← Older revision		Revision as of 19:28, 19 August 2011
Line 83:		Line 83:
	! align="right" valign="top" \| Desirable Properties		! align="right" valign="top" \| Desirable Properties
	\|		\|
	* [[Component_Model#~~Composability~~ \| ~~Composability~~]] -- the controls should act just like any other DOM elements.		* [[Component_Model#Consistency \| Consistency]] -- the controls should act just like any other DOM elements.
	* [[Component_Model#Encapsulation \| Encapsulation]] -- the document shouldn't be able to accidentally mess up the rendering of the controls.		* [[Component_Model#Encapsulation \| Encapsulation]] -- the document shouldn't be able to accidentally mess up the rendering of the controls.
	* [[Component_Model#Performance \| Performance]] -- load quickly, avoid [http://en.wikipedia.org/wiki/Flash_of_unstyled_content FOUC]-like symptoms when using controls.		* [[Component_Model#Performance \| Performance]] -- load quickly, avoid [http://en.wikipedia.org/wiki/Flash_of_unstyled_content FOUC]-like symptoms when using controls.