Lack of feedback when links clicked
Bug #308108 reported by
GreenReaper
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Wikipedia Dump Reader |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
On restricted-CPU environments and slow storage, it can take several seconds to open a link. In this time, the app is frozen. There should be some indication that it is working on loading the link.
Ideally the page would be displayed blank first, and then filled in (this requires that links actually open in the current window - see Bug #308107). If rendering is taking the time (although I suspect it is the unbzipping from flash), a single page of text could be rendered before the others so that the user has something to read.
Changed in wikipediadumpreader: | |
status: | New → Confirmed |
To post a comment you must log in.
Hi,
Thanks for the report,
The loading is slightly long, and scale linearly IIRC, because the indexation is not the smartest possible way, as i benched a good compromise between speed and index-size (for example, using a SQLlite indexation doubled the size of the index, while not improving speed that much). Note that i tested on a usual hard-drive, where streaming is fast.
Regarding the feedback, i just commited cursor change, which can give visual feedback that the app is busy (frozen).
(I don't plan to use threads yet as i feel it adds unecessary complexity and wanted to keep the reader small. Not that having an empty blank page replacing the user's current text would definitely upset him)