I agree with using the list for alpha testing, and opening up beta testing to the public (since they don't have to d/l anything, just run the servers scripts). May main concern is the PA licence. Untill I have stable code, the PHP, and text derived from the XML is going to be hosted on one of my machines for manipulation reasons. During the beta test (public) this will have the effect of serving book pages from a non-PA server. I figure I need either 1) The legal OK from PA to do so 2) Letting me set a folder one of my servers as an 'official' PA test server with the right to distribute under the PA licence (unchanged graphics and book text to keep everything inline with the text as presented on PA) Just got through the array section of my PHP/MySQL book. I should be getting to the MySQL basics in a week. At that time I'm going to tey and vreate the item/equpment tables, as well as the player table. Then I'll get the GUI shell up, and test equping and unequiping items to test the inventory system. Simon Osborne <outspaced@xxxxxxxxxxxx> wrote: Hi Sorry for the delay in replying. J H wrote: > Does this keep me good with the licencing issues (private only for PA > development) even though it's not on the PA server? And should I limit > testers to the mail-serve list vs. the forum (while hosted on my machines)? I'd suggest that the initial testing be opened exclusively to the list. The main reason for this would be to catch all the major errors in a pressure-free environment; if members of the public download something and it doesn't work, they generally get a bit irate (I know I do!), so if we can catch the worst of it in the first one or two releases, then would probably be a good time to open up Beta-testing to members of the forum. Just my own thoughts, of course. -- Simon Osborne --------------------------------- Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.