I've been thinking about how the "unplayed" bit could work technically. How does something like this sound:
For each podcast, store a file called something like -<podcast name>-_unplayed.xml. This should hold the ID of the most recent podcast episode separately, and a list of all unplayed episodes so far. This would be created when a podcast is added - all the episode URLs would be stripped out from the relavant xml file and put in this new file, along with the latest one held seperately. Each time the user navigates to a podcast, SC should do the following: - Compare the latest list of episodes to the "unplayed" file...... - If there are any episodes in "unplayed" that are no longer in the latest episode list file, remove them from "unplayed" (it's too late to play them now - they've gone) - If there are any new episodes in the list (later than the most recent episode id), add them to the unplayed file and update the most recent episode id. - Dynamically build a selectable list of episodes under "Not Played" based directly on the contents of the "unplayed" file. - Once -(the end of)- any episode has been played, remove it from the "unplayed" file. As you can probably tell, I'm not familiar with the terminology (I don't know what that "episode list" xml file is really called), but hopefully my thoughts are relatively easy to decipher...... Is that sort of thing feasible or have I made any dodgy assumptions? -- SadGamerGeek ------------------------------------------------------------------------ SadGamerGeek's Profile: http://forums.slimdevices.com/member.php?userid=6145 View this thread: http://forums.slimdevices.com/showthread.php?t=52098 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
