gary.moncrieff:
Brian, just on this point is it possible to add new player designs without having to edit the core to register them first, I looked at this a while ago and seen I would have to edit the core to register the new player template.
You don't need to edit the core at all. Don't edit the core.
A skin defines what player it wants to use if there are options eg: in jrElastic
/skins/jrElastic/includes.php
You'll find this:
jrCore_register_module_feature('jrCore', 'media_player_skin', 'jrElastic', 'jrAudio', 'jrAudio_player_dark');
jrCore_register_module_feature('jrCore', 'media_player_skin', 'jrElastic', 'jrVideo', 'jrVideo_player_dark');
jrCore_register_module_feature('jrCore', 'media_player_skin', 'jrElastic', 'jrPlaylist', 'jrPlaylist_player_dark');
That is the elastic skin registering that it wants to use:
* jrAudio_player_dark as the default player for jrAudio
* jrVideo_player_dark as the default player for jrVideo
* jrPlaylist_player_dark as the default player for jrPlaylist
So if no type="xxxxxxxxxxxx" is defined for the {jrCore_media_player .....} call then the default will be used.
You can define to use any player you want in that location by adding it as the value.
{jrCore_media_player type="jrPlaylist_blue_monday" module="jrPlaylist" item=$item}
If you don't like the way jrPlaylist_blue_monday looks at the skin level and want to customize it for your skin you can over-ride it in all locations by defining a template over-ride at:
/skins/jrElastic/jrPlaylist_jrPlaylist_blue_monday.tpl and that will be used instead.
Is that enough to get you where your going? What are you thinking?
JAMROOM
