Why not just use the existing overlay interface (cal and TT columns) for authenticated users?
> (1) designing the user interface for this (which calendars should be > overlaid and where? Can the anonymous user decide by > himself/herself, or is it a decision made by the site > administrator?) Regarding the existing overlay interface: I like that the administrator chooses which calendars a user can overlay, if any, and that the user can choose of that list which she actually views. Scenario #1: An organization is allowing a calendar to be viewed without a password. This calendar is maintained by the authenticated user. This being a public calendar, chances are that the calendar maintained is not their personal calendar. If they were vehemently opposed to giving unauthenticated users access to overlays they probably wouldn't mind sacrificing the overlay view while logged in because it's not their personal calendar anyway. Scenario #2: An organization is allowing a calendar to be viewed without a password. This calendar is maintained by a number of users that have sufficient rights to do so. If they were vehemently opposed to giving unauthenticated users access to overlays they definetly wouldn't mind sacrificing the overlay view to the authenticated user because no one logs in as the authenticated user. Doesn't it make sense to give this existing feature to unauthenticated users? What do you think? Thanks, Peter On 12/12/05, Marius Gedminas <[EMAIL PROTECTED]> wrote: > On Sat, Dec 10, 2005 at 10:12:06PM -0500, Peter Hartmann wrote: > > I'm sure someone must have asked this but , is there a way to keep the > > overlay feature when viewing a calendar from the "unauthenticated > > mode"? > > It is a matter of > > (1) designing the user interface for this (which calendars should be > overlaid and where? Can the anonymous user decide by > himself/herself, or is it a decision made by the site > administrator?) > > and > > (2) writing some code to implement (1). > > The first part is more difficult. You could help here, by coming up > with a description of the UI, and creating a wishlist issue on > http://issues.schooltool.org/. > > Note that even if you did come up with great UI, the core developers > (that's us) probably wouldn't have time to implement it in the near > future. > > > This would be really useful for the parish and school public > > calendars. The situation is this: we'd like to have a calendar just > > for church holidays/saints days. We'd like to overlay that holiday > > calendar on both the parish calendar and school public calendars since > > these events apply to both. It would be a pain to enter this stuff > > twice and it would be cool to uncheck it to relive the clutter. I > > really don't want to force people to sign in to see a pubic calendar. > > That sounds like a reasonable use case. > > Marius Gedminas > -- > Never assume the reader has read the subject line. > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQFDnfEBkVdEXeem148RAt9GAJ9Vg+/yvmhII+C4XDsrGSbu7DKNnwCcCA89 > 1uzrvM7w58yfIMCYdA+emXE= > =hqm8 > -----END PGP SIGNATURE----- > > > _______________________________________________ > Schooltool mailing list > [email protected] > http://lists.schooltool.org/mailman/listinfo/schooltool > > > _______________________________________________ Schooltool mailing list [email protected] http://lists.schooltool.org/mailman/listinfo/schooltool
