Too long time for status popups

[reox]

Is your suggestion for improvement related to a problem? Please describe.

I'm using the 5.x snapshots of JabRef.

My usual workflow for adding articles is like this: copy DOI, go into JabRef, press Ctrl+N, Press Ctrl+V, Enter, Press Alt+F7, Press Alt+F8.
I also have auto-saving activated.
When I do this, I see a lot of status popups / messages at the bottom, i.e.

Saving library...
Saved library 'file.bib'
Adding new 'Article' Entry
Saving library...
Saved library 'file.bib'
Saving library...
Saved library 'file.bib'
Looking for full text document...
Saving library...
Saved library 'file.bib'
finished full text document download for entry Foo
Saving library...
Saved library 'file.bib'
Doing a cleanup for 1 entry...
Saving library...
Saved library 'file.bib'.
Saving library...
Saved library 'file.bib'.

each of the popups stays for about 3 seconds, so the process of adding a new entry, which took me like 5 seconds will not produce popups for about the next minute.

Describe the solution you'd like
Usually I do not care about messages when saving and have the library saved. In my opinion there should be a message if it has failed but not for every auto-save action. Maybe when auto-saving is enabled, there should be no message, only if manual saving is requested.

Next, the duration is too long for certain actions. I.e. if you are looking for the text document, there should be a message saying "I found one, downloading..." (right now the user has no information that a document was found and sometimes the download takes some time) which will cancel the previous notification. Also if the document is downloaded, the message could cancel the previous one, as it made the previous notification irrelevant.
From a usability point of view, the message should be shown when the action is taken. Using a message queue is IMO only helpful when the action and message are not time related.

If all the messages are important, then a log or list of messages would probably be better or maybe stacking them into a single popup - but as you might see with the number of messages right now, this would fill up quite easily.

[tobiasdiez]

Agree. Especially, the auto-save should never display a notification.

[Ka0o0]

Hello,

If the issue is still not addressed, I would like to contribute.
For me the requirements were a bit unclear, so I tried to make myself my own picture in regards to notification. For me, it feels like notifications are used quite often.
Sometimes, I think they might be obsolete, as either the default expectation of a user is reported or changes are directly visible in the UI.
I summarized my questions below.

Regardless of my questions, is there any specification on how the expected behavior should be like upon which I could orientate?

Thanks in advance

---

• Is Preferences recorded in PreferencesDialogViewModel obsolete? User would expect that this happen, and should we only show a notification in error case?
• Is Closed library in JabRefFrame obsolete? Is directly represented in the view.
• Is New library created in FromAuxDialog obsolete?
• In all actions, should the going to do something message be replaced with a progress bar and one final notification? Actions might take long, and any thoughts about hindering the user from messing with the DB during operation?
  • SaveAllAction
  • ExportCommand
  • CleanupAction
  • GeneratingBibtexKeyAction
  • DuplicateSearch
• This action requires one or more entries to be selected notification looks the same as a successful notification. Should the action be disabled in the menu bar?
  • Additionally, when using Cmd + C no such popup is presented
• Is Saving library obsolete? Maybe short spinner.
• In AttachFileAction, This operation requires exactly one entry to be selected, can the action be disabled?
• Are the messages in ToggleUnionIntersection obsolete? It is directly represented in the view.
• Is Added group obsolete?
• Is Modified group obsolete?
• Is Removed group obsolete?
• Is Files opened obsolete?
• Is File already open obsolete? Could we just switch to the tab of the opened file?
• Can Opening file be replaced with a progress bar or spinner?
• Is Opened database obsolete? Directly visible in UI.
• Is the Connection lost notification obsolete, as there is a popup with the same text right afterwards anyway?

[tobiasdiez]

Thanks for the throughout analysis. The notifications should be shown only if there is no visible change (or the change might be so minimal that users don't notice them). Thus, I agree with the items you listed except for the following:

• Preferences recorded although expected, there is no visible feedback and it doesn't hurt to notify the user about a successful action.
• Notifications related to the groups, as these changes might be small and easily missed if you have large group trees

I also like the idea to replace the progress notifications by some spinner and/or progress bar. Not sure however how easily this can be implemented.

[reox]

I also like the idea to replace the progress notifications by some spinner and/or progress bar. Not sure however how easily this can be implemented.

Do you know Darktable? I think they have a nice system implemented: They use stackable progressbars and system notifications.
So if you do some things after each other, the progressbars will stack up. If one item is finished you get a notification into the system bus (depending on your OS and bus system you use).

[Siedlerchr]

I think eclipse also has this multiple progress bars window for tasks to be performed

[Ka0o0]

Okay I think there are multiple tasks here:

• Remove obsolete notifications (This issue)
• Implement Spinner/Progress notification for longer tasks
• Disable actions that are not possible (Options should be inactive or show Error or Information Box #4795 and koppor#156)
• Do not show notification for automated saving task (This issue)

To keep this issue as small as possible, I would suggest we just remove the obsolete notifications and disabling notifications for automated saving for this issue, add another UI improvement issue for the spinner and another for disabling not possible actions. What do you think @tobiasdiez ?