- From: Cameron McCormack <cam@mcc.id.au>
- Date: Sun, 12 Sep 2010 13:40:30 +1000
- To: Arthur Barstow <art.barstow@nokia.com>
- Cc: ext Anne van Kesteren <annevk@opera.com>, Eric Uhrhane <ericu@google.com>, Arun Ranganathan <arun@mozilla.com>, Mark Miller <erights@google.com>, Tyler Close <tyler.close@gmail.com>, Ian Hickson <ian@hixie.ch>, public-webapps <public-webapps@w3.org>, Thomas Roessler <tlr@w3.org>, Jeff Hodges <Jeff.Hodges@KingsMountain.com>
Arthur Barstow: > * Web IDL - Cameron - will you attend this meeting? I hadn’t considered it yet. Do you think there is an advantage in my attending (beyond progress that could be made on the mailing lists, once I’m back into the swing of things)? I think we should be putting a high priority on solving the issue of how arrays are exposed on the web, and whether we can still unify the WebGL typed arrays, CanvasPixelArray, Blob, and various other interfaces that take lists of things. (Whether it is possible at this point I am not sure.) One cross-group discussion point that has been at the back of my mind for a while is that of working out some shared design goals for the web platform, especially in the API space. For example, I see that the DAP interfaces quite often use property-bag-style parameters for functions. While this might be a fine design pattern in itself, it certainly isn’t consistent with the rest of the web platform. In other specs, some interfaces have [NoInterfaceObject] on them, some don’t, and I feel like there should be some general guidelines that we should be following to decide these kinds of things. I am concerned that decisions like these, made in isolation, could lead to the platform as a whole feeling less cohesive. I haven’t had time to think about this in detail at all yet, though. -- Cameron McCormack ≝ http://mcc.id.au/
Received on Sunday, 12 September 2010 03:41:45 UTC