Where to write CUE support code?

[Simon Bühler]

> 1. Locate the CUE when scanning
this code already exists 

> 2. Parse the CUE into timecode tracks
this is also present

> 3. Enter the split tracks into the database.
thats the big part left ...
 
> So a CUE track's url might look something like
> /home/ramblurr/Music/01-OhYea.mp3;path_to_cue;begin_point1;end_point1

wouldn't it be better to add a cue sheet table, throw in a forein key to the 
local track entry (fk_cuesheet_id, can be null)  and avoid string splitting in 
rpath completly?
The cue sheet table can contain also a uniqueid per cue sheet track so when a 
typo in the title or the cue sheet times are edited inside the amarok gui, the 
metadata can be synced easily with the cue sheet content or just be kept in 
amarok db if the cue sheet is not writable when playing from cd/dvds storage.

anyway, i'm looking forward to working cue sheet support, its been a long time 
(too long ) without