[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok-devel
Subject:    Re: DataPtr vs. TrackPtr in the collection browser
From:       "Alexandre Oliveira" <aleprjlists () gmail ! com>
Date:       2007-05-18 2:51:38
Message-ID: be280ab80705171951q63d6703dycc3942ae49a820e5 () mail ! gmail ! com
[Download RAW message or body]

Yeah, sure, for that it makes a lot of sense.


On 5/17/07, Ian Monroe <ian@monroe.nu> wrote:
> On 5/17/07, Alexandre Oliveira <aleprjlists@gmail.com> wrote:
> > Because for the collection model it doesn't matter what the data is.
> > As long as it knows how to extract information from it, no problem.
> > And DataPtrs are enough for that, at least for now, and makes things
> > much easier, as I don't need to handle them differently.
>
> So I'm going to implement a QList<Meta::TrackPtr>
> CollectionTreeItem::allDescendentTracks()
>
> I'll be looking for some code review when I commit the collection
> browser context menu. :)
>
> Ian Monroe
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel@kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>
_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel
[prev in list] [next in list] [prev in thread] [next in thread]