Added section "Advanced Playlist Management" with 3rd party web app

[porg]

Retroarch Playlist Editor:

• Linked to the web app. Free and open source: https://github.com/marcrobledo/retroarch-playlist-editor/
• Gave an outline of what you can do with it.
• Useful end user information.
• Hence legitimate to be mentioned in the user docs I'd say.

[fpscan]

Hey @RobLoach I don't like to go out organization area but I see your contribution on that project. So I was wondering would you like to review this but like I said mostly we point to organization project. So maybe we can fork to libretro if the author and licence is okay and we can built with github actions.

[porg]

@fpscan FYI I the author of this addition am okay with everything you do with that text snippet as long as the info that there's a 3rd party tool for playlist management makes it to the docs. 👍

[porg]

@fpscan Today you accepted /pull/700 amazingly fast in ca. 30min, whereas this pull request here is pending for a week now. Any news? Why the holdup?

[fpscan]

@fpscan Today you accepted /pull/700 amazingly fast in ca. 30min, whereas this pull request here is pending for a week now. Any news? Why the holdup?

This is great imo but I usually avoid the any software outside the organization, I was waiting Rob's input on this to see his involve with that project. I'll ping him on the discord and get back here.

[porg]

Ah ok! Because of referring to a 3rd party software. I understand.

• This care is actually warranted in that case.
• Because the software is a bit outdated and buggy.
• I had to do some RegEx postprocessing on the .lpl files
• Last development activity in 04/2019
• Maybe worth for your RetroArch guys to look into the open issues there, possible contributing or forking.
• Really only rather some small things (such as outdated core names, etc) which are quick to fix for someone with knowhow.

[porg]

@fpscan and @RobLoach

• I understand your hesitation/care before recommending a 3rd party tool
• The good news: Last development activity was in 04/2019 but now the author has reacted with explicit intention to continue development 🙂
• I on my side made very concrete feedback for all the issues I experienced while evaluating it

What we could do now in terms of user docs:

1. Publish it but add a line of caution with a link to the currently known limitations)
2. Don't publish anything and instead delegate to the /marcrobledo/retroarch-playlist-editor project to notify when the main issues where addressed and then publish.

• Downside of # 2 "Sitting on the knowledge silently" IMHO is: Some users may have the need for creating custom playlists and maybe are better of with a half working tool + some RegEx postprocessing, rather than having nothing and doing this from scratch (copping snippets of JSON around, or maybe doing a JSON -> CSV, then editing in Spreadsheet App, then CSV -> JSON).

[porg]

@RobLoach I just saw that you wrote the very first issue for marcrobledo/retroarch-playlist-editor/issues/1 so you are surely familiar with the tool and it's capabilities, as you yourself proposed to make it available in a hosted form on the GitHub pages 😉