Icebreaker: Difference between revisions

From XiphWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:
My plans are as follows:
My plans are as follows:


1. Written in Python.<br>
# Written in Python.
2. Metadata in database.<br>
# Metadata in database.
3. Playlists stored in database.<br>
# Playlists stored in database.
4. Playlist scheduling.<br>
# Playlist scheduling.
5. Backend/frontend design, possibly multible frontends.<br>
# Backend/frontend design, possibly multible frontends.
6. No web server needed, interface comes from TurboGears.<br>
# No web server needed, interface comes from TurboGears.
7. Minimal configuration, after all thats why I started the project.<br>
# Minimal configuration, after all thats why I started the project.
8. SQLObject will be used to work with any database.<br>
# SQLObject will be used to work with any database.
--[[User:Nickmudd|Nickmudd]] 18:54, 30 May 2007 (PDT)
--[[User:Nickmudd|Nickmudd]] 18:54, 30 May 2007 (PDT)

Revision as of 18:56, 30 May 2007

Introduction

Icebreaker is a playlist authoring/scheduling system for Icecast. It uses a database to store playlists and scheduling data. Icebreaker's main objective is to be easy to use, so that writing playlists by hand can be avoided. Icebreaker is being designed to use a web-based interface through TurboGears. Icebreaker is _NOT_ a web-based streamer or a client.


Plans

My plans are as follows:

  1. Written in Python.
  2. Metadata in database.
  3. Playlists stored in database.
  4. Playlist scheduling.
  5. Backend/frontend design, possibly multible frontends.
  6. No web server needed, interface comes from TurboGears.
  7. Minimal configuration, after all thats why I started the project.
  8. SQLObject will be used to work with any database.

--Nickmudd 18:54, 30 May 2007 (PDT)