Comment 18 for bug 1387691

@saviq
I agree with the 2 approaches from comment #14. However neither are really feasible for RTM without doing a sizable amount of work:

1) For the embedded video component
- my team would create the component, and move it into ui-extras to start with. We started this a while ago here:
https://code.launchpad.net/~renatofilho/mediaplayer-app/share-components/+merge/241599, but this would need to be finished
- modify Video scopes to use the component
- modify Gallery and Camera to use the component

2) Trusted session support
For this to land, there are a couple of blocking issues that need to be sorted on Unity and/or Scopes
- fullscreen window support - this is needed because users expect video playback to happen in fullscreen mode as it does today when launching mediaplayer-app via url-dispatcher.
- feedback when launching - based on ted's prototype of launching mediaplayer-app as a trusted session, there is quite some delay when launching as a trusted session. Some sort of spinner or splash screen is needed when launching it. Guessing would be better to build this into the framework somehow rather than having each client (i.e. scopes, apps) be responsible for doing it.

My suggestion is that we add these tasks to respective backlog and get them scheduled.

For the short term, I'd suggest we use "OnlyShowIn" in the desktop file of mediaplayer-app. This would hide it from the apps scope but still allow it to be launched as it is today from scopes and apps. The only downside is it would still show up in the launcher when running and could be pinned, but I'd say that is still an improvement over what we have today.

Question: what value would we set for "OnlyShowIn"?

Thoughts?