Thank You for your continued support and contributions!
... Then that begs the question, why not save all bookmarks in the one folder and then we can replace the "recent bookmarks" screen with a file browser pointing to the right folder?
- dynamic (inram and dirplay, stored in .playlist_control as a set of instructions on how to recreate the playlist)
Could bookmarks be incorporated entirely into the playlist storage? Without the corresponding playlist, a bookmark isn't much use.
Quote from: pondlife on August 11, 2008, 02:27:51 PMCould bookmarks be incorporated entirely into the playlist storage? Without the corresponding playlist, a bookmark isn't much use.adding resume info to a m3u means that loading will be much slower usually... the .playlistcontorl file can rebuild a playlist very quickly
...database playlists? inram playlists? (from the playlist POV there is no difference between these, but there should be... thats something for later though). I'm thinking we could store it in /bookmarks/ and show the keyboard so the user can choose a name? as long as the resume point is stored straight away then any delay naming the file wont cause an issue with the wrong point being saved.
Then that begs the question, why not save all bookmarks in the one folder and then we can replace the "recent bookmarks" screen with a file browser pointing to the right folder
What about configuring the database playlist bookmark names in the tagnavi.config file? The file name could consist of a constant part and a variable part containing the database query parameters. To identify multiple bookmarks of the same query there could be a serial number or time in the filename.
Page created in 0.12 seconds with 21 queries.