After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 713187 - Background process reporting
Background process reporting
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: engine
master
Other All
: High normal
: 0.14.0
Assigned To: Geary Maintainers
Geary Maintainers
: 714727 766546 (view as bug list)
Depends on: 730712
Blocks:
 
 
Reported: 2013-05-22 10:04 UTC by Jim Nelson
Modified: 2021-07-05 13:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 20:18:59 UTC


---- Reported by jim@yorba.org 2013-05-22 15:04:00 -0700 ----

Original Redmine bug id: 6985
Original URL: http://redmine.yorba.org/issues/6985
Searchable id: yorba-bug-6985
Original author: Jim Nelson
Original description:

(This was initially described in #6963)

Our current design to is implement "processing" signals on Folder, Account,
and Engine. The common signal parameters are a notification type (Background
Sync, Database Update, Search Processing, Sending Email, Connecting, and a
generic Activity notification), a state enum (Start, Progress, Stop), a
percentage field of some kind for Progress, and a tag to indicate
Start/Progress/Stop pairings.

In addition, each container (Account, Engine) aggregates the objects it holds
as a convenience to the client. Thus, the Account "processing" signal includes
a nullable Folder parameter, and the Engine "processing" signal includes a
nullable Account parameter. (It's possible in the future Engine will do its
own background processing.)

Since some of these notifications can come in parallel, each object in the
heirarchy will have a ProcessingTracker which does the bookwork of tracking
pairs and supplying relevant information, i.e. the number of active processes
per type, the aggregate percentage per type, and maybe even an overall
aggregate percentage and a simple boolean "is_processing" field.

With this in place, the client can then get specific information about what
objects are busy (Account, Folder, #4654) as well as a simplified result
("is_processing") for the current spinner (#4644), while not precluding other
indicators where displaying a percentage is desireable (during the search
upgrade, which is what this ticket covers). This system is flexible enough
that all background processing can report their status at any time.

Related issues:
related to geary - Feature #4654: display progress spinner in pane(s) where
information wil... (Open)
related to geary - 4644: spinner should spin as messages are loaded (Open)
related to geary - 6963: display progress to user while performing
database upgrad... (Fixed)



---- Additional Comments From geary-maint@gnome.bugs 2013-09-04 17:42:00 -0700 ----

### History

####

#1

Updated by Jim Nelson 5 months ago

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

####

#2

Updated by Jim Nelson 3 months ago

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



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

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

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 

Comment 1 Michael Gratton 2016-05-17 04:14:59 UTC
*** Bug 766546 has been marked as a duplicate of this bug. ***
Comment 2 Michael Gratton 2017-12-07 23:45:28 UTC
See https://wiki.gnome.org/Apps/Geary/Design/Notifications for some design ideas for this.
Comment 3 Michael Gratton 2018-04-13 01:46:44 UTC
*** Bug 714727 has been marked as a duplicate of this bug. ***
Comment 4 GNOME Infrastructure Team 2021-07-05 13:27:36 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/geary/-/issues/

Thank you for your understanding and your help.