Tickets :: Comment on [#11126] Progress feedback for the ICS import

* Your Email Address
* Spam protection	Enter the letters below: _ _ _ ________ _ _ _ \| \| \| \| \|/ /___ / \| \| \| \| \| \| \| \| \| ' / / / \| \| \| \| \| \| \| \| \| < / / _ \| \| \| \| \| \| \|__\| \| . \ / /__ \|__\| \| \|__\| \| \____/\|_\|\_\_____\____/ \____/
Comment	> The ICS import for Kronolith calendars needs progress feedback for > the 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.
Attachment
Watch this ticket