Icebreaker: Difference between revisions
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: | ||
# Written in Python. | |||
# Metadata in database. | |||
# Playlists stored in database. | |||
# Playlist scheduling. | |||
# Backend/frontend design, possibly multible frontends. | |||
# No web server needed, interface comes from TurboGears. | |||
# Minimal configuration, after all thats why I started the project. | |||
# 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 17: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:
- Written in Python.
- Metadata in database.
- Playlists stored in database.
- Playlist scheduling.
- Backend/frontend design, possibly multible frontends.
- No web server needed, interface comes from TurboGears.
- Minimal configuration, after all thats why I started the project.
- SQLObject will be used to work with any database.
--Nickmudd 18:54, 30 May 2007 (PDT)