Re: Format considerations (Pieces)
Tim P. Gerla (timg nospam at means.net)
Tue, 9 Mar 1999 15:56:34 -0600
On Tue, Mar 09, 1999 at 06:07:43PM +0000, robin nospam at acm.org wrote:
> The way I was thinking of doing it was to have Pieces as first-order
> objects, which reference a sequence of tracks (which in turn belong
> to CDs).
>
> Your example:
> > Artist: Ludwig Van Beethoven / London Symphony Orchestra
> reminds me of something else that needs fixing---the grouping of
> useful information as unpareseable text. We should have:
> Disk123456789ABCDEF/Composer: Ludwig Van Beethoven
> Disk123456789ABCDEF/Orchestra: London Symphony Orchestra
> and generalise it so where appropriate we can have:
> Disk123456789ABCDEF/Track11/Soloist: Rousset
> (and similarly for Pieces, whichever way they work).
>
> Ideally, there should be a way of listing all database entries for each
> field, so clever clients could offer their users a menu rather than
> requiring free text entry every time.
>
Just stick it in a different file. Large files full of crap are slow to
load.
--
-Tim
timg nospam at means.net | http://flow.geol.und.nodak.edu/
Can you live your life in a day
Putting every moment in play
Never hear a word they say
As you watch the wheels go around
-Savatage