Forum OpenACS Development: Re: Meeting Scheduler over Calendar

Collapse
Posted by Tom Jackson on

I think we should start fresh for the reasons Don stated. Calendar does work, it just isn't worth trying to fix the problems it has. One problem I ran into is that the API requires a connection thread, this problem is impossible to remove with out a rewrite of most every page and proc.

I'm not sure a calendar should be tied to a package_id, because who wants to see different calendar content based on the package they are using? I want to see 'my' calendar, with everything on it

One other annoyance with the current calendar is that the markup used to be in .adp files (in 4.5). In 4.6 it move into library code. Nasty html hardcoded into library procedures!

Using the cr, could we design containers that would actually be things like a monthly/weekly/daily/list calendar which contains other cr items? Then the calendar package would be more flexable wouldn't it? Focusing more on a tcl api for use by other applications?