W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: Flags for getFile/getDirectory (Re: New draft of FileSystem API posted)

From: Kinuko Yasuda <kinuko@chromium.org>
Date: Thu, 9 Sep 2010 16:18:29 -0700
Message-ID: <AANLkTimLZstpgBXCtC5_sfPDuQJx-Gezu98tz1DnPgC+@mail.gmail.com>
To: Eric Uhrhane <ericu@google.com>
Cc: Ian Hickson <ian@hixie.ch>, Darin Fisher <darin@chromium.org>, Adam Barth <w3c@adambarth.com>, Web Applications Working Group WG <public-webapps@w3.org>, Robin Berjon <robin@berjon.com>
Sounds good, going back to the original topic, I'm convinced that the
current specification (Flags object) is more JavaScript-ish and now I see no
reason to change it.

Thanks,
Kinuko

On Wed, Sep 8, 2010 at 11:03 AM, Eric Uhrhane <ericu@google.com> wrote:

> On Tue, Sep 7, 2010 at 11:13 PM, Ian Hickson <ian@hixie.ch> wrote:
> > On Tue, 7 Sep 2010, Darin Fisher wrote:
> >>
> >> Based on the ValidityState example, it seems that the members of Flags
> >> should be camelCase then instead of UPPERCASE?
> >
> > The platform convention, insofar as there is a convention, is that
> > constants are uppercase, members are camelCase, and interfaces and
> > constructors are TitleCase.
>
> I was thinking of those as constants, but really they're members, so
> yes, they should be camelCase.  I'll fix them.
>
> > --
> > Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> > http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> > Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
> >
>
Received on Thursday, 9 September 2010 23:19:22 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:40 GMT