Hi James and Tona, Thanks - this is great! Once I have it up on the Studios I'll let you know so that you can have a look at it.
Michelle On 2011-12-07, at 6:28 AM, tona monjo wrote: > I've been reading James' writing and I think it's exhaustive, so I've only > added a line about full-screen view. I've also started describing the design > process: > > --start-- > > Goal: Design of a 'video' player that gives users access to video-based > content with particular sensitivity to: a) their preferred sensory input > mode, and b) their device and browser of choice. That is, the video delivery > would be both sensory and platform agnostic. This player would eventually be > accompanied by an alternatives authoring tool. > > Some features might include: > - Layered content: audio + video, audio + audio descriptions, video + closed > captioning, transcripts, etc. > - Playability of videos across HTML5-ready browsers, with Flash regression > for older browsers > - Desktop and mobile-readiness > - Language localization for interface elements, captions, and transcripts > - Enabling users to make content requests (e.g., localized > captions/transcripts), and fulfill requests made by other users > - Integration with PCF's Universal Subtitles authoring tools and content > database > - High level of user configurability (key bindings, captioning and transcript > type size and contrast, etc.), and integration with UI Options > - Full-screen view with horizontal/vertical layout (adapting to user’s > preferences) > - Portability of video preferences across sessions and devices > > > Process - Design > > The process of design begins with some early drafts that explore the > possibilities for integrating the defined features into the video player, and > how they can be placed into the web page [images of the early drafts] > > In this phase, the design team meets frequently, to make the drafts evolve > until reaching the last version of the wireframes, available here: > http://wiki.fluidproject.org/display/fluid/Video+player+designs > > The designers pay special attention on: > - Integrating Narration and Transcript options in the best way, preserving > the possibility of customize them. > - Displaying the downloading progress for different video qualities. > - Managing the scrubbing bar in a way that clearly informs the user what are > the contents of each frame. > - Integrating the Transcript text in the web page without invading other > contents area. > - Enhancing the video player responsiveness among different device formats > (desktop and mobile, with diverse browser sizes). > > The wireframes are presented to developers in a walkthrough > (http://wiki.fluidproject.org/display/fluid/Video+Player+Feature+List), and > some questions emerge about expected behavior and other details of the > features. Developers share their questions in the Fluid wiki > (http://wiki.fluidproject.org/display/fluid/Video+Player+Questions), so they > can be directly answered by designers, or sometimes discussed to make some of > the design details evolve beyond. > > Once the wireframes have been discussed, it starts the design of the high > fidelity mockups > (http://wiki.fluidproject.org/display/fluid/Video+Player+%28November+2011%29) > that include the graphic design of the video player. These are the > pixel-perfect mockups that will be used for the development of the video > player. > > > Process-development > > Roadmap > > --end-- > > > On Tue, Dec 6, 2011 at 4:44 PM, tona monjo <[email protected]> wrote: > > > > Thanks James! I will work from your writing. > > > > Tona > > > > > > On Tue, Dec 6, 2011 at 3:35 PM, James W. Yoon <[email protected]> wrote: > >> > >> Hi Tona, > >> > >> At one point, I had written down some high-level objectives and > >> requirements. Feel free to repurpose these as appropriate. > >> > >> --start-- > >> > >> Goal: Design of a 'video' player that gives users access to video-based > >> content with particular sensitivity to: a) their preferred sensory input > >> mode, and b) their device and browser of choice. That is, the video > >> delivery would be both sensory and platform agnostic. This player would > >> eventually be accompanied by an alternatives authoring tool. > >> > >> Some features might include: > >> - Layered content: audio + video, audio + audio descriptions, video + > >> closed captioning, transcripts, etc. > >> - Playability of videos across HTML5-ready browsers, with Flash regression > >> for older browsers > >> - Desktop and mobile-readiness > >> - Language localization for interface elements, captions, and transcripts > >> - Enabling users to make content requests (e.g., localized > >> captions/transcripts), and fulfill requests made by other users > >> - Integration with PCF's Universal Subtitles authoring tools and content > >> database > >> - High level of user configurability (key bindings, captioning and > >> transcript type size and contrast, etc.), and integration with UI Options > >> - Portability of video preferences across sessions and devices > >> > >> --end-- > >> > >> James > >> > >> On 2011-12-06, at 6:20 AM, Tonamonjo wrote: > >> > >> Hi Michelle, > >> > >> I think that the objectives and requirements are not still formally > >> written, but can be done. I'll start preparing a draft for this. > >> > >> Tona > >> > >> > >> > >> On 05/12/2011, at 19:01, Michelle D'Souza <[email protected]> wrote: > >> > >> Hi Tona, > >> > >> This sounds like a good plan. > >> > >> I'm not sure that we can easily show the working, in development video > >> player in a way that would allow other authors to follow suit. Do you > >> think we can link to a demo of the working player instead? > >> > >> Do you know if the objectives and requirements for the video player are > >> written down somewhere? > >> > >> Thanks! > >> > >> Michelle > >> > >> > >> > >> > >> On 2011-12-05, at 8:37 AM, James William Yoon wrote: > >> > >> Tona, > >> > >> That sounds like a great outline for the post. +1 > >> > >> James > >> > >> On Mon, Dec 5, 2011 at 4:18 AM, tona monjo <[email protected]> wrote: > >>> > >>> Hi Michelle, > >>> > >>> Good question, and sorry for not answering before. > >>> > >>> Although there is still no one project page in Fluid Studios, maybe > >>> someone has already got ideas about what kind of contents should be > >>> included in these kind of pages. > >>> > >>> From my point of view, and having in mind the goals of the Fluid Studios, > >>> it would be interesting to explain all the process of design and > >>> development, so each project page can work as a case study. > >>> > >>> If so, we can have the developed video player at the beginning of the > >>> page (to show how works the current version of the video player), and > >>> then an explanation of: > >>> > >>> Project's background: objectives and requirements, > >>> Process: brief explanation of the process of design and development, > >>> supported mainly on downloadable documents and links to the wiki. > >>> Roadmap (phases of development, to let the user know the functionalities > >>> of the current version and how the project is expected to evolve). > >>> > >>> I would also emphasize the commenting functionality, to encourage the > >>> users to share their opinions or suggestions about the project. > >>> > >>> I'm not very sure if this goes in the direction of your question, > >>> Michelle. What are your thoughts? > >>> > >>> Tona > >>> > >>> > >>> > >>> > >>> > >>> On Thu, Dec 1, 2011 at 11:00 PM, Michelle D'Souza <[email protected]> > >>> wrote: > >>> > > >>> > Hi Tona and Joanna, > >>> > > >>> > I'm hoping you can help me create a Studios entry for the video player. > >>> > I want to ensure that the Studios site works well with real content and > >>> > it seems like a good opportunity to showcase our work on the video > >>> > player. > >>> > > >>> > Any thoughts on what you would expect on the video player studios page? > >>> > > >>> > Thanks, > >>> > > >>> > Michelle > >>> > > >>> > > >>> > > >>> > ------------------------------------------------------------------------ > >>> > Michelle D'Souza > >>> > Senior Inclusive Developer > >>> > Inclusive Design Research Centre, OCAD University > >>> > > >>> > >>> > >>> _______________________________________________________ > >>> fluid-work mailing list - [email protected] > >>> To unsubscribe, change settings or access archives, > >>> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work > >> > >> > >> > >> > > > > > > > > -- > > Tona Monjo > > LATENT, User Experience Design > > http://www.latent-design.com > > T (+34) 654 402 387 > > Skype: tona.monjo > > Twitter: tona_monjo > > Blog: http://blogs.elpunt.cat/tonamonjo/ > > > > ------------------------------------------------------ Michelle D'Souza Inclusive Software Developer Researcher Inclusive Design Research Centre
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
