Icebreaker::Design: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{historical}} | |||
= Design = | = Design = | ||
I've put a few things that I've been thinking about on this wiki page.<br> | I've put a few things that I've been thinking about on this wiki page.<br> | ||
| Line 20: | Line 21: | ||
::current- designates the currently running playlist, value is 1 or 0.<br> | ::current- designates the currently running playlist, value is 1 or 0.<br> | ||
:playlist- table, name of table is playlist? maybe incorporated in playlists table?<br> | :playlist- table, name of table is playlist? maybe incorporated in playlists table?<br> | ||
[[Category:Icebreaker]] | |||
Latest revision as of 15:04, 3 February 2008
Design
I've put a few things that I've been thinking about on this wiki page.
If you would like to comment, please make a note.
Database
Here is a simple structure with explanations.
Database: On a server or sqlite, doesnt matter.
- data- table; houses file data.
- path- path of file on the file system.
- genre- genre example: Rock
- artist- artist example: Misfits
- title- title example: Hybrid Moments
- album- album example: Static Age
- path- path of file on the file system.
- playlists- table; definition on databases, scheduling, defined in web-app.
- name- playlist name.
- description- description of playlist
- position- position in playlist, so that play is not started over from beginning. Incremented when track begins.
- day- scheduling, a string of days to play??? numbers 1-7.
- time- scheduling, a dictionary of times to play based with day (1-7) as key.
- current- designates the currently running playlist, value is 1 or 0.
- name- playlist name.
- playlist- table, name of table is playlist? maybe incorporated in playlists table?