Actually, webContent would be displayed in the event, so if you create a webcontent displaying the local time, based on the extendedProperty value,
you would in fact be seeing this on the calendar.

Thinking about it, you might not need the extendedProperty. The webContent could just hold this in it's xhtml content. Or, if you prefer a generated gif, you need the extendedProperty.

Frank

On 10/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Thanks Frank.

Frank Mantek wrote:
> The calendar team is aware of that issue, but i am unaware currently if
> there is a resolution on this. I will forward and come back to you on that.
>
> With the event organisation this makes sense. You know though, that, at
> least using the API, you can fix this yourself? Would that help for now?
>
> The way to fix this (drumroll):
>
> -> use an extendedProperty to store the local eventtimezone offset
> -> use a webContent property for the event to display the local time
>
> That should work
>

Sorry, I don't quote understand that. How does it help for a user who
finds the Calendar using the standard public calendar search, and then
views it using the standard Google Calendar facilities?

John Walton



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi
-~----------~----~----~----~------~----~------~--~---

Reply via email to