Main > Audio/Jukebox/MP3 Forum
Plugins: Document API for JukePlugSys
Space Fractal:
BTW I think I ask saint to lock this thread I have created to the hell.
I dedicated to pull off. No more points to debate this anymore .
Thanks very much for the debate.
We start from the beginnig with a completly new format.
loadman:
--- Quote from: Space Fractal on January 07, 2008, 04:51:11 pm ---BTW I think I ask saint to lock this thread I have created to the hell.
I dedicated to pull off. No more points to debate this anymore .
Thanks very much for the debate.
We start from the beginnig with a completly new format.
--- End quote ---
You don't have to agree, That's fine. :)
But don't get upset about it. ;D
headkaze:
--- Quote from: unclet on January 07, 2008, 04:35:35 pm ---Based on my format, your software would still use the "JUKE_ATTRACT_MODE" command. The documented description of the "JUKE_ATTRACT_MODE" command would simply inform the plugin author that this command relates to "MultiJuke's screensaver function", "UncleT's Jukebox page flipping attract mode function", etc...., etc....
Basically, the plugin author will understand what each command does based on their reading of the each command description which should definitely occur before they start coding their plugin.
--- End quote ---
This is what I was saying all along too (and was starting to repeat myself over and over). It's simple and it works in any scenario. Any Jukebox programmer can add or remove the commands they want, and they can share common commands. If people can't agree on something as simple as this it's best to create your own plugin systems.
It's a shame but hey these things happen :dunno
loadman:
--- Quote from: headkaze on January 07, 2008, 05:15:39 pm ---
--- Quote from: unclet on January 07, 2008, 04:35:35 pm ---Based on my format, your software would still use the "JUKE_ATTRACT_MODE" command. The documented description of the "JUKE_ATTRACT_MODE" command would simply inform the plugin author that this command relates to "MultiJuke's screensaver function", "UncleT's Jukebox page flipping attract mode function", etc...., etc....
Basically, the plugin author will understand what each command does based on their reading of the each command description which should definitely occur before they start coding their plugin.
--- End quote ---
This is what I was saying all along too (and was starting to repeat myself over and over). It's simple and it works in any scenario. Any Jukebox programmer can add or remove the commands they want, and they can share common commands. If people can't agree on something as simple as this it's best to create your own plugin systems.
It's a shame but hey these things happen :dunno
--- End quote ---
I gotta go to work now :-(
Space Fractal:
sorry about it, but I still prefer start from beginning with a new thread started by you.
we other can then see we can agree or disagree.
Also sorry to UncleT as well.
I think we scrash both SDK and trying to make a comprimest in a new thread using my and Uncle't ideas.
Let plugin writes think first and let us jukebox writes came after. Use both of ideas by mine and UncleT.
I was just scare about all these new commands that never would been used, if a plug worked best for one contain software.
BTW we could make few functions. One for sending commands and one for sending a command list as well or something like that.
EDIT: Since this came out of controls where many us was upset (sorry again), I created a new thread with no listed command and my vision). I dont want have more posts into this thread.
PLEASE LOCK THIS THREAD
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version