Summary | Progress feedback for the ICS import |
Queue | Kronolith |
Queue Version | Git master |
Type | Enhancement |
State | Accepted |
Priority | 1. Low |
Owners | |
Requester | shop (at) open-t (dot) co (dot) uk |
Created | 04/02/2012 (4790 days ago) |
Due | |
Updated | 08/20/2013 (4285 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
over the last years takes a very long time (why is that?) and a
progress bar of some kind would be greatly appreciated.
entries for anybody. The very fact that the import procedure has
absolutely no feedback (be it that it succeeds or fails) is a
significant UI problem.
State ⇒ Accepted
Priority ⇒ 1. Low
Priority ⇒ 3. High
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Progress feedback for the ICS import
Type ⇒ Enhancement
State ⇒ New
user to know what is happening. I've just finished importing a 4819
entries calendar - which took about 15 minutes. Now this is all fine -
but the only way I knew this was the case was by watching the table in
the SQL back end. A regular user would have been left staring at an
empty calendar, having no idea if the import is happening, is failing
etc. They would have most likely restarted the process 5 times over
thinking that it isn't working - and messed up the whole thing.
This could be implemented either:
1. As a generic message - something like "The import process could
take a long time, after which the events will show up in the calendar.
It is OK to continue using Horde applications in the meanwhile". This
should be easier to implement, but not that useful to the user
(however, more useful than nothing).
2. As a progress display in the Kronolith interface - showing how much
of the ICS file has already been processed. This could lock the entire
interface during the import - or just display in a corner while the
interface is still usable.
Either of the above would make the ICS import process a lot more
usable to regular, end users, than it is now. At the moment -
specially with larger calendar sets - it is close to impossible for
users without access to the back-end to make use of it.