Towards Amarok Mobile: Beginning separation

[Ian Monroe]

On Sat, Mar 20, 2010 at 11:26 AM, Jeff Mitchell <mitchell at kde.org> wrote:
> On 03/20/2010 05:00 AM, Maximilian Kossick wrote:
>> Moving all those classes into meta/ does not make a lot of sense imo.
>> They are not providing track metadata after all.
>
> Neither does a Playlist, but that's sitting in meta/. It seemed like
> meta was a location for general metadata, not track metadata specifically.
>
>> If you are planning
>> to do that refactoring, I suggest creating a "Core API" library
>> instead. Which could then continue to have the internal distinction
>> between meta/ and collection/.
>
> I could do that. That basically just means shuffling around directories
> to create e.g. core/meta/ instead of meta/. That would end up as a very
> large amount of busywork fixing build breakage, though.

It's busywork, but it is mindless busywork and its good for reaching a
Zen state if you're after that. :)

Seriously though it's important that any core/gui or qt/kde separation
happen very very very clearly at the directory level or else things
get confusing.

Ian