02-05-2021, 09:51 PM
(This post was last modified: 02-05-2021, 09:53 PM by TheOldPresbyope.)
@steven4build
Yup, the worker.php and playerlib.php routines contain a lot of the meat of moOde's backend, but I'd suggest you look at how the LCD update engine is implemented to get an idea of how you might hook in without hacking at these core routines. Keep in mind that they are subject to change with each update of moOde. The more you can depend only on their "hooks", the better insulated from change your code will be.
And just so there's no mistake, Tim's the primary author of this lovely music player. I started hanging out about 4 years ago and have made only minor contributions, more in the way of quality assurance. What I know about moOde, I learned by reading the code.
Good luck.
Regards,
Kent
Yup, the worker.php and playerlib.php routines contain a lot of the meat of moOde's backend, but I'd suggest you look at how the LCD update engine is implemented to get an idea of how you might hook in without hacking at these core routines. Keep in mind that they are subject to change with each update of moOde. The more you can depend only on their "hooks", the better insulated from change your code will be.
And just so there's no mistake, Tim's the primary author of this lovely music player. I started hanging out about 4 years ago and have made only minor contributions, more in the way of quality assurance. What I know about moOde, I learned by reading the code.
Good luck.
Regards,
Kent
