As I've been using SilverJuke for several months now, I have realized that my music collection isn't quite where I would like it. I often have people telling me that " You need to get _______ on your jukebox " ... the problem is their is no organized way to keep track of this. I had out a piece of paper for people to write suggestions on (several times) but always seem to lose them. (plus, inthis digital world...who wants to keep track of PAPER...)
I would love to see a 'music suggestion list' feature.
Functionality Possibilities:
- When searching for a song using the search bar or on-screen keyboard, add a button that would either add the search string to a list, or would bring the user to a quick popup form and allow them to enter information (this would allow the suggestions to go into a database and be more flexible for later use)
The form would ask for basic information : Artist name, Song name, User Name, and Comments (all fields optional).
This information would then be entered into a new row into the music_suggestion table (or whatever table is created for this).
I can't imagine a Jukebox owner or Music enthusiast who wouldnt want the chance to get direct feedback from the users or customers of their jukebox.
I hope this all makes sense and finds a home in a future version of Silverjuke.
(I know this could be done with a skin and script, but I think this should be a permanent feature that the SJ developers could integrate very cleanly)
I would be happy to expand on more ideas I have for this feature.
Thanks!
Music Request Feature
Re: Music Request Feature
I third this idea!
Any one fancy taking a stab at adding it as a script or mod???
Any one fancy taking a stab at adding it as a script or mod???
-
- Posts: 16
- Joined: 22. Aug 08, 20:41 [phpBB Debug] PHP Warning: in file [ROOT]/vendor/twig/twig/lib/Twig/Extension/Core.php on line 1266: count(): Parameter must be an array or an object that implements Countable
Re: Music Request Feature
Ideally (for me) a script that gets info, then emails me the info about the request, but storing it in a data base would be fine too. Why not offer both methods :)