Thanks Niphlod. May I know where I can pick up the examples?
Appreciate your help on this.
On 19 Apr, 2013, at 3:13, Niphlod <niph...@gmail.com> wrote:
> packed an app with a few examples: might explain better how to deal with
> timezones.
>
> On Thursday, April 18, 2013 6:20:18 PM UTC+2, fun man wrote:
>>
>> yes. I am with you. I didn't store timezone in the db, and will be using UTC
>> for all input to the db too.
>>
>> I hope to find a way to use the detected timezone to use in the .represent
>> method for the sqlform.grid.
>> db.prototype.modified_on.represent = lambda value, row :
>> pytz.UTC.localize(value).astimezone(pytz.timezone('Asia/Tokyo'))
>>
>> The above is working for me. I basically hardcode it to 'Asia/Tokyo'. I am
>> trying to get the value from your plugin to replace my hard coded one above.
>>
>>
>> On Fri, Apr 19, 2013 at 12:41 AM, Niphlod <nip...@gmail.com> wrote:
>>> the whole point of timezone normalization is NOT having "a timezone
>>> attached at the end".
>>> It's storing in the database as UTC and displaying as "localized" to the
>>> users.
>>> Are we sure that you fully grasped what the timezone implementation on the
>>> IS_DATE* validators in web2py and that that idea fits with your one ?
>>>
>>>
>>> On Thursday, April 18, 2013 4:35:51 PM UTC+2, fun man wrote:
>>>> i am not using any specific language translation. It should be the default
>>>> language.
>>>>
>>>> i also think that it is timezone issue, but not very sure how to do the
>>>> normalization. The model i use is Field('modified_on', 'datetime'),
>>>> I see that there is no timezone attached at the end.
>>>>
>>>>
>>>> On Thu, Apr 18, 2013 at 7:11 PM, Niphlod <nip...@gmail.com> wrote:
>>>>> that seems more a problem with the format of the date than the fact that
>>>>> it has to be "timezone-normalized"....what language translation are you
>>>>> using ?
>>>>>
>>>>> PS: what I meant with "landing page" is that you're sure that the user
>>>>> will hit that page before arriving to the form.
>>>>> If you are sure, there's no need to embed the LOADed fragment in the form
>>>>> page
>>>>> --
>>>>>
>>>>> ---
>>>>> You received this message because you are subscribed to a topic in the
>>>>> Google Groups "web2py-users" group.
>>>>> To unsubscribe from this topic, visit
>>>>> https://groups.google.com/d/topic/web2py/aV1nNiDIwiY/unsubscribe?hl=en.
>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>> web2py+un...@googlegroups.com.
>>>>>
>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "web2py-users" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/web2py/aV1nNiDIwiY/unsubscribe?hl=en.
>>> To unsubscribe from this group and all its topics, send an email to
>>> web2py+un...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
> --
>
> ---
> You received this message because you are subscribed to a topic in the Google
> Groups "web2py-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/web2py/aV1nNiDIwiY/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to
> web2py+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
> <web2py.app.fun_man.w2p>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
