Changes between Version 4 and Version 5 of XBL2UseCases


Ignore:
Timestamp:
Dec 2, 2010 8:51:03 AM (13 years ago)
Author:
Dimitri Glazkov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • XBL2UseCases

    v4 v5  
    1212 * shadow DOM
    1313 * UA-level attachment
    14  * Ability to completely hide implementation from consumer
    15  * Restricted post-UA-level styling using pseudoclasses
    16  * High performance
     14 * ability to designate and use DOM SPIs only within the shadow scope
     15 * ability to completely hide implementation details from author and user
     16 * restricted post-UA-level styling using pseudoclasses
     17 * style/event propagation control at the borders of the shadow DOM
     18 * high performance, especially compared to native implementation
    1719
    1820Could use:
     
    2527 * attachment using CSS or DOM
    2628 * content element (output ports), since they can't have children (this may change)
    27  * attribute forwarding
     29 * attribute/pseudo forwarding
    2830 * xml:base handling
    2931
     
    3234Does:
    3335 * provide a uniform way (i.e. DOM) to declare widget APIs
     36 * encapsulate widget implementation details
     37 * enable control over how styles and events outside of a widget affect it
     38 * enable widget styling primitives
    3439 * asynchronously instantiate and initialize widgets (for instance, display a widget without starting up a script context, then progressively enhance with script).
    3540 * allow seamless reuse a widget written using various libraries or frameworks
     
    4045 * shadow DOM
    4146 * content element (output ports)
     47 * style/event propagation control at the borders of the shadow DOM
    4248 * attachment using CSS and DOM
    43  * separation of instantiation and binding phases (or another way to allow asynchronous binding)
    44  * attribute forwarding
     49 * separate instantiation and binding phases (or another way to allow asynchronous binding)
     50 * attribute/pseudo forwarding
    4551 * declarative templating/binding
    4652
     
    5157Doesn't care:
    5258 * mutable templates
     59 * xml:base handling
    5360
    5461=== Layout Manager ===
    5562
    56  * make easier the restructuring of content to accommodate layout, both in an imperative and a declarative way
    57  * enable development of templating/theming frameworks
     63Does:
     64 * provide a framework for client-side restructuring of content to accommodate layout
     65 * support both imperative a declarative layout models
     66 * provide templating/theming capabilities
     67
     68Needs:
     69 * shadow DOM
     70 * content element (output ports)
     71 * attachment using CSS and DOM
     72 * separate instantiation and binding phases (or another way to allow asynchronous binding)
     73
     74Could use:
     75
     76Doesn't care:
     77 * mutable templates
     78 * xml:base handling
     79 *