status on browser tab plugin

[Nikolaj Hald Nielsen]

Christopher,

Even though I know it is a large task, I pointed you in that direction for
several reasons.

First of all, no one (to the best of my knowledge) is currently working on a
plug in system / generic interface for these things. I will venture a guess
that I Will be doing a substantial amount of this work when the time comes,
and I doubt it will be happening for a  while still. I still have quite a
bit of work to do refining the Magnatune stuff and I really think that it
will be a mistake to branch out before this functionality is really solid.

Secondly, (and this is just my own personal opinion) I don't believe in
building frameworks from scratch. I have seen this fail too many times.
Instead I would much prefer, just like you mentioned, to factor out common
functionality from a number of similar, working,  features.

About being new to KDE/QT development, welcome to the club! :-) Seriously
though, I think you should be able to reuse the entire Magnatune browser and
its list view with few modifications (perhaps a with number of custom
QListViewItems). All you need to do is provide your own parser and database
handler (again, for the database the MagnatuedatabaseHandler should provide
a good starting point). If you do this, you will end up with a working,
albeit crude, implementation. from there it will be much easier to start
working on a framework that supports both our functionalities equally well.

Just my 2 cents, the other developers might not agree at all! :-)

- Nikolaj

On 11/13/06, Christopher Conroy <cconroy at gmail.com> wrote:
>
> My apologies...a stray mouse click sent my past message prematurely...
>
> ...continued:
> a DCOP interface that would allow one to setup a parser/fetcher/dbhandler
> to correspond to a  browser gui (a tree and some script defined buttons).
>
> Sorry for the split email...stupid terminal :P
>
> Thanks.
>
> On 11/13/06, Christopher Conroy <cconroy at gmail.com> wrote:
> >
> > Hey all. I think it would be a neat feature to provide some level of
> > integration with the etree live music archive http://www.archive.org/browse.php?collection=etree&field=%2Fmetadata%2Fcreator
> >
> >
> > I have mentioned this to Nikolaj, and he suggested that I just start
> > coding up something based off the Magnatune code and then would pull out
> > common functionality later. I'm hesistant to do this just because I am brand
> > new to KDE/QT development and would be a bit more comfortable working off a
> > well defined, extendable interface.
> >
> > So, my question is multipart:
> > 1) What is the status of defining a plugin structure for things *like*
> > magnatune. If it is still in development, are there some things a newbie
> > contributor like me could help with?
> >
> > 2) Has any consideration been given to making these sorts of things
> > scriptable (via DCOP?) It seems to me (after a very cursory examination of
> > some scripts and amarok code), that one could have a DCOP interface that
> > would
> >
> > --
> > Christopher Conroy
> >
>
>
>
> --
> Christopher Conroy
>
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok/attachments/20061113/372c6dcc/attachment.html>