Client Server www

xlobby docs (works in progress)

Client Server www

Postby stevenhanna6 on Fri Apr 01, 2005 6:40 pm

How to setup client/server in xlobby for thin clients.
<p></p>A Pocket PC (PPC) and a PC client are the exact same, they behave the same way. The only difference is the start screen. For our purposes we will call the xlobby2sd.exe client a "thin client" meaning everything is stored on the server side, do not confuse the thin client with the fat client which is much more powerful and must be run on a PC.
<p></p>When we talk about client server in xlobby we are really talking about independent client server. This is a rather unique feature that cannot be achieved using a remote desktop program like vnc for example. What the feature allows you to do is have multiple clients logged on to the server, but all doing independent things. One client could be looking at movies and the other could be playing music. The number of clients one can have connected to the server at anyone time is only limited by your computer resources. But its probably a safe bet that most people could run 10 clients at once.
<p></p>Now some people get confused thinking that xlobby will actually playback movies or music through the client. It will not do this (use xlobby byitself to do this). The client is basicly a remote control for the server, exactly like a remote desktop but with the independent capabilities I described earlier.
<p></p>Ok, you only need 2 files for this client program to work.
<p></p>You dont need anything else, make sure those 2 files are in the same folder.
<p></p>2 easy steps to running the client.
<p></p>1. Make sure xlobby is running in server mode on your server machine.<br>
2. Start xlobby2sd.exe<br>
<p></p><em><strong>Pocket PC</strong></em><br>
<p></p>.net compact framework <br>
<a class='urllink' href=''>;displaylang=en</a>
<p></p><em><strong>Normal PC</strong></em><br>
MAKE SURE YOU HAVE THE .NET FRAMEWORK INSTALLED. You need this to run the xlobby client program. It's the same you had to install to get xlobby server working.
<p></p><h2>"servers.txt" file variables</h2>
<p></p>IP or servername to the computer running xlobby in server mode
<p></p>the first screen you wish the client to show on startup
<p></p>the resolution you wish to use, should be set to "auto" unless speed becomes an issue. If your having speed issues try setting a lower resolution while keeping the aspect ratio the same. So if your client is running at 800x600 you could try 640x480 or 320x240 because they all have the same aspect ratio.
<p></p>This should be set to 100%, unless your having speed issues. Again simple lower the value to lower the quality, this will increase the speed but lower the picture quality.
<p></p><h3>zone: (optional)</h3>
<p></p>This is an optional setting to set the current audio zone on startup in a multizone environment, you can use the actual zone name or use a number starting from 1.
<p></p><h3>navigationpad: (optional)</h3>
<p></p>Basicly only used for pocket pc clients, it allows them to send button presses from the navigation pad as hard buttons.
<p></p><h3>bindbuttons: (optional)</h3>
<p></p>Pocket pc clients only. This will cause all hardbuttons on the pocket pc to be binded. You can unbind individual ones with the option below.
<p></p><h3>unbindbuttons: (optional)</h3>
<p></p>Again only used for pocket pc clients. Instead of binding xlobby to all the hardbuttons on the pocket pc, you can define which buttons you want to unbind. This is done by specifying the the button code, you can get a button code on the xlobby server through the eventmanager in the hardbuttons trigger section.
<p></p><h3>refresh: (optional)</h3>
<p></p>Number in milliseconds between refreshes, I wouldn't use anything less than 1000 (1000 = 1second), simply add "refresh:1000" to try this refresh option.
<p></p><h3>border: (optional)</h3>
<p></p>If you want to show a border around the client application. Use "border:true" if you want to.
<p></p><h3>mimic: (optional)</h3>
<p></p>If you want mimic mode activated on startup. Use "mimic:true" if you want to. By default it is off.
<p></p><h3>width: (optional)</h3>
<p></p>This will allow you to set the width of the client instead of its default fullscreen. For example "width:300".
<p></p><h3>height: (optional)</h3>
<p></p>This will allow you to set the height of the client instead of its default fullscreen. For example "height:300".
<p></p>If you wanted to connect to a server at IP, have the startup screen "menu",a resolution of "640x480", and a quality of "95%" you would put the following in your servers.txt file. I have also added the optional zone setting to start controlling audio zone 2.
<p></p>server: <br />screen:menu <br />resolution:640x480 <br />quality:95% <br />zone:2
<p></p>And if you want to use the default settings you should do something like this
<p></p>server: <br />screen:menu <br />resolution:auto <br />quality:100%
<p></p>Advanced Pocket pc example, using the navigation pad and unbinding specific buttons.
<p></p>server: <br />screen:ppcmenu <br />resolution:auto <br />quality:100% <br />navigationpad:true <br />unbindbuttons:340,300
Last edited by stevenhanna6 on Tue Apr 05, 2005 6:54 pm, edited 1 time in total.
Posts: 934
Joined: Tue Feb 18, 2003 10:39 am
Location: Ontario, Canada

Postby rhinoman on Sat Apr 02, 2005 7:29 am

The PPC example should have

screen:ppcmenu instead of menu

Xlobby-Server: AMD64x2 4400+, 1gb ram, MSI NF4, RME 96/52 HDSP, 2*aeb8o for 8 zones feeding amps with long speaker runs, 2 touchscreen's and 2 Dell X5 PPC's. "Unraid" media storage.
Posts: 420
Joined: Wed Jan 14, 2004 8:58 pm
Location: Herne Bay, UK

Postby stevenhanna6 on Tue Apr 05, 2005 6:54 pm

thanks rhinoman
Posts: 934
Joined: Tue Feb 18, 2003 10:39 am
Location: Ontario, Canada

Postby bmblank on Fri Jun 30, 2006 1:07 pm

I have a question about the thin clients. I'm only a couple days into xlobby and my brother and I are planning on implementing it in our (his) house as well as in my truck. The first question I have is in reply to your advanced ppc example. I have a dell axim x3i and xlobby with the kiss skin just kicks butt. Anyhoo in the line "unbindbuttons:310,300" or whatever, is that saying that the xlobby server is associating those two ppc hard buttons with the codes 310 and 300, so then in turn the thin client is unlocking those two buttons for use? Another question I have is the sizing of the screen. I'd like to make my xlobby a little smaller so I can still see the bar at the top of my ppc screen. How would I do that? I'd imagine I change the size and then change the originating point to match... A third question I have is about 2 servers. Is it possible to use my axim to connect to both the house xlobby and then my truck xlobby (not at the same time)? If the IPs are the same then it should "just work" correct? In that case I'd give up the ability to network my truck with the house. Would I have to have two instances of xlobby (instead of one and changing the .txt file every time), one for 192.168.1.x and one for 192.168.1.y? I'm not bad with computers, but I am by no means a programmer or write code make skins or plugins. I'm an engineer, so I'm resourceful. Anyhoo, thanks for the great program, it's neat.
Posts: 233
Joined: Fri Jun 30, 2006 12:55 pm

Postby Marbles_00 on Fri Jun 30, 2006 2:50 pm

Not sure, but I think you would have conflict errors if you had both your home server and truck at the same IP address, and you tried to access one while in the area of the other. I've never tried it but couldn't you set up two clients in seperate directories, each with their own test setup file. One directed at the home server, and the other directed at the truck server. Then just rename the client.exe to suit? Worth experimenting

Hope this was helpful
Mayhem Creations
where my:
    -Music Distribution
    -UnRAID box
are all discussed.

Xlobby Free Zone
Posts: 1882
Joined: Wed Apr 06, 2005 12:44 pm
Location: Canada

Postby bmblank on Fri Jun 30, 2006 3:35 pm

Thats what I was figuring I'd have to do just for the fact that I might want to network my truck to the house some time... It'd be nice to have one button to do whatever though. Maybe somebody could write up a script in which you put in the .txt file something like 192.168.1.* and that would indicate it to search for any server on that subnet (is that the right word??). Then if it happened to find two, it could ask which one to connect to, or something to that effect. I use remoteamp (for controlling winamp with the axim) and that's what it does. Pretty nice.
Posts: 233
Joined: Fri Jun 30, 2006 12:55 pm

Return to Documentation

Who is online

Users browsing this forum: No registered users and 1 guest