2008/8/12 Magnus Holmgren <[EMAIL PROTECTED]>: > One thing about adding bookmark reading/writing handling to playlist.c: it > is already quite large and complicated. A bit of cleanup/refactoring would > probably be nice before doing that, e.g., split out the code directly > dealing with the the .playlist_control file... > Oh, I know...
> In-ram playlist is only used for dirplay, as far as I know. If so, then > that won't be a problem. It was 1am when I wrote this last night so I may have got the names messed up, if you fiddle with the playlist so its no longer dirplay, current svn wont let you create a bookmark from it. > How handle name collisions? Because to keep current behavior, you need a > good, unique mapping from a playlist file/directory to the bookmark file. > Database results could (should?) be stored centrally though. thats what I wanted to discuss.... I've got a general idea of how to handle the new file format, its the placement and naming which is stumped me... Jonathan
