RFC: Cleaning up Trunk

[Dan Meltzer]

I removed playlist and its friends today.  Metabundle and collectiondb
will probably require a whole lot more love.

On 9/4/07, Maximilian Kossick <mkossick at gmx.de> wrote:
> On Tuesday 04 September 2007, Seb Ruiz wrote:
> > Hi Devs,
> >
> > I'm wondering if it would be worthwhile to rip out all of the old 1.4
> > amarokisms from trunk. By this, I mean everything which hasn't been
> > ported yet.
> > eg:
> >  - Playlist
> >  - PlaylistItem
> >  - MetaBundle
>
> especially MetaBundle should probably be kept around for reference (yes i
> know, we could just look in previous svn revisions for, but that's not very
> convenient). there's some code in there which still need to be ported, but
> MetaBundle itself should be removed. Maybe we could move the files into a new
> directory, and delete them later.
>
> >
> > I know, it's a HUGE amount of work, but maybe it would help us in
> > clearing out the codebase and understanding the new development
> > techniques we are using. Another advantage is that it would help make
> > obvious the giant holes we have in trunk.
>
> Removing MetaBundle will probably mean breaking trunk for a few days. I don't
> think one person can do it alone in a local checkout. But I think it's
> worthwhile doing.
>
> > Obvious disadvantages would be that we would need to keep an older
> > revision checked out locally to do any comparisons etc.
> >
> > We have at least a start on most of the major components of Amarok 2:
> > Interface, Context, Playlist, Collections, Collection browser,
> > Playlist browser, services.
> >
> > I don't imagine that the rest of the components would be refactored,
> > but probably written again from scratch (with previous knowledge or
> > referencing 1.4 code).
> >
> > Comments?
>
>
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>
>
>