Current Status of EoPK

[Paige]

After being sick and getting dumped on at work, I am now back to a
place that I can continue on with work on EoPK.

Can you let me know where you are? I'd like to set up a release in
the next few days or so.

I was looking at the XML settings stuff. Looks good. Great work on
tracking this down and smoothing it out.
Some questions:

XMLSettings.py,line 67: eopkSchemaLocation.nodeValue="http://
code.google.com/p/eopk/ http://www.torchdragon.com/l5r/settings.xsd"

For now, it's alright, but if for some reason your site goes away,
will the application have issues?
Can we point the schema location to the code site in some way? Also,
since it is "Open Source", the xsd should be included in the code
source .zip file. I don't know if it has been added to the setup.py
files list yet.

This brings up another issue. I am going to try to see if I can get
"Eggofpanku.com".

I think it would be really helpful if we had a simple site we could
use to "ping" files for checking for newer versions from within the
application. This is somewhat related to issue37, but would also allow
us to work with setting up some sort of "auto-update" feature. Also,
we could use this site to run the game matching service code.

Thoughts?

Finally, I am going to work on getting Issue27 & Issue34 done this
week.

Thanks,
Paige

[Bryan Buschmann]

Hey, glad you're feeling better.

Re: Schema location - The schema location was there just for some
testing that I was doing via online schema validation. You can
technically have the schema location a local file. Its a rather moot
issue however as there is currently no validation being done on the xml
file itself. There's no specific validation routine in the python
minidom library right now and I didn't feel it was worth it to add an
entirely different set of XML libraries just to handle that. I'd rather
just error handle a bad import and regenerate the file if there is an
issue with the xml file.

Getting a domain pegged down is definitely going to be a requirement for
any kind of matchmaking service I'd think. The auto update would also
have to trigger off a domain name as it'd break if we were hard
referencing IP addresses and had to change them on the back end.

On my plate this week is to bang out switching the Filters over to an
XML storage point.

-Bryan

[Paige]

I agree with you on the XML Library issue. No need to add more
libraries.

Domain is now mine. I will have a DNN site up shortly. In looking at
the auto update issues, we'll probably have to ping a "version" file
and check it's file date against the current local "version" file
date. Updating would be done by downloading the core eopk files in
a .zip and extracting them to the EoPK directory. maybe... still
trying this sort of thing out.
I found that the setup.py makes a "sys\library.zip" file in the builds
folder. I can copy this over the top of the same file on another
machine and get an "updated" version of my game. Except for the
EoPK.py file. It's not included in the "sys\library.zip"

I'll fix those quick issues on my plate and see where we're at on
Friday.

> > code.google.com/p/eopk/http://www.torchdragon.com/l5r/settings.xsd"

[Bryan Buschmann]

Alright. I'll work on implementing the XML items for filtering and
hopefully have it in and running by Friday as well.

-Bryan