Hi Anders, thanks but I don't want to make the calendars public. I
store the login details on a database and just want to be able to
login/create a session automatically. I'm basically just trying to use
the cool component to display a users daily events. The user doesn't
need to know that they're logging into a google calendar but I just
don't want to have to redesign the wheel on the calendar component.

On Nov 2, 7:30 pm, Anders <[email protected]> wrote:
> Perhaps make sure each calendar is listed as public (through the
> calendar settings).  I got this to work this way, but couldn't do it
> via my web application (had to manually go to each calendar).
>
> On Nov 2, 8:28 am, jbeat <[email protected]> wrote:
>
>
>
> > Hi all, i'm try to do some basic linkups between a web application and
> > google calendar.  I have one single username/password for google
> > calendar but i create multiple sub calendars for each site user. I can
> > create and update events etc on the backend but i really want to avoid
> > the google login screen that appears when i first request the google
> > calendar view via iframe. I was hoping the authentication might have
> > given a few pointers but now joy. AuthSub seems to be more concerned
> > with not having to handle the client login details at all(?) but what
> > i really need to just to ensure that people dont have to login twice,
> > once from my system then a second time for google calendar. I dont
> > even want/need the users to know the google account login details at
> > all? none of the calendars need to be hidden from other calendars
> > under the same login details.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to