On Wed, 2005-03-02 at 16:40 -0500, Jeffrey Stedfast wrote: > perhaps you'd like to enlighten us on how to set off calendar alarms > without having any processes running?
I don't expect you to set off alarms when the process isn't running. This might sound strange, but it hadn't even occurred to me. I only need the alarms when evolution is actually running. Having said that, it makes sense to have a background daemon... which should be optional. Especially when the alarm daemon takes 60MB of RAM, and the data server takes over 70MB. I suppose I can live with the background process, but it shouldn't take that much memory to run a simple alarm server. For appointments that show up in the calendar panel applet, that should not require a background process after evolution quits. No changes are going to happen to the schedule while I'm not logged in to evolution. Also, it should be possible to --force-shutdown from a shell without DISPLAY being set. Should I file a bug for this, or is it by design? > I'd say it is pretty robust. Evolution is pretty robust... but Connector is not. Lots of random crashes and usability issues. It has come a long way, but I'd rate evolution proper to be production quality, while Connector is definitely still beta. It's come a long way though, and I know the team is working hard on it, so I'm still happy to use it. Raul _______________________________________________ evolution maillist - [email protected] http://lists.ximian.com/mailman/listinfo/evolution
