Written by tliketea the 26 Jun 09 at 12:41.

So:
1. either allow users to deselect Evolution during installation or
2. allow users to select other default PIM

P.S.: didn't know if it should go into "installation" or "office", because PIM is "office" I put it here

So: 1. either allow users to deselect Evolution during installation or 2. allow users to select other default PIM P.S.: didn't know if it should go into "installation" or "office", because PIM is "office" I put it here

Written by cheesehead the 26 Jun 09 at 15:50.

Use a dbus deamon or library or other layer to handle e-mail or PIM access. HAL is a good analogy. The handler knows which PIM application you use, and converts calls from other applications into calls to the PIM's API.

Other applications don't need to call Evolution (and evolution-data-server) directly, they just call the handler. Other applications don't care what PIM you use, they just call the handler.

This could replace evolution-specific dependencies from many packages. That would make removing evolution much easier

Different e-mail and PIM applications have quite different capabilities and APIs, so the handler might be fairly complicated - particularly to deal gracefully with errors and failures.

Use a dbus deamon or library or other layer to handle e-mail or PIM access. HAL is a good analogy. The handler knows which PIM application you use, and converts calls from other applications into calls to the PIM's API. Other applications don't need to call Evolution (and evolution-data-server) directly, they just call the handler. Other applications don't care what PIM you use, they just call the handler. This could replace evolution-specific dependencies from many packages. That would make removing evolution much easier Different e-mail and PIM applications have quite different capabilities and APIs, so the handler might be fairly complicated - particularly to deal gracefully with errors and failures.