API review

[Seb Ruiz]

During your refactor, please try and optimise as much as possible - we
use MetaBundles everywhere and pass them around like cake at a
birthday. Keep in mind that every object makes the bundle heavier and
heavier, so we really need to keep it slim.

seb

On 06/03/07, Maximilian Kossick <mkossick at gmx.de> wrote:
> Yes, I am planning on having different implementations of the same API.
> SqlTrack is an implementation which, for the time being, is tightly coupled
> to CollectionDB. We'll probably need a few other implementations to replace
> MetaBundle, for example one for last.fm stream, podcasts, and possibly normal
> streams, and one for songs from a daap share, i think.
>
> Max
>
> On Monday 05 March 2007, Ian Monroe wrote:
> > Could you explain the difference between Meta::Track and SqlTrack?
> > Meta::Track is completely abstract, I don't quite get its point.
> > Unless you plan on having different implementations of the same API?
> >
> > Ian Monroe
> >
> > On 3/5/07, Maximilian Kossick <mkossick at gmx.de> wrote:
> > > Hi
> > > I committed the first code for the MetaBundle replacement classes to
> > > src/meta and src/collection. src/meta contains the generic header file,
> > > src/collection contains the beginning of an implementation for our
> > > current SQL collection backend.
> > >
> > > Because replacing MetaBundle is going to be a major task and will touch
> > > basically all parts of Amarok, please review the API and improve/extend
> > > it (it doesn't have all the features of MetaBundle yet)
> > >
> > > Cheers, Max
>
>
>
>
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>
>
>


-- 
http://www.sebruiz.net/