https://bugs.gpodder.org/show_bug.cgi?id=930
--- Comment #5 from flansuse <[email protected]> 2010-03-15 16:37:30 GMT --- (In reply to comment #4) > (In reply to comment #3) > > What if a user, such as myself, disables the auto-cleanup > > feature, but the Downloads section becomes populated with many completed > > downloads that have already been acknowledged? There will be no way to clear > > the Downloads list, short of exiting and restarting gPodder, entirely. > > I've been thinking of maybe showing the button in case this advanced option is > enabled (and not acting like a "toggle" button, but rather like the old push > button). An alternative would be to add a new item in the (right-click) > context > menu. That's actually a simple, yet intuitive idea. The "normal button" behavior works better in this case. I can tell you already I am one of those users who will enable the advanced option to disable auto-cleanup, and simply remove/cleanup manually. As for the right-click context menu, it would be inconsistent to have it without a complementary button. This is akin to having a "Sync" menu item from the tray icon, but nowhere else in the main application's UI. > > It might also seem strange for a user, especially one who is new to > > gPodder, to > > see a handful of completed downloads suddenly vanish after "switching" to > > the > > Downloads tab. If clicking on the Downloads tab triggers the "cleanup" > > event, > > there might be a short delay, in which the user might notice that > > "something" > > happened, but he's not entirely sure. "Did some things just disappear? Were > > those errors? Were those completed downloads? Did those get canceled?" > > Yes, we will make it so that this does not happen (i.e. switching "to" the > downloads tab will have it look like it's gone, and not like it's just being > removed from the list). I've seen this in iTunes, and it's pretty neat. I > think > users will "get" it. This auto-cleanup will then obviously not remove failed > downloads, but only finished and cancelled ones: > > * Finished downloads do not require the users's attention, > and (s)he can see the result of the download in the UI > * Downloads are only "cancelled" based on user interaction, > so the user knowingly cancels a download and can expect > it to be removed from the list. > > I think cleanup should never remove failed downloads, something that is done > at > the moment. If the download failed, the user should be confronted with it and > deal with it (either cancel/remove manually or re-start if (s)he thinks the > problem was just temporary). I believe finished downloads and failed downloads are equally important to certain users. I will use Firefox as an example: If I begin downloading many different files with Firefox, I might lose track of what I had tried to download and what actually saved to my hard disk. In order to double-check, I can refer to the Downloads window and recall what is finished downloading. Otherwise, if the Downloads window auto removes completed downloads from the list, I would have to navigate to the folder (or folders) where I had told my browser to save the files in order to verify and recall what is complete. The same can apply to gPodder, similarly. In gPodder's case, instead of "folders" you have "podcast series". The same concept applies. This is not such a concern for users with very few podcasts who download very few episodes. It really applies to those with many subscribed podcasts and many downloads. I am not familiar with how iTunes deals with this, but it does sound interesting by the way you described it. (No delay in the list being cleared, so no confusions about "What just happened?") > What are your thoughts on this? I'm going to implement this soon, and any > potential issue would be nice to have been discussed, so that the final design > is usable and provides an improvement in the eyes of our users :) I think you've got the right idea going on. A combination of simplicity, with the ability to have more control via an advanced option! Good defaults for most users that yields a cleaner UI, yet other users are not neglected if they wish to use a more controlled approach to managing their podcasts. Sounds good! Here is a recap of what I've gotten so far: * By default, there is no cleanup button. * If the user is watching the Downloads tab, nothing gets removed. (Even completed downloads remain in the list.) Or is that incorrect? If the Downloads tab is the active tab, then the completed downloads are cleanup up automatically anyways? * If the user clicks on the Downloads tab, then the finished downloads are cleaned up from the list without a delay that might cause confusion. * There will be an advanced option to disable auto-cleanup, which will also enable the "Cleanup" button. The "Cleanup" button will not toggle, but instead act like a normal button. * Whether or not the advanced option is enabled, failed downloads will not be cleared from the list. * There will be a button labeled "Refresh" which will actually delete all downloaded episodes and unsubscribe from all podcasts. (Maybe you should wait until April 1st to implement this one?) -- Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
