Thanks for the example Ray. I'm not able to replicate that behavior quite yet, but it will help me refine my thinking.
On Feb 10, 8:00 pm, Ray Baxter <[email protected]> wrote: > Ok, this behavior is browser dependent. > If you go to this url: > > http://www.google.com/calendar/embed?dates=20080901%2F20080904&src=ca... > > or*http://tinyurl.com/ball3z* > > in Firefox (3 - Mac), IE (7), Chrome (1.0 - ancient!), or Opera (10.0 - Mac) > you will see a calendar for August 31-October 4 with events every day. You > can navigate to any date and see the events that occur on that day. > > If you go to the same url in Safari (3.2.1 - Mac) or WebKit (yesterday's > build), you see the same base calendar, but there are only events on > Sepetember 1 - 3 (exact range might depend on your local time zone). > > Note that on the original page I referenced, there was reported to be some > problem with the rendering of the embedded calendar in Safari. That calendar > now renders, but there are still some problems with Google's support of > Safari/Webkit (or the underlying JS engines.) > > Ray > > On Tue, Feb 10, 2009 at 6:59 PM, Ray Baxter <[email protected]> wrote: > > Sorry, I see what you are saying. > > Let me do some checking. > > > Ray > > > On Tue, Feb 10, 2009 at 6:51 PM, Ray Baxter <[email protected]> wrote: > > >> As I said, "You''ll have to change the showNav parameter to 1 if you want > >> your users to be able to navigate backward and forward." > > >> Ray > > >> On Tue, Feb 10, 2009 at 6:23 PM, Eli <[email protected]> wrote: > > >>> Thanks Ray. The date range query parameter works fine for its own > >>> purpose, but that's not to designate a start date. You've disabled > >>> the forward/backward navigation so that you've explicitly limited the > >>> widget to that range which perfectly exemplifies what I don't want to > >>> happen. All I want to do is to make sure that the widget starts on a > >>> particular date, but without any constraints applied to the events > >>> that appear in the widget. > > >>> Eli > > >>> On Feb 10, 5:56 pm, Ray Baxter <[email protected]> wrote: > >>> > Try using the dates parameter with your embedded calendar. > >>> > There is an example here: > > >>> > Adding Events to Secondary Google Calendars in > >>> > Python< > >>>http://67central.com/bc/2008/09/28/adding-events-to-secondary-google-.. > >>> .> > > >>> > Scroll down for the embedded calendar. Its url is: > > >>> >http://www.google.com/calendar/embed?showTitle=0&showNav=0&showDate=0. > >>> .. > > >>> > You''ll have to change the showNav parameter to 1 if you want your > >>> users to > >>> > be able to navigate backward and forward. > > >>> > Ray > > >>> > On Tue, Feb 10, 2009 at 5:26 PM, Eli <[email protected]> wrote: > > >>> > > Googlers, > > >>> > > This subject was addressed in a post title: "specify a start date > >>> when > >>> > > embedding a calendar in a html page" > > >>> > > However, the technique that was suggested which is to use a "dates" > >>> > > querystring parameter does not appear to be the proper solution to > >>> > > this inquiry. The reason is because when you specify a date range > >>> > > only the events that occur within the range are ever visible to your > >>> > > user. Any events that occur around that range are ignored by the > >>> > > widget. That is not the desired behavior when trying to designate a > >>> > > start date. > > >>> > > Are there any other solutions? > > >>> > > Eli --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
