- From: Dimitri Glazkov <dglazkov@chromium.org>
- Date: Thu, 30 Jun 2011 14:10:52 -0700
- To: Maciej Stachowiak <mjs@apple.com>
- Cc: public-webapps <public-webapps@w3.org>
On Thu, Jun 30, 2011 at 10:59 AM, Maciej Stachowiak <mjs@apple.com> wrote:
>
> On Jun 29, 2011, at 9:08 AM, Dimitri Glazkov wrote:
>
>> Hi Folks!
>>
>> With use cases (http://wiki.whatwg.org/wiki/Component_Model_Use_Cases)
>
> So I looked at this list of use cases. It seems to me almost none of these are met by the proposal at <http://dglazkov.github.com/component-model/dom.html>.
>
> Can you give a list of use cases that are actually intended to be addressed by this proposal?
The main purpose of this API is to provide authors the ability to
create shadow DOM subtrees -- as a first step toward addressing the
use cases. I realize that we need to resolve the issue of multiple
shadow subtrees before we can proceed any further.
>
> (I would be glad to explain in more detail why the requirements aren't satisfied in case it isn't obvious; the main issues being that the proposal on the table can't handle multiple bindings, can't form controls, and lacks proper ("type 2") encapsulation).
>
> These use cases are also, honestly, rather vague. In light of this, it's very hard to evaluate the proposal, since it has no obvious relationship to its supporting use cases.
Alex Russell is working feverishly to provide awesomer use cases.
>
> Could we please get the following to be able to evaluate this component proposal:
>
> - List of use cases, ideally backed up with very concrete examples, not just vague high-level statements
> - Identification of which use cases the proposal even intends to address, and which will possibly be addressed later
> - Explanation of how the proposal satisfies the use cases it is intended to address
> - For bonus points, explanation of how XBL2 fails to meet the stated use cases
Working on that.
>
> Regards,
> Maciej
>
>
Received on Thursday, 30 June 2011 21:11:48 UTC