> >You need to give the user a way of picking the "current calendar" as
> >explained above. Instead of showing a list of URIs we should allow
> >the user to name the calendars so that you get a list with
> >
> > My personal calendar
> > Company calendar
> > Concert calendar from www.yourlocalsymphonyorchestra.org
> > Movie schedule from www.cinemex.com.mx
>
> Names should at least be an option; URI's are a second-best fallback.
> Naming them, however, requires a centralized database of some sort...
> (Unless you use them only to select among already loaded calendars,
> rather than allowing the user to Include/Exclude them based on their
> name.) Maybe an XML file stored in ~/evolution or a system-wide dir?
I'm concerned about how all of this fits into the Evolution shell. When
you click on a mail folder in /local, you're looking at a specific file
stored in ~/evolution/local/. Is this not the way the calendar is going
to work? That seems annoyingly inconsistent if so.
One nice fix might be calendar vfolders. Then you can have your local
calendar in /local, and remote calendars in various remote calendar
storages, and a calendar vfolder to merge them together. (And then, the
issue of "current calendar" goes away: you can't add appointments to a
calendar vfolder, you have to go to the relevant real calendar. Or
alternately, a calendar vfolder has a specific implied "current
calendar".)
-- Dan
_______________________________________________
evolution-hackers maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/evolution-hackers
