You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gathering of video data can be simplified using oEmbed data from the video service provider. This data can not only be used to prepopulate the Title field for the user, saving them from having manually enter it, but can also provide other useful data, such as thumbnail URL's and links to the author and provider sites. oEmbed data can also be used to share this content with PMP and other services that support oEmbed links.
Not all providers return the same amount of data and would require some handling to normalize the data for standardized usage. Also,not all providers support a jsonp response options necessary front-end implementation. Until an in-house oEmbed retrieval endpoint can be created, suggest using Noembed service to support implementation of this feature into front-end code.
The text was updated successfully, but these errors were encountered:
- Issue #348 - Video embed now treats video embed as a 1:1 pointer to
provider video oEmbed data. URL field is no longer editable after being
saved, since changing the URL would be the same as removing the video
and adding a new one.
- Added drag-and-drop support for video URL's into Video embed modal via
plain text (dragged from address bar) or link HTML (dragged from link to
video URL).
- Added support for promises to be returned by embedType's
getModelFromForm method.
Gathering of video data can be simplified using oEmbed data from the video service provider. This data can not only be used to prepopulate the Title field for the user, saving them from having manually enter it, but can also provide other useful data, such as thumbnail URL's and links to the author and provider sites. oEmbed data can also be used to share this content with PMP and other services that support oEmbed links.
Not all providers return the same amount of data and would require some handling to normalize the data for standardized usage. Also,not all providers support a jsonp response options necessary front-end implementation. Until an in-house oEmbed retrieval endpoint can be created, suggest using Noembed service to support implementation of this feature into front-end code.
The text was updated successfully, but these errors were encountered: