The following modules failed to load: XML::Parser

[Fred]

This shows on start. Apparently XML::Parser is there in CPAN.

Fred

[Dan Sully]

* Fred shaped the electrons to say...

>This shows on start. Apparently XML::Parser is there in CPAN.

What OS / Perl version? I updated all the perl modules yesterday.

-D
--
<phone> i am a sausage fan

[Fred]

This is perl, v5.8.6 built for darwin-thread-multi-2level

Also the "forget" link is gone from the player setup page (checks that [page = "player"], did the popup menu code change page names?).

And the popup menu is not really useable as it is since it mixes up player and server preferences and I am not sure how it copes if there are multiple players...

Fred

[Dan Sully]

* Fred shaped the electrons to say...

>This is perl, v5.8.6 built for darwin-thread-multi-2level

Hmm.. ok. Would it be possible to get an account on your machine?

>Also the "forget" link is gone from the player setup page (checks that
>[page = "player"], did the popup menu code change page names?).
>
>And the popup menu is not really useable as it is since it mixes up
>player and server preferences and I am not sure how it copes if there
>are multiple players...

It's a work in progress - I'm sure kdf will have more in the coming days.

-Dan

[kdf]

And the popup menu is not really useable as it is since it mixes up player and server preferences and I am not sure how it copes if there are multiple players...

Fred

ARGH! sorry. left some plugin stuff that I hadn't meant to commit with the rest. the main server settings and player settings should be working fine, however.

The multiple player thing does work when entering from home (there is a link for each player. I haven't done the work for handling a change from the status side, but that will be the same code that I'm using to handle the fishbone skin's pulldown

[kdf]

Quoting Dan Sully <dan (AT) slimdevices (DOT) com>:


> It's a work in progress - I'm sure kdf will have more in the coming days.

I hope to. I wanted to get this one in becuase it was very large when
changing the page names to use tokens. I hadn't noticed that my first
commit failed and I went on to add plugins to the pulldown. I guess I
didn't take out the entire function before I committed.

Setup.pm line 2849 and PluginManager.pm lines 445 and 456 shoudl be
commented out. That should clean them up.

What should be there in the default skin is:

Home
Server Settings
followed by the usual tabs, plus iTunes/MMM/ML as req'd

Player settings should list:
Home
Player Settings
then the regular tabs

I dont have the page switching done yet for changing the player
settings if you change the player from the right side. However, I'm
thnking that since the links are all there from the home page, that the
settings don't need to be tied to the "current" player in the status
pane. I'm inclined to simply add the Player name to the header so that
it is clear which player's settings are open.

If you comment out the above and still have problems, please let me
know as this does not match what I see on my system. steps to
reproduce would be of use.

Note that only Default and Fishbone are calling up the pulldown. All
other skins still have the familar tab links.

The plan is to strip down the massive and daunting setup hash into
something that makes use of the prefs TT plugin, template toolkit and
css templates with more flexibility for custom form inputs. Validation
will be moved into javascript as the last phase. Plugins can then
register their own setup pages, or load their own set hashes to
existing templates.

I'm wide open to advice and tips.

-kdf

[Fred]

* Fred shaped the electrons to say...

>This is perl, v5.8.6 built for darwin-thread-multi-2level

Hmm.. ok. Would it be possible to get an account on your machine?
[color=blue]

Sure, just need to set it all up with NAT and all.

In the meantime, this is the error in tryLoadModule (or something in slimserver.pl):

Can't load '/Volumes/Sid/slimp3/trunk/server/CPAN/arch/5.8/darwin-thread-multi-2level/auto/XML/Parser/Expat/Expat.bundle' for module XML::Parser::Expat: dlopen(/Volumes/Sid/slimp3/trunk/server/CPAN/arch/5.8/darwin-thread-multi-2level/auto/XML/Parser/Expat/Expat.bundle, 1): no suitable image found. Did find:
/Volumes/Sid/slimp3/trunk/server/CPAN/arch/5.8/darwin-thread-multi-2level/auto/XML/Parser/Expat/Expat.bundle: unknown file type, first eight bytes: 0xCA 0xFE 0xBA 0xBE 0x00 0x00 0x00 0x02 at /System/Library/Perl/5.8.6/darwin-thread-multi-2level/DynaLoader.pm line 230.

I did get Expat from darwinports and installed XML::Parser using CPAN on my machine, and if I replace the server Expat.bundle with mine, it works

-rwxr-xr-x 1 fred admin 183152 Jan 20 20:07 Expat.bundle
-rwxr-xr-x 1 fred admin 183985 Jan 20 19:52 Expat.bundle.old

(.old is the one installed by svn).

Want me to commit it? My machine runs PowerPC but xcode is 2.1 or whatever that should support univeral binaries.

Let me know how to proceed.

Fred

[Fred]

Kevin,

I can live with it for the moment. I was just mentioning it as a strange behaviour I was seing.

While you're in the HTML stuff, what would it take to do 2798 (Call forget like any other command) and 2403 (descriptive text for plugins). Both require changing the HTML and the second one requires some formatting so I did not want to do them while changes were in progress. I can help, I just need gentle guidance...

Thanks

Fred

[kdf]

Quoting Fred <Fred.21ybdz (AT) no-mx (DOT) forums.slimdevices.com>:

>
> Kevin,
>
> I can live with it for the moment. I was just mentioning it as a
> strange behaviour I was seing.

np. Aside from the plugins being in the list, anything else would not
be what I'm seeing, so I'm happy to be made aware of it.

>
> While you're in the HTML stuff, what would it take to do 2798 (Call
> forget like any other command) and 2403 (descriptive text for plugins).
> Both require changing the HTML and the second one requires some
> formatting so I did not want to do them while changes were in progress.
> I can help, I just need gentle guidance...

Descriptive text for plugins, will probably be available. I'm really
in over my depth at this point, but I supidly told Dan I was bored

I'm still fleching out ideas, but I can certainly envision an API that
gives plugins the ability to register their own pages. This means no
more mile long scrol on the plugin settings. That will just be for
enable/disable. I supose this would allow for a bit more room for each
item. I supose each enable/disable option could be built up from each
plugin, rather than a server side single array.

I haven't looked at the forget command. I think its tied very deeply
into the client, but shoudl be possible.

Here is the basic top level as I see it now:

Setup will be made of pages listed in the pulldown. Plugins will each
have their own page for their settings. Each of these pages will be
css divided into groups. The groups will probably stay defined much as
they are now in teh setup hash, but reduced by removing all the layout
parameters. At minimum, a group provides a list of prefs. We'll use
Template Toolkit to jump through the list, loading a
"setup_<prefname>.html" file with javascript and css to handle layout
and validation. This way we build the pages from blocks, allowing the
skins to contorl layout and the plugins to provide their own setup
forms. Forget client can certainly be one of them:
setup_forgetclient.html, for example. If you want to create a small
page with a form button to issue a CLI command through the action url,
that would be one way to start. I can maybe use that to start building
a test backend to handlle it.

I've been out of the loop for a bit, so I'm going to be pouring over
code to get some idea of just how huge this might get

-k

[Fred]

I haven't looked at the forget command. I think its tied very deeply
into the client, but shoudl be possible.

Right now it is at the very top of Home.pm, if (param->{'forget'})... The change is an HTML one only, use the standard thing (url?command=client&subcommand=forget) and it should work...

I let you finish and we'll revisit that. There's no hurry.

Fred