[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnump3d-users] Big changes - big bugs?
From: |
Steve Kemp |
Subject: |
Re: [Gnump3d-users] Big changes - big bugs? |
Date: |
Sun, 4 Dec 2005 14:32:24 +0000 |
User-agent: |
Mutt/1.5.9i |
On Sun, Dec 04, 2005 at 01:42:17AM +0100, C. Menge wrote:
> Wow - lots of changes came in today with the CVS-sync.
Indeed.
> Unfortunately, it broke quite some things for me too:
Yes.
> Some plugins completely stopped working.
> Every time I try to access one of them, I get the error page stating:
The plugin API is being reworked/improved. It is not yet complete.
If you run:
gnump3d --dump-plugins
You'll see the name/version of the working plugins. The rest are
not yet updated. Since you've mentioned it I'll aim to have them
all fixed tonight.
> > The requested file /search/ couldn't be found. Please try returning to the
> > index.
>
> where "search" can also be "tagbrowse", "playlist" or "random".
Yes - these plugins aren't ready yet.
> At the same time, there's HTML code in the title bar, here the content
> of the <title> tag:
> ----------------------
> GNUMP3d ::
> The requested file <code>/tagbrowse</code> couldn't be found.
That is a bad error - I've been bugged by this too and will endeavour
to update all the templates/code to avoid HTML in the title.
> The console readout always shows
> > Testing plugin : plugins::bug - for /search/ plugin won't handle path
> > Testing plugin : plugins::copying - for /search/ plugin won't handle path
> > Testing plugin : plugins::info - for /search/ plugin won't handle path
The new plugin system, rather than using hardcoded paths (e.g. /now/
-> current songs, or /search/ -> search page) tests each plugin
to see if it wishes to handle each incoming request.
So when a request is made for /foo/ each loaded plugin is iterated
over and given the opportunity to handle the request.
The text you're seeing is the debugging information for this
testing process. It will be removed/disabled by default once the
changes are fully implemented.
> It seems that by some reason GNUMP3d forgot their existence.
Nope, just doesn't use them since their API is incompatible.
> I had a quick glance at the source code, but couldn't find
> any obvious reason for this - probably because of my very
> limited knowledge of Perl...
Read "PLUGINS", or have a look at bin/gnump3d2, specifically the
usage of the array '@callbacks'. Anytime that is mentioned is a
plugin-related event.
> If this is just temprorary and part of the transition to the new plugin
> system, just ignore me - if not, please fix it anyway :-)
It is temporary, will be fixed, and should be over soon.
Remember CVS gives you interesting times ...
Steve
--