---- Reported by adam@yorba.org 2012-01-06 13:59:00 -0800 ----

Original Redmine bug id: 4570
Original URL: http://redmine.yorba.org/issues/4570
Searchable id: yorba-bug-4570
Original author: Adam Dingle
Original description:

The Geary engine should live in a separate shared library from the graphical
user interface code. This will allow us (or others) to develop multiple user
interfaces that use the engine.

Related issues:
related to geary - Feature #6354: Start notifying of new mail at session
startup (Open)
related to geary - Feature #6010: When "Compose Message" is selected via
external means, on... (Open)
related to geary - Feature #5129: undo send (Open)
duplicated by geary - 5857: Separate UI and daemon (Duplicate)



---- Additional Comments From geary-maint@gnome.bugs 2013-11-14 17:18:00 -0800 ----

### History

####

#1

Updated by Adam Dingle over 1 year ago

  * **Assignee** set to _Eric Gregory_

####

#2

Updated by Eric Gregory over 1 year ago

Just to update this ticket, we've taken two approaches that come close to
implementing this:

  1. Geary's engine is now compiled as a static library. This was to fix a compilation bug, but could be easily adapted to build a dynamic library from the static lib.
  2. We now have a "gearyd" executable, which implements a DBus server. It's far from complete, but if we did complete it, it might eliminate the need for a shared library.

####

#3

Updated by Adam Dingle over 1 year ago

  * **Assignee** deleted (<strike>_Eric Gregory_</strike>)

####

#4

Updated by Jim Nelson about 1 year ago

  * **Category** set to _engine_

Requested as well at https://bugs.launchpad.net/geary/+bug/1053205

####

#5

Updated by Jim Nelson about 1 year ago

  * **Subject** changed from _split Geary engine into separate shared library_ to _split Geary engine into separate shared library or background daemon (DBus service)_
  * **Target version** set to _0.3.0_

Enough requests have been made for Geary to run in the background that I've
added such a feature to this ticket's title.

####

#6

Updated by Jim Nelson 10 months ago

A poor-man's solution would be to set Geary to run at login and hide the main
window. Geary would notify of incoming mail as normal. When the user "ran"
Geary, the window would instantly appear with the most current mail ready to
read. When the user closed Geary, it would hide the window again.

Of course, some users don't like applications running in the background, but
pragmatically speaking, this is not terribly different than running Geary as a
background daemon that the client connects to via DBus. We should have some
way for the user to force Geary closed and, of course, for them to configure
Geary not to start at login.

####

#7

Updated by Jim Nelson 10 months ago

  * **Target version** changed from _0.3.0_ to _0.4.0_

####

#8

Updated by Jim Nelson 8 months ago

  * **Target version** changed from _0.4.0_ to _0.5.0_

####

#9

Updated by Jim Nelson 7 days ago

  * **Target version** deleted (<strike>_0.5.0_</strike>)



--- Bug imported by chaz@yorba.org 2013-11-21 20:22 UTC  ---

This bug was previously known as _bug_ 4570 at http://redmine.yorba.org/show_bug.cgi?id=4570

Unknown version " in product geary. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution