Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=MEDIA_FRAME_CONTROLS_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed

current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

When playing audio or video, the user needs the ability to control the media. This can be though simple controllers that start or stop the media, slider controllers that allow the user to control where in time the media is playing, or any other kind of controller we can imagine.

Each content should be able to determine how to render itself based on it's state.

Frames need a mechanism for handling adornments in general, of which controllers are one type of adornment. Adornments can either render themselves on top of the frame, or extend the size of the frame without affecting the content of the frame.

For example, a slider controller with a play/stop button, rewind, fast forward and a slider with a thumb, may live below the content in a frame. This controller would live below video. So if a video is 320x160, and the controller is 16 pixels tall, the actual frame size is 320x176. This is necessary because when the author flows text around the frame, they don't want the text flowing under a video controller.

However, other controllers may not need to extend the frame. One can imagine a controller that shows translucent controls on top of the media as the cursor passes over the media, and then fade out when the user stops moving the mouse.

So, adornments, be them controllers or some other use of adornments, need to be able to specify where they are to be rendered in the frame. They should be able to specify bottom, top, left, right, what their size should be (fixed, expanding in either vertical or horizontal dimensions) and whether or not they live inside or outside of the frame (the visual representation of it).

Adornments are properties of a frame, not the content. The same content can be rendered in 3 different frames, some with adornments, some without.

Users should be able to toggle controllers on and off.

Controllers will need to be able to interface with the content of the frame, so there will need to be a clean way to notify the controller that the content has changed state.

Task requirements

• Create controllers for media manipulation.
  • play, stop and pause.
• Allow controllers to communicate with a frame's content
• Think about how controllers can be skinned
• Notes:
  • Keep the connection between controllers and media as simple as possible.
  • Remember that every frame can have the same content in different states.

Task result

The result of this task is source code.

Implementation idea

• Review the scene elements of the media.
• Decide how to display controllers and connect them with the media manipulation interfaces (perhaps through the LogicR3).

Related

• SCENE_COMMONS_R1
• SCENE_COMMONS_R0
• MEDIA_ENGINE_IMPL_COMMON_R0
• MEDIA_ENGINE_IMPL_MAIN_R0
• VIDEO_CONTENT_R0
• AUDIO_CONTENT_R0

How to demo

• Insert a media frame.
• Click on the frame.
• Use the controls to manipulate the media.

Design

• Media frame controls will be defined as MediaManipulationViews which have image SceneElements containing icons. These will represent "buttons" that manipulate the media in Sophie2. In order for the scene elements to behave as buttons we should specify some logic that changes the alpha values of the scene elements (so that they look as if they are clicked, pressed or the mouse is over them - as real buttons do).

• For the time being we will implement three MediaManipulationViews:
  • PlayMediaManipulationView - for playing media.
  • PauseMediaManipulationView - for pausing the media.
  • StopMediaManipulationView - for stopping the media.
• In order for these to be skinable we should define tool-tip and icon in a SkinPart.
• "Buttons" should be arrange correspondingly in the bottom left corner of the frame in the same order as described above.
• Every icon should be scaled to look nicely inside the frame.

Implementation

^{(Describe and link the implementation results here (from the wiki or the repository).)}

Testing

^{(Place the testing results here.)}

Comments

Steve doesn't feel that "including the ability to set image for not-available" and "and image for not playing" are not part of this task.

desc("related to frame contents") desc("should allow customization of how media appear (play button, slider, etc)") desc("including the ability to set image for not-available, ") desc("and image for not playing")