W3C home > Mailing lists > Public > public-sysapps@w3.org > June 2013

Re: Alarm API: ignoreTimezone/respectTimezone

From: Marcos Caceres <w3c@marcosc.com>
Date: Tue, 4 Jun 2013 17:41:43 +0100
To: Marta Pawlowska <m.pawlowska@samsung.com>
Cc: Mounir Lamouri <mounir@lamouri.fr>, public-sysapps@w3.org
Message-ID: <E363B09077EB4D98899C3EE0235E5676@marcosc.com>


On Tuesday, June 4, 2013 at 3:33 PM, Marta Pawlowska wrote:

> Hello Mounir,
> I would like to add my 2 cents...
>  
> 1. ScheduleTask object
> I like this idea most, however I would add default timezone identifier (I agree with Marcos here). I understand that we want to make sure that developers will think about their intentions, but it might be inconvenient/irritating, especially if in most cases they will use current timezone. Moreover I would like to change timezone identifiers names: "current" to "CurrentTimeZone" and "none" to "ignoreTimeZoneChanges" (I prefer to use "ingnore...Changes" over "no..." or "none" since it would be self-explanatory to me).

IMO, if we do get agreement to go optional, it would be nice to have this as:

{timezone: timezone | none | current }  

Less typing and legible (and no need for uppercase letters) - I also like none, because it's a nice carry over from CSS. So, some examples:

new ScheduledTask(date, {timezone: "GMT+1"});

var props = {timezone: "PST", data: {...}}
new ScheduledTask(date, props);



new ScheduledTask(date, {timezone: "none"});

and so on…  
Received on Tuesday, 4 June 2013 16:42:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:13 UTC