Technical implementations

Here's some notes about the technical implementations.

The original kaltura_video for Elgg 1.7 used Kaltura's VideoMix content type. This type didn't support multiple video formats and qualities so I decided to start using MediaEntry type instead.

I decided to dump the object tags using flash videos and use HTML5 video tags instead. The view generating the video tags connects to Kaltura and get all the flavors of the video generating a tag of each video source so the web browser can pick the type it supports.

Quite few browsers fully support HTML5 video at the moment so I'm thinking about using video.js player (http://videojs.com/) to improve the compatibility. Using video.js I have currently managed to get the videos to work on Firefox, Chome, Opera, Safari, IE7, IE8 and IE9. I have also successfully tested them iPad, Lumia 800 and Samsung Galaxy S II. (The video format being mp4.)

The idea of originally using VideoMix content type for the videos in Elgg was propably that it is possible to edit this type through web browser using Kaltura's editor widget. The MediaEntry type most likely doesn't support any kind of editing since it is the top level video in Kaltura and all the VideoMixes and different flavors are created under this video. So propably we'll have to completely remove the possibility to edit videos through Elgg.