Forum OpenACS Development: Calendar about to break hard
Over the past few months, I've slowly been rebuilding chunks of
calendar, specifically recurring events, no-time events, scoping, and
all the display widgets. I've done so with parallel Tcl procs that do
not interfere with the way the main calendar package works. If you've
tried dotLRN, you've seen some of this stuff already.
I'm now about to take a chainsaw to the calendar package (*NOT* for
v4.5) and rebuild the Tcl pages based on this new structure I've been
putting together. This is going to take a while, and it will probably
break the PG version for up to 2 weeks in the CVS development branch.
This is one of these dreaded cleanup efforts that is highly necessary.
Please let me know ASAP if you have any objection to my breaking the
calendar CVS tree for the next 2 weeks. I'd rather not break things,
but I also like to commit my work often.
That's my opinion, anyway!
Thanks for letting us now.
Two of my studennts will start working on calendar (as we have discussed on email) in about 4 weeks.
One of them will hopefully add alerts (email and and now maybe SMS) to it.
Outlook synchronization with Calendar?
sync'ing to Outlook taken from ACES. However, complete
synchronization is not currently scoped. Rafael had mentioned
that his team might do something in that respect.
What's mostly needed is to make the calendar package bright about timezones. Once that's done, it wouldn't be too difficult to extract that and build the timezone definitions and references required in iCalendar format.
The single event synch stuff only works because after experimentation I figured out that in practice Outlook only requires timezone info for recurring, not single, events.
It's been literally 8 or so months since I read the iCalendar spec by I think timezone defs are in theory required, Outlook's just a bit more forgiving so we were able to slip in that feature without fairly large-scale rewriting of the ACES calendar package.
upload events from Outlook into Calendar?
They should start working on it in the next few weeks, although they first need to read and learn a bit more about OACS.
think this should probably be implemented using user-
preferences. But this won't be done as part of the overhaul
(which is almost done now).
Do you mean a service contract so that calendar can "notify"
other packages when their events are due, etc...? Kind of like a
programmatic scheduled jobs?
The task list can tell the calendar to display the due date of a task in the calendar view.
Like Yahoo's "My Time Guides": Lets you put holidays or club events or other things into your calendar.
But it'd be nice if it didn't require that you actually insert rows into the calendar tables. They can stay where they are, but calendar, when it displays the day/week/month/year/whatever view just includes those items.
items should just *map* acs_events to a calendar. Then you can
extend acs_events to do exactly what you mention, except
calendar doesn't need to perform multiple queries to find all the
events, it can just query the acs_events table.
The issue which remains is then what happens if you want to
have your data type extend something *other* than acs_event,
but I'm thinking this is a small subset of cases... Thoughts?
So Calendar was about to break hard for two weeks back in May. Did this work ever get finished? I am using the 4.5 calendar module and I either need to fix the annoying bugs or upgrade. If I have to fix bugs, I would rather them be in a future module. Ben, any way I can help?
I will upload my files to OACS in the very near future.
- Jamie Hill