[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: Re: xPLMediaNet Seems to Work!
- Subject: RE: Re: xPLMediaNet Seems to Work!
- From: "Tony Tofts" <tony@xxxxxxxxxx>
- Date: Sun, 13 Mar 2005 18:01:14 -0000
Got it a bit wrong there
> The structure of module loading is like this:
>
> Core modules - loaded at startup
Core modules are actually any module section that isn't client, source,
utility, or transcoder
> Interface Modules - loaded at startup
Interface modules are as above (basically core modules)
A core module has a main module, any number of support modules, and as many
settings as required
Blimey, this is complicated ;-) But it's flexible too :-)
Some snippets:
The nfs module (that was for rio only) has been modified to get it's tar
file from any file name. So if a future client needs nfs then the same nfs
module can be loaded but with different settings... (and similar for
portmap, etc)
On the client side, defaults in the control file for things like volume are
passed to new clients. When clients are saved they are requested to write
their settings to the client.xml. Then when next booted they get the
settings they saved, rather than the default settings (they can also add
extra items that weren't defaults). This will make it very easy, for
instance, for each mvp to use different screen layouts
Although I've defined M, V, P for the current media types, these aren't
hardcoded - other than in the clients that need those media types. i.e.
rio/slim/exstr only use "M", but MVP uses all three
If we need a new media type for a new style client, we just specify that
media type in the control file and it _should_ all hang together.
Regards
Tony
xPL Links: http://www.xplproject.org.uk http://www.xplhal.com http://www.xpl.myby.co.uk
To Post a Message: ukha_xpl@xxxxxxx
To Subscribe: ukha_xpl-subscribe@xxxxxxx
To Unsubscribe: ukha_xpl-unsubscribe@xxxxxxx
xPL Main Index |
xPL Thread Index |
xPL Home |
Archives Home
|