Click on
http://groups-beta.google.com/group/Google-Calendar-Users/web/google-calendar-suggestions?hl=en
- or copy & paste it into your browser's address bar if that doesn't
work.
http://groups.google.com/group/Google-Calendar-Users/web/google-calendar-suggestions
I started a couple "test" calendars to see which I could get
synchronized the best with my other calendar applications, and now
that I have one I like, I'd like to make that test calendar my primary
instead of trying to reset my synchronizations to use the "official"
primary calendar.
· Add, Update and Delete Events.
· Access a complete list of Calendars (including Shared or Imported
Calendars).
· View Calendars by Day, Week or Month.
· Color Schemes match your Google Calendar preferences.
· Google Calendar -- security and user privileges.
· Functional on most mobile devices (PDA's, Blackberry's, Phones
etc).
· No software to download.
Beta testing is underway. You can begin using this application at
http://www.mobilegcal.com
Ability to give a starting date, e. g. for an event "my birthday":
07.02.1974. Then, in following repeating occurrences the time
difference could be stated like "my birthday (33 years)".
I think it should be more generic. I would like the occurrence number
to be displayed, whether the event is scheduled to repeat weekly,
monthly or annually. This way, the person's age will equal the
occurrence number, provided the start date is his date of birth.
Taking this idea even further, what about a set of simple parameter
values and functions that one can place in any field in the event,
e.g.
I'd want to put %RECURRENCE_NUMBER% in both the event summary, as well
as the event details. Maybe I'd want %DateTime("2007/12/25") -
DateTime.Now% in the summary to show me the number of days left till I
get my Ferrari :)
The experts can decide on the syntax, but I think a basic set of
functions built on an existing framework would be very useful.
Thje event begins at 8am and ends at 5pm, but have a break from 1pm to
2pm
Got it ?
Sorry if my english is wrong!
This could be used for Anniversary dates as well.
The flexibility of this idea makes it even better.