EditLive! 9 Documentation : Working with Media

EditLive! supports the embedding of media content through the use of oEmbed APIs. This section provides information on how the media support of EditLive! functions and how to configure media support within EditLive!.

Media Overview 

Media support within EditLive! is achieved by utilising oEmbed APIs to ask a service provider how one of their URLs should be embedded. This is described in the oEmbed specification. EditLive! supports all four oEmbed types in the specification; photo, video, link and rich.

Endpoints and URL scheme matching information must be provided for each service provider. This documentation is usually available from the service provider directly.

Media objects embedded within EditLive! are presented to the user in uneditable sections to preserve the output format returned by the service provider. Each section uses an overlay to indicate the type of oEmbed media that has been inserted. The icons can be seen below:

 Used to represent rich, interactive and social media.  Includes services such as SlideShare, Google Maps and Twitter.

 Used to represent video media.  Includes services such as YouTube, Vimeo and Brightcove

Photos inserted by media services, Flickr images for example, will be inserted as images.

To create an Insert Media menu item or toolbar button, the value InsertMedia must be specified for the name attribute of either a <menuItem> or <toolbarButton> configuration file element. For more information on EditLive! for Java configuration files, see the Instantiating the Applet article. For more information on creating menu or toolbar items, see the Setting Menu and Toolbar Items and Menu and Toolbar Item List articles.

oEmbed fallback

Due to the huge number of oEmbed service providers and the differences between how each service provider returns specifies their content to be inserted, Ephox recommends the use of a central provider such as embed.ly. While not free, such services provide a enhanced embedded media experience for your users.

Configuration

Configuration of media content is provided via the <multimedia> element within an EditLive! configuration file. A separate <service> configuration file element must be provided for each oEmbed service to be used with EditLive!. Types are evaluated in order, to allow for prioritisation of ambiguous schemes and fallback services to be specified as a last resort.

Example
The following example would ask youtube.com for how to insert YouTube videos, and embed.ly for all other links.

 
<editLive>
   ...
      <mediaSettings>
         ...
            <multimedia>
		      <services>
		        ...
		        <service name="YouTube" endpoint="http://www.youtube.com/oembed" scheme="http://*.youtube.com/*" />
				<service name="Embed.ly" endpoint="http://api.embed.ly/1/oembed?key=<your key here>" scheme="*" />
		        ...
		      </servies>
            </multimedia>
         ...
      </mediaSettings>
   ...
</editLive>

See Also

• <multimedia> Configuration File Element
• <service> Configuration File Element
• Instantiating the Applet