[Openfc-design] player brief v 0.1

[adam <ad...@xs...>]

hey all,

This is primarily for Goo to het him started with design.



Brief for HTML Player

Functional Overview
In some sense, the FC HTML Player is a cross platform version of the VB
Frequency Clock Player, in that the palyer is used for replaying
timetables created with the Frequency Clock scheduling system. However
there are some substantial differneces, so please do not refder to the
current VB player as a prototype, instead refer to the demo located at:
http://openfc.sourceforge.net/player/base2.htm

Functional Description
The Frequency Clock timetabling system is being re-organised. The most
substantial change is the implementation of more complicated user
accounts. These accounts allow for the creation and customisation of
multiple timetables, the addition of private or shared programs, the
ability to assign other users priviledges for your programs and
timetables, and the ability to customise a player dedicated to each
timetable.

What is a channel?
A channel is what we now call all those items that are associated with a
specific timetable. For example, if Montevideo has a channel, then this
channel comprises of:
a timetable
the programs associated with the timetable
a player associated to the timetable

A single user can have multiple channels. The dedicated player is what we
are looking at here.

The player can open from any webpage. If, for example, Montevideo has a
channel then a simple link on their front page will open the player
associated with that channel. This player will have a default design but
the design elements can be customised through the FC backend so the player
can reflect the design elements of its owner. If, for example, MAMA had a
channel, then the MAMA player could be customised to a MAMA specific look
and feel.

The player is used for replaying only the content on that particular
channel. If the contnet for another channel is to be viewed a seperate
HTML player will need to be opened. Hence multiple channels can be
simultaneously opened if necessary.

It must work across Mac IE 5.1+, Netscape 4.75+, Windows IE 5.5+, Netscape
4.7+, Linux (Mozilla?, Konquerer?)



The sections of the player are:
1. Player
this contains the following:
i) Video Frame : video window for replaying content, default ratio 4:3.
This window simply replays the video, or plays the embeded audio and
displays a jpg (the jpg is determined by the user, but will be at a size
defined by us)
ii) Timetable Frame : scrollable window with programs listed for that day.
This will list the date of the program, the time it starts, the name of
the program, and an indication of whether the program is live. If the name
of the program is clicked then the info window appears (as a seperate
window) with details about the program. This window is scrollable down but
not across.
iii) Control Frame : controls are located in the bottom frame. These are
graphic buttons with rollover behaviours as close to possible to a typical
media player (eg. Winamp). In this situation this means only that if a
button is pushed, all other buttons become 'de-pressed' and the selected
button should look 'pressed'. This javascript will also trigger events in
the video frame.

If javascript cannot allow certain events (eg. fast-forward), then the
button should appear 'greyed-out'.

From the Control Frame users will also be able to open (as seperate
windows) the Chat Window, and Archive Window (see below).

2. Chat Window
This is a chat window defaulted to the name of the timetable. At the
moment I am using free Leachim Java Chat:
http://www.chatzone.de/startpage.jsp

Its advantages are that it works, its free, and its simple. The page can
be custimised through HTML (see source of chat window linked from player).

3. Info Window
This window displays the text about the current program playing, or the
program listed in the Timetable Frame (see above).

4. Archive Window
This window will display a pre-determined number of programs (determined
by the user) for browsing. The name is displayed with an info icon.
Clicking on the info icon displays the program info as mentioned above.
Clicking on the name plays the content in the players Video Frame.

5. Channel Selector
Quandry....it would be nice if a dhtml drop down menu could open when the
'channel' link is clicked on the Control Frame. This would simply list
channels that the user has chosen to be associated with their player.
Chosing a channel from this drop down list would open that channels player
in a seperate window. However I am not sure this can be done across the
browser listed above. This may instead have to be a standard HTML drop
down menu...ideas?


Look and Feel
The player and the associated windows (Chat, Archive, Info), should all
look like applications. They should also look like they belong together,
including the addition of docking if possible.

The current demo uses a chromeless window script. This works for IE on
Windows only. For this reason we must have a basic version, with a simple
open.window script that opens a window without toolbars etc and at a
specific size across the browsers listed above, and if the users wishes
they can instead use the more complex link (requires extra javascript in
the header and a linked js script) for opening the chromeless window.

The player must have as many customisable design elements as possible. If,
for example, Tate Modern wishes to implement a player, they should be
satisfied that the player _looks_ like a Tate Modern player. This includes
fonts, colors, the possible addition of a space for logos, replacement
button images etc.





 "free, as in 'radio'"