Re: Rough first draft of Level 0

Hi:

This may be nit-picking ... but I am wondering what if anything we should
do about partial support of an API in level 0. For instance, not all
Canvas2D APIs are supported currently by mobile vendors - especially those
related to pixel manipulations. OTOH these are not commonly used APIs
either. Do we pick and choose what may be relevant to Level 0 in such cases?

Regards,
Mansoor
TI



On Wed, Mar 28, 2012 at 9:57 AM, Robin Berjon <robin@berjon.com> wrote:

> Dear all,
>
> please find the (very) rough draft of "Core Mobile Web Platform — Level 0"
> at the following URL:
>
>    http://coremob.github.com/level-0/
>
> A lot of it is still in flux, notably we need to check that some of those
> features are really at level 0 and not 1. Also, a number of things that
> should be in there are missing (notably details about what to support from
> HTML for instance, or some parts of CSS modules).
>
> As you can see there are a bunch of issues. You are invited to voice your
> opinion on those here (and, of course, on any other feedback you may have).
> Please read the "Philosophy" section before commenting on any of the rest,
> it's not meant to be fluff. I haven't had time to update the references DB
> with all the missing references as well as to update the out of date links
> that it has.
>
> If you feel like getting your hands dirty, the repository is at:
>
>    https://github.com/coremob/level-0/
>
> So go ahead, fork, and make pull requests. It is important to note that
> the branch in which the real stuff happens is gh-pages (*not* master).
>
> Share and enjoy!
>
> --
> Robin Berjon - http://berjon.com/ - @robinberjon
>
>
>