yea lets put player discussion on-list : )
my thoughts on the questions:
Should the skin show up right from the beginning (i.e., with the thumbnail picture)?
I think we should include it (if the "controls" attribute is set to true) ... Youtube does it .. in the future we could support jump to time seeking... where the user drags the seek bar (before the video has started playing).. update the video thumbnail with jpegs and the new timecode as they drag and then just seek to that time onMouseUp (we already have (updateThumbnail and updateVideoTimeReq ) ;)
Should we migrate the icons/functionality accessible in the corners of the thumbnail (download, choose player, ...) to the icons on the control bar (options icon etc.)
Yes.
How do we deal with the case where the requested width is insufficient for the entire control bar? impose a minimum width? Scale things down?
Bellow 320x240 I think we should hide the seek bar. You will probably have to do some hackery to get it to do dynamic layout widths properly. Let me know if you run into any css issues that seem insurmountable...
I got a lot of flv info today and it seems there is no perfect seeking solution without re-encoding flash content because flash can only seek or play media from a given keyframe. (it does not seem capable of decoding from previous keyframe and then skipping/dumping unrequested content to start playing at the time requested :( I will look at the existing media on archive.org see how much keyframe granularity they have...
--michael
Stjepan Rajko wrote:
Hi Michael,
I got started with the reskinning and have some questions. You can see my modest beginnings at:
http://urbanstew.org/MediaWiki/extensions/MetavidWiki/skins/mv_embed/sample_...
For now, the new skin will show up only if you play something using flowplayer - it will materialize (poorly) the control strip, and the pause/play button will work (but not change its image). I left the old controls for now as well.
My questions are:
- Should the skin show up right from the beginning (i.e., with the
thumbnail picture)?
- Should we migrate the icons/functionality accessible in the corners
of the thumbnail (download, choose player, ...) to the icons on the control bar (options icon etc.)
- How do we deal with the case where the requested width is
insufficient for the entire control bar? impose a minimum width? Scale things down?
Let me know if you'd rather I send these questions out to the list.
Thanks!
Stjepan
On Wed, Jul 23, 2008 at 7:13 AM, Michael Dale dale@ucsc.edu wrote:
yea lets put player discussion on-list : )
Should the skin show up right from the beginning (i.e., with the thumbnail picture)?
I think we should include it (if the "controls" attribute is set to true) ...
Cool - that will make things simpler for individual player embed implementation (we can move the controls html construction code to the main mv_embed script and just query the player embed script regading which commands it supports through JS.
For now I'm keeping the testing limited to the flowplayer embed. You can see my progress at: http://urbanstew.org/MediaWiki/extensions/MetavidWiki/skins/mv_embed/sample_...
If you choose flowplayer for the 2nd, 3rd, 4th example you will see the skin pop into place when you hit play. Play/pause functionality, seeker bar (for display, not seeking yet) & time display all work (on Firefox).
Youtube does it .. in the future we could support jump to time seeking...
Good idea.
Should we migrate the icons/functionality accessible in the corners of the thumbnail (download, choose player, ...) to the icons on the control bar (options icon etc.)
Yes.
OK. I will now start migrating the skin code to the main script (I will probably refrain from committing until it appears to work well on multiple browsers)
How do we deal with the case where the requested width is insufficient for the entire control bar? impose a minimum width? Scale things down?
Bellow 320x240 I think we should hide the seek bar. You will probably have to do some hackery to get it to do dynamic layout widths properly. Let me know if you run into any css issues that seem insurmountable...
It looks like with the provided design, the breaking point when something needs to go is just under 400. I made the seek bar go away at that point. I'll try to fine-tune things more as I go.
Cheers,
Stjepan