View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004557 | MMW v4 | Synchronization | public | 2008-04-09 03:30 | 2009-02-21 05:22 |
Reporter | rusty | Assigned To | |||
Priority | immediate | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 3.1 | ||||
Fixed in Version | 3.1 | ||||
Summary | 0004557: Podcast synchronization: ability to sync older podcasts | ||||
Description | Many podcasts are best listened to sequentially beginning with the oldest podcasts. For such podcasts, it would be useful to allow the user to sync podcasts beginning with oldest ones first e.g. the sync dialog's podcast tab should offer: 1 oldest 2 oldest 3 oldest 5 oldest 10 oldest in addition to the currently available options of 1,2,3,5,10 most recent. | ||||
Tags | No tags attached. | ||||
Fixed in build | 1203 | ||||
|
Fixed in build 1186. |
|
The currently proposed UI should be tweaked a bit since the current UI assume that the functionality is to download newest episodes. e.g. -'When _new_ episodes are available:...download the ..." We need a UI that clearly allows the user to: - download new episodes whenever new ones exist, and delete older ones - download the most recent old episodes that are unheard but not delete old ones unless they've been listened to - clearly communicate what happens when a Podcast is initially subscribed. Possible approach: When updating, download: _the 5 most recent episodes._^ _all episodes_ _the x most recent episodes_ _the oldest episode never before downloaded_ _the oldest x episodes never before downloaded_ _nothing_ |
|
Please have a look at my comments re. the proposed UI--I entered them soon after you'd resolved the bug :( |
|
Implemented also the latter proposal in build 1188. |
|
String review shows that this seems a bit confusing in practice, since: -the list of dropdowns is so long -the wording in some of the dropdowns is confusing (esp. the option for 'the oldest xx episodes never before downloaded' since what is really meant is 'xx oldest unplayed episodes'), and sometimes inconsistent (e.g. those episodes posted in the last 24hrs, vs. those episodes from the last 2 days) Suggested alternatives (the second is preferable if space permits): 1) When updating, download -all episodes -no episodes -the x most recent episodes -the episodes from the past xxxxxxx -the oldest xx unplayed episodes 2) An alternative layout that would be even easier to understand would be the following: On update, download _recent episodes first_^ _5 most recent_^ -recent episodes first [x most recent, from the past xxxx] -older episodes first [x unplayed episodes] -all episodes -no episodes |
|
Implemented the second (preferable) approach in build 1203. |
|
verified 1224 |