Instant action when launching the Journal GUI

Bug #364087 reported by Ketil Wendelbo Aanensen
2
Affects Status Importance Assigned to Milestone
[Legacy] GNOME Activity Journal
Status tracked in Trunk
Trunk
Invalid
High
Siegfried Gevatter

Bug Description

ATM, when launching the Journal GUI, it takes 4-5 seconds to have it open. That is of course way too long, and there needs to be a goal.

Everyone want everything to happen instantly, so there should be formal goal on this. I propose to set the goal at something related to around 24 fps, that is ~0,05 seconds.
So, from clicking the button, it ideally shouldn't take more than 0,05 seconds to bring it to your screen.

Changed in gnome-zeitgeist:
importance: Undecided → Wishlist
Revision history for this message
Ketil Wendelbo Aanensen (ketilwaa-deactivatedaccount) wrote :

Set to high, some progress on this needs to be done before release

Changed in gnome-zeitgeist:
importance: Wishlist → High
Revision history for this message
Seif Lotfy (seif) wrote :

Maybe loading the UI then the items could be a oslution

Changed in gnome-zeitgeist:
assignee: nobody → Siegfried Gevatter (RainCT) (rainct)
Revision history for this message
Seif Lotfy (seif) wrote :

Maybe loading the UI then the items could be a solution

Revision history for this message
Siegfried Gevatter (rainct) wrote : Re: [Bug 364087] Re: Instant action when launching the Journal GUI

I'm starting to think we will need a thread for this. Looking the UI
when items are being fetched is definitely not optimal.

We should also do some more optimization work and see if we can reduce
the filtering time.

--
Siegfried-Angel Gevatter Pujals (RainCT)
Ubuntu Developer. Debian Contributor.

Revision history for this message
Seif Lotfy (seif) wrote :

the filtering has been moved form Datasink to the UI so basically it is not worth filtering out data while fetching form the datasink since it wil lslow down the datasink
thus filtering happens on the UI

Seif Lotfy (seif)
Changed in gnome-zeitgeist:
status: New → In Progress
Revision history for this message
Siegfried Gevatter (rainct) wrote :

I'm closing this as the Journal has been rewritten.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.