osterdamus
Monsieur Member
Some ideas on this from an outside perspective, if you don't mind.
This could be implemented as a concept that wraps the player. On my site I made a wrapping concept called Stage (yeah, the player is on a stage
), and provides extra functionality that wouldn't naturally belong in the player. In my case, I experimented with changing the surrounding layout and starting a video, when the player was started by the user. Here's an example, I even considered changing the css of my site to something more dark, as it is a moody track. (It's all just an experiment...)Continuing this concept further, you could easily provide future pre-made Stages for users to copy and paste (and let them code their own if so inclined), such as:
* Video Background Stage
* Image Ken Burns Stage
* Full Screen Stage
* A/B Test Stage
* ...
To implement this, you could base it on a (new) official public API made up of a few public functions such as Start([from]), Stop() and a few public evens such as Started(startedAt), Stopped(stoppedAt), Ended (when the player reaches the end of sound file).
The positives would be that it would incur limited new complexity in the player, start a solid public frontend API and a new concept that is open to extension if new needs arise.
You could make a separate page that is a "Stage builder". User opens context menu on a given Audio in the admin, clicks "Add to Stage", which could open the Stage builder. User chooses what stage and copies the code.
Aaaaanyway, just some ideas... :D
