Hi Varsha
You could do this using the IFrame object which can link to an external web page. This gives you a degree of control as you can have that page check versioning and extensions (see below) with a fine degree of control.
If you want this to have 100% availibility then you should probably add the page and its contents as a folder in the courselab module. You should also add the MSI for the version you want used and MSI's that may be required for any functionality above that normally included in that specific version.
In this case, iframe and web page) the control of the media file is with the discrete web page.
*** You should be aware that this action is increasingly viewed as a potential threat by the web browser engines. Some coporate browsers have locked security settings and will not allow actions like this, some newer version web browser engines will flag warnings that will require the user to allow the action to complete.
Cross domain name calls are bad news.
*** You will need to ensure that the player and any required codecs (that every user of the page has installed on their PC) is the same as you are defining for the functionality level you require. You cannot assume that as a user I will be using the same viewer as you or anyone else is even when considering windows as your main target platform.
The player action in courselab simply calls for an instance of the player to run within the courselab DOM, if it is not available then nothing happens within courselab although the OS may flag this as a problem and ask if it can download a player to suit the media type.
Courselab can check at the module start up for the availibility of generic player types but NOT the specific version available or required.
You are specifying the windows media player which is available in 11 main versions now and 100's of sub versions (luckily probably only 3 are in common use) each has many generic and version specific add-ons.
*** If the user has CC turned off then the player won't even look for the sami file, if you want to change the properties of the player then you need to get the SDK for players 8 - 11 and code for each. The coding is virtually the same but there are small increments in functionality. Again wether this is allowed by the OS layer on the viewers PC depends on which it is and what the users security schema is like.
Otherwise
(a) just use the inbuilt wmv object. If the user has CC turned on then it should find the sami and work. Add an advisory note that CC is available fom the module startup page so users can turn the functionality on if they need it.
(b) produce a plain wmv and OC'd version then offer the user the option of using either.
(c) synchronise the wmv with a timeline series of objects to provide a pseudo CC, this will probably fail due to differences in PC performance and playback capabilities.
Regards
Nick
Hi Varsha
You could do this using the IFrame object which can link to an external web page. This gives you a degree of control as you can have that page check versioning and extensions (see below) with a fine degree of control.
If you want this to have 100% availibility then you should probably add the page and its contents as a folder in the courselab module. You should also add the MSI for the version you want used and MSI's that may be required for any functionality above that normally included in that specific version.
In this case, iframe and web page) the control of the media file is with the discrete web page.
*** You should be aware that this action is increasingly viewed as a potential threat by the web browser engines. Some coporate browsers have locked security settings and will not allow actions like this, some newer version web browser engines will flag warnings that will require the user to allow the action to complete.
Cross domain name calls are bad news.
*** You will need to ensure that the player and any required codecs (that every user of the page has installed on their PC) is the same as you are defining for the functionality level you require. You cannot assume that as a user I will be using the same viewer as you or anyone else is even when considering windows as your main target platform.
The player action in courselab simply calls for an instance of the player to run within the courselab DOM, if it is not available then nothing happens within courselab although the OS may flag this as a problem and ask if it can download a player to suit the media type.
Courselab can check at the module start up for the availibility of generic player types but NOT the specific version available or required.
You are specifying the windows media player which is available in 11 main versions now and 100's of sub versions (luckily probably only 3 are in common use) each has many generic and version specific add-ons.
*** If the user has CC turned off then the player won't even look for the sami file, if you want to change the properties of the player then you need to get the SDK for players 8 - 11 and code for each. The coding is virtually the same but there are small increments in functionality. Again wether this is allowed by the OS layer on the viewers PC depends on which it is and what the users security schema is like.
Otherwise
(a) just use the inbuilt wmv object. If the user has CC turned on then it should find the sami and work. Add an advisory note that CC is available fom the module startup page so users can turn the functionality on if they need it.
(b) produce a plain wmv and OC'd version then offer the user the option of using either.
(c) synchronise the wmv with a timeline series of objects to provide a pseudo CC, this will probably fail due to differences in PC performance and playback capabilities.
Regards
Nick
