WFMU Accu-Playlist Notes

Requirements

1. Super-insane broswer compatibility not just current generation modern browsers (Firefox 1.5+, IE6/7, Safari) but way, way backwards compatible. In practice this means text browsers should render usable pages and the use of Frames.
2. "Now Playing" most prominent Playlist element
3. Playlist commands lion's share or realestate with Comments to the side.
4. Customization easily mod some portions of page per show/dj
5. Chronologically Order Comments, oldest on top, newest, well, at the bottom. (Note: easily done: just added an anchor "lastComment" to bottom of comments page, linked this on the frame.
6. Required Info see notes below
7. Min browser size while design needs to "work" at 800x600 the 1024 experience should be just dandy

Objectives

1. Minimize backend coding use the same backend generator for all dj pages.
2. Static where possible, some portions of the page (frames) can be static, whether common to all djs or one per dj (prefer "globally" static where possible). Examples: header and comment form are globally shared. Footer is one per DJ.

Features (and some Assumptions)

1. Odd/Even coding, attach CSS "odd" (or even) class to comments and playlist's rows. Can be done on backend or on client via Javascript.
2. Trusted commenters such as staff, DJs, this will allow their comments to feature either avatars or other design elements calling them out.
3. Show/Hide comment form only added if client has Javascript enabled. By default this link is not visiable; it's turned on by JS in page footer.
4. Odd/Even rows add class="odd" (or even) to comments and playlist's rows. Can be done on backend or on client via Javascript.
5. the mock-up includes two avatar/user pics as examples to what could be done for DJ's and staff (admittedly these are teensie, perhaps 50x50 would be best)

Hopes & Suggestions

1. AJAX detection using simple Javascript check that deteremines whether user's browser supports Movilla or IE type DOM/HTTP request allow present-gen browers to use AJAX rather than page refreshing as this flickering interrupts user experience. If possible see if existing RSS feeds will suffice.

Questions

1. Paging on archived playlists the number of comments could be quite large... will comments be paged?

Info to Display

Header

• WFMU logo w/link to WFMU home page
• Audio stream links
• ??

Playlist Page

• Now Playing: Artist, Song, Album
• Show Title
• Show Description
• Playlist table: Artist, Song, Album, isNew indicator

Comments Page

• Commenter's name, posting date, comment

Footer

• Link to email DJ
• Link to last (most recent/prior) show's playlist
• Link to all this DJ's Playlists (archive)
• Link to all artists played by DJ
• Links to common RSS feeds for this show
• Kenzo / support link
• WFMU home page
• WFMU Schedule
• All WFMU Playlists

Comment Form

• Display Name
• Email
• Comment

top

Notes to Kenzo

• The CSS goes a bit overboard on descendant selectors, and in fact, for reuses, wshould rely more on unique names or ids. Please forgive.