Rockbox Development > Feature Ideas

Streamline playlist handling

<< < (5/6) > >>

nls:

--- Quote from: jim234567 on June 12, 2011, 06:29:59 PM ---Well, I see you guys are pretty adamant about this, as all you continue to  keep suggesting are workarounds for a deficiency in Rockbox's handling of playlists (at least Chronon seemed to finally catch on what the issue is)

--- End quote ---

We have suggested different approaches to solving your problem so that you don't have to write a patch for rockbox that does something at least some devs don't think fits well into our database scheme. I understand perfectly fine what you want to do but you don't seem to want to hear of alternate approaches to solve this so happy coding i guess.

Chronon:
jim234567, I do agree that some method of converting playlists containing relative paths into playlists containing absolute paths would be useful.  However, I didn't ever suggest that playlists should be indexed in the database.  If there is a way to convert the playlists to use absolute paths then you are free to move the playlists to any convenient location (like the directory you choose as the playlist catalog).  It seems like this is the change that would be of primary benefit.

The topics in this forum are purely to discuss ideas for rockbox and how to implement them.  The only way that a topic in this forum translates into a change happening in Rockbox is if somebody steps up and decides to do the work to actually implement it.  So, while you might have a list of changes you wish to see, I think it's a good idea to decouple different ideas from each other as much as possible to allow them to be implemented separately if somebody decides that one of them is worth their time and effort.

jim234567:

--- Quote from: nls on June 12, 2011, 07:16:57 PM ---We have suggested different approaches to solving your problem so that you don't have to write a patch for rockbox that does something at least some devs don't think fits well into our database scheme. I understand perfectly fine what you want to do but you don't seem to want to hear of alternate approaches to solve this so happy coding i guess.

--- End quote ---
Lol.
The approaches mentioned here are what I said I'm already doing. Kinda crazy to have a "Playlist Catalog" on the menu if it can't be used in any practical sense where you have to launch your playlists from elsewhere...
And yes, I would love to help with the development of it if I could, but unfortunately I lack the technical knowledge of it (simply trying to figure out a dang screen theme was already hard enough for me).
I figured this one would've been an easy suggestion (thinking it even could've just been an oversight), but dang was I sure proven wrong. :-[




--- Quote from: Chronon on June 13, 2011, 01:05:39 AM ---jim234567, I do agree that some method of converting playlists containing relative paths into playlists containing absolute paths would be useful.  However, I didn't ever suggest that playlists should be indexed in the database.  If there is a way to convert the playlists to use absolute paths then you are free to move the playlists to any convenient location (like the directory you choose as the playlist catalog).  It seems like this is the change that would be of primary benefit.



--- End quote ---

Chronon, I did not mean to suggest you had said it should go in the Database itself or anywhere else, I was simply pointing out that you seemed to understand where I was coming from. Seems no one else here does though so I guess I'll just have to leave it at that.



Appreciate your time guys. I'll butt out of here 8)

bluebrother:

--- Quote from: jim234567 on June 12, 2011, 06:29:59 PM ---I'm only suggesting it handle it like other players do.
--- End quote ---

In Rockbox generally we don't care much about how other players or especially the original firmware does things. It's this since years, so don't expect a change here.


--- Quote ---When it's scanning your files ("Refreshing", to use Sansa's word for it), it automatically takes any playlist file it finds, (I assume scans it and generates whatever code it needs for it internally) and then shows it under a heading called "Playlists" on it's menu where it can easily be found by the user.
--- End quote ---

Rockbox does *not* scan the files. The Database indexes them, and as I explained earlier, there's no sensible way to put playlists into the Database.


--- Quote ---With Rockbox, I have to go digging amongst thousands of files & folders to find each of my lists that are scattered about them, then go through this arduous re-saving procedure I already explained earlier to get the list to show itself under Playlists.
--- End quote ---

To put it in your words, you seem to be pretty adamant to accept that there are ways to achieve what you want. There's no need to resave all playlists, and putting all playlists on the player into a single folder is for sure a bad idea for all those people that intentionally split them across folders. So you're basically saying to make things more like the way you prefer it we should make it worse for all people that have a different approach.

While I can see that there are possibilities to improve things the suggestions you made are simply to short sighted and therefore not acceptable.

[Saint]:

--- Quote from: jim234567 on June 13, 2011, 01:59:13 AM ---Kinda crazy to have a "Playlist Catalog" on the menu if it can't be used in any practical sense where you have to launch your playlists from elsewhere...

--- End quote ---

I can't say that I'm not confused about this...The playlist catalogue is perfectly functional and does exactly what it should do. In a previous post I already explained how to move the location of the playlist catalogue with a config file entry.
In my case I make it so that the root of the device is the playlist catalogue, so that playlists saved to the root of the device "just work" and appear in the playlist catalogue as one would expect them to without any further manual intervention.


[St.]

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version