*** tpb has joined #tp | 00:00 | |
*** ChanServ sets mode: +o tpb | 00:00 | |
*** Greywhind has joined #tp | 00:25 | |
*** Greywhind has quit IRC | 00:59 | |
*** Greywhind has joined #tp | 01:01 | |
*** peres has left #tp | 01:04 | |
llnz | mithro: i'm around | 01:25 |
---|---|---|
mithro | llnz: has all the money been sorted or is it still waiting to be paid? | 01:26 |
llnz | i'm still waiting | 01:27 |
llnz | could take another 2 weeks or so | 01:27 |
mithro | stupid payment systems | 02:35 |
CIA-23 | jmingtan tpclient-pyogre * r177e3031196c /src/ (6 files): Updated methods to match Python-Ogre 1.6.1 | 02:47 |
ezod | mithro: pong | 02:54 |
mithro | hey ezod | 02:54 |
ezod | hello | 02:54 |
mithro | so how goes things? | 02:54 |
ezod | not bad | 02:55 |
ezod | feeling a bit better now that i dropped one of my courses :) | 02:56 |
ezod | way too much on my plate this semester | 02:56 |
mithro | so where are we at with single player? | 02:56 |
ezod | well, it works on linux | 02:56 |
mithro | ezod: oh, we should nuke the single player branches | 02:57 |
ezod | i was hoping you could take a look and consider starting the merging | 02:57 |
ezod | excellent | 02:57 |
mithro | I'm happy enough to do that | 02:57 |
ezod | ok, have you seen the wizard in action? | 02:57 |
ezod | a bit ugly still, and has some quirks, but usable | 02:59 |
mithro | I'm just about too | 03:00 |
ezod | it certainly needs work before being "finished" | 03:01 |
ezod | i haven't had time to really learn wx/etc. to do that | 03:01 |
ezod | the libtpclient-py stuff works well on linux | 03:02 |
ezod | as far as i recall it worked fine on win32 as well, but i haven't tested it recently still | 03:02 |
mithro | how does the developer setup work? | 03:02 |
ezod | switch tpclient-pywx to singleplayer branch | 03:03 |
ezod | make sure submodules are pulled | 03:03 |
ezod | and manually switch libtpclient-py to singleplayer branch | 03:03 |
ezod | i also have actual installed packages of tpserver-cpp-0.6.0 and daneel-ai | 03:04 |
ezod | with xml files in /usr/share/tp or whatever | 03:04 |
mithro | where do you search again? | 03:06 |
ezod | 1 sec, ill paste the path | 03:06 |
mithro | do you check an environment variable? | 03:06 |
ezod | line 50 of SinglePlayer.py | 03:06 |
ezod | sharepath = ['/usr/share/tp', '/usr/share/games/tp', '/usr/local/share/tp', '/opt/tp', os.path.join(installpath, 'tp/client/singleplayer')] | 03:06 |
ezod | hardcoded basically | 03:07 |
ezod | but the installpath lets you put them locally, for testing etc. | 03:07 |
ezod | win32 looks in the registry for keys put there by packages | 03:07 |
ezod | so.. the packages will need to put the keys there :) | 03:08 |
ezod | s/keys/values | 03:08 |
* mithro tries to see if debs work | 03:08 | |
ezod | if you just want to see the wizard work quickly, you can just paste a few xml files from the wiki somewhere it looks | 03:10 |
ezod | http://thousandparsec.net/wiki/Single_Player | 03:10 |
tpb | Title: Single Player - Thousand Parsec Wiki (at thousandparsec.net) | 03:10 |
ezod | recall that server ones go under servers/ and ai clients under aiclients/ | 03:10 |
ezod | im also about to update the testing procedure on that wiki page | 03:12 |
mithro | ezod: maybe it's a good idea to setup some default ones which are used in developing | 03:13 |
mithro | it's okay to assume that the stuff is in a directory above the current client | 03:13 |
ezod | what i did for gsoc was just add some sample xml files to the libtpclient-py repo | 03:15 |
ezod | is that what you mean? | 03:15 |
ezod | (they aren't there anymore) | 03:15 |
ezod | like, i could put some samples that don't actually run anything - would let you complete the wizard, but the client would of course fail to connect to anything afterward | 03:17 |
*** jmtan has joined #tp | 03:18 | |
mithro | what I mean is that most people do the following | 03:19 |
mithro | 1) checkout everything into the same directory | 03:19 |
mithro | 2) expect it to work | 03:19 |
mithro | having a devel setup which works is a good thing | 03:19 |
ezod | ok, i'm just pointing out that it can only "work" up to that point | 03:20 |
ezod | i can't point it at a server that doesn't come with the repo | 03:21 |
ezod | so in that sense, it works just as well with no xml files at all | 03:21 |
ezod | but what i can do (as previously) is make it show you every possible thing it can do with bogus xml files | 03:22 |
mithro | so | 03:22 |
mithro | way somebody has tpserver-cpp checkout to a directory called tpsever-cpp | 03:22 |
mithro | can't you just find that? | 03:22 |
ezod | find it how? | 03:23 |
ezod | here's the problem | 03:24 |
ezod | the xml file contains a lot of specific info, including path to executable | 03:24 |
ezod | i can't provide the xml files with libtpclient-py, because then you'd have to add to libtpclient-py every time you made a new server/aiclient/ruleset | 03:25 |
ezod | in fact, every time you changed something about how it runs pertinent to it | 03:26 |
ezod | so that's not an option, to my mind | 03:26 |
ezod | so i could have libtpclient-py look for tpserver-cpp repo's xml file | 03:26 |
ezod | but where? | 03:26 |
ezod | and then, once it finds it, there's the issue of the executable path being wrong, as the xml file is written expecting tpserver-cpp to be installed | 03:27 |
ezod | i.e. the build system puts in the path | 03:27 |
mithro | hrm | 03:28 |
ezod | so we could maybe rethink how this whole thing works | 03:28 |
ezod | but i spent an awful lot of time doing that last summer :) | 03:28 |
mithro | It seems like you could just write a "relative" xml file | 03:28 |
mithro | then use that for the uninstalled stuff | 03:29 |
ezod | i can see one way to do that as things stand | 03:30 |
ezod | basically, put the xml file in the same dir as the executable is or will be, in the repo path | 03:31 |
ezod | in all packages | 03:31 |
ezod | another thing i was thinking was just to give devs some easy way to generate them | 03:31 |
mithro | what I'm thinking is that each git repo has a "development.xml" which specifies relative to the checkout directory the excutables | 03:32 |
ezod | including quick ones that reference their own local working dirs | 03:32 |
ezod | ok | 03:32 |
mithro | it also as a "installed.xml" which is used when packaging | 03:32 |
ezod | ah | 03:32 |
mithro | (or what ever the current name is) | 03:32 |
ezod | so then one thing remains | 03:32 |
mithro | make more sense now? | 03:32 |
mithro | keeping them in sync is a bit of a pain | 03:33 |
mithro | but we can solve that problem later | 03:33 |
ezod | well if i write a script to generate it or whatever.. | 03:33 |
ezod | plus it's really just the executable path to worry about there, possibly we can do this with a single file, i'll see what i can figure out | 03:33 |
ezod | but there's still this: | 03:33 |
ezod | how does libtpclient-py know about these other repos? | 03:33 |
ezod | the checked-out libtpclient-py i mean.. how does it find other tp repos? | 03:34 |
mithro | if it finds a .git directory it looks up one directory and checks each directory for a development.xml | 03:34 |
ezod | searches the entire filesystem? | 03:34 |
mithro | no | 03:34 |
mithro | just up one directory | 03:35 |
mithro | pretty much everyone has a checkout seutp like | 03:35 |
ezod | oh i see | 03:35 |
ezod | fair enough | 03:35 |
mithro | all the tp stuff checked out in a single directory | 03:35 |
ezod | yeah | 03:35 |
mithro | if you want to be really facy have a "TPPATH" or something which defaults to ".." when development and normal search locations when not | 03:37 |
ezod | also, the xml files currently live in various places in the server/ruleset/aiclient repos... | 03:37 |
ezod | and, e.g., tpserver-cpp has more than one | 03:37 |
ezod | ok, can do | 03:37 |
ezod | without disturbing that setup, can i just poke through the entire tree of each looking for xml files that use the proper dtd? | 03:37 |
mithro | that will be slow I was just going to dump one file in the top level directory | 03:38 |
mithro | (ie development.xml in tpserver-cpp | 03:38 |
ezod | i know, but (a) it's only for devs, and (b) having to put everything in one xml file in the top level dir is not ideal at least for tpserver-cpp | 03:39 |
mithro | okay | 03:39 |
ezod | as they are supposed to be modular with the rulesets and all | 03:39 |
mithro | well what ever works | 03:41 |
ezod | ok, on it | 03:43 |
ezod | thanks | 03:43 |
mithro | do you have much time tonight? | 03:45 |
mithro | I assume it's pretty late where you are | 03:45 |
ezod | 3:45am :( | 03:46 |
mithro | dang I was hoping that we could knock of some of this stuff | 03:47 |
mithro | what are your plans next weekend? | 03:49 |
ezod | free, to my knowledge | 03:49 |
mithro | could we organise a hack session to knock all these remaining issues off? | 03:49 |
ezod | aside from the usual deluge of school work, but given warning i can push it aside | 03:49 |
ezod | sure | 03:50 |
ezod | what range of hours works for you? (UTC) | 03:50 |
ezod | my sleep schedule is all over the place so anytime is basically fine for me | 03:51 |
mithro | what timezone are you in? | 03:51 |
ezod | EST | 03:51 |
mithro | which is which city? | 03:52 |
ezod | toronto, new york, montreal | 03:53 |
mithro | http://www.timeanddate.com/worldclock/meetingtime.html?month=3&day=1&year=2009&p1=0&p2=240&p3=250&p4=-1 | 03:55 |
tpb | <http://ln-s.net/2wHg> (at www.timeanddate.com) | 03:55 |
mithro | how does this look | 03:55 |
mithro | Die Remote Console (LARA) ermöglicht Ihnen die Fernwartung Ihres Servers. Die Anzahl der zur Verfügung stehenden LARAs im Rechenzentrum ist begrenzt. Bei Buchung wird Ihnen eine Nutzungsdauer von 2 Stunden eingeräumt. Sofern die Remote Console nach Ablauf dieser Zeit nicht weiter verplant ist, kann sie ggf. weiter verwendet werden. Benötigen Sie die LARA garantiert länger als 2 Stunden, so kann sie für je 2 Folgestunden für 10 Euro (inkl. MwSt.) gemi | 03:55 |
mithro | etet werden (z.B. LARA für 6 Stunden = 20 Euro). | 03:55 |
mithro | Weitere Informationen zur Remote Console finden Sie hier. | 03:55 |
mithro | opps | 03:55 |
mithro | http://www.timeanddate.com/worldclock/meetingdetails.html?year=2009&month=2&day=28&hour=23&min=0&sec=0&p1=240&p2=250 | 03:55 |
tpb | <http://ln-s.net/2wHj> (at www.timeanddate.com) | 03:55 |
mithro | that is 6:00pm your time | 03:57 |
ezod | okay, so next sat 6pm - | 03:57 |
ezod | right | 03:57 |
mithro | yeah I'll setup a meeting invite | 03:57 |
ezod | ok, sounds good | 03:57 |
mithro | sent the meeting request | 04:03 |
mithro | do that look right? | 04:03 |
ezod | yep, cool | 04:04 |
mithro | ezod: so I'm assuming you have gone now? | 04:27 |
* llnz wanders off | 05:11 | |
llnz | later all | 05:11 |
*** llnz has quit IRC | 05:11 | |
mithro | hey jmtan | 05:58 |
jmtan | hi mithro, it's been a while | 06:03 |
mithro | yeah | 06:03 |
mithro | I saw your commits | 06:03 |
jmtan | i've not tested them in linux yet, my linux box just died this week | 06:04 |
jmtan | i'm setting it up on my laptop atm | 06:04 |
mithro | cool | 06:04 |
mithro | jmtan: so I'm assuming you have not played spore? | 06:09 |
jmtan | no i haven't, i've looked at some screenshots after getting your email though | 06:10 |
mithro | you want to take a look at the space map and the ship builder | 06:10 |
jmtan | oh yeah, the space map is pretty cool | 06:14 |
jmtan | i'm not too sure how the ship builder works, i've only found a single shot of it | 06:17 |
jmtan | but, is it a set of pre-built parts put together? | 06:18 |
mithro | yes | 06:18 |
mithro | it works quite well | 06:24 |
jmtan | btw, i'm not sure if it is osx-specific, but i get this error thrown when i'm in the login phase of the client | 06:35 |
jmtan | http://pastebin.com/d7c9fe690 | 06:35 |
tpb | Title: pastebin - collaborative debugging tool (at pastebin.com) | 06:35 |
jmtan | commenting out the line seems to work fine though, perhaps my version of python has a missing module | 06:36 |
mithro | hrm what version of Python do you have? | 06:36 |
jmtan | 2.5.1 | 06:37 |
mithro | hrm... | 06:37 |
mithro | what happens if you do | 06:37 |
mithro | python | 06:37 |
mithro | import encodings | 06:38 |
mithro | dir(encodings) | 06:38 |
mithro | jmtan: what does that output? | 06:41 |
jmtan | ['CodecRegistryError', '__builtins__', '__doc__', '__file__', '__name__', '__path__', '_aliases', '_cache', '_import_tail', '_norm_encoding_map', '_unknown', 'aliases', 'codecs', 'normalize_encoding', 'search_function', 'types'] | 06:41 |
mithro | hrm | 06:42 |
mithro | can you do a | 06:42 |
mithro | import encodings.utf_8 | 06:42 |
mithro | ? | 06:42 |
jmtan | it seems to work fine | 06:46 |
mithro | hrm | 06:49 |
mithro | okay | 06:50 |
CIA-23 | mithro libtpproto-py * raafce7adda3a /tp/netlib/xstruct.py: Import encodings.utf_8 as some systems don't auto-import. | 06:51 |
mithro | jmtan: give that a try? | 06:51 |
jmtan | sure | 06:52 |
jmtan | it works fine now :) | 06:56 |
mithro | cool | 07:14 |
JLP | good morning everyone | 08:10 |
*** peres has joined #tp | 09:35 | |
*** peres has left #tp | 10:59 | |
*** jmtan has quit IRC | 11:54 | |
*** DTRemenak|RDP has joined #tp | 12:39 | |
*** DTRemenak has quit IRC | 12:55 | |
*** llnz has joined #tp | 13:48 | |
*** nash has joined #tp | 18:00 | |
*** DTRemenak|RDP has quit IRC | 18:42 | |
*** nash has quit IRC | 18:58 | |
*** DTRemenak has joined #tp | 18:59 | |
*** mithro has quit IRC | 19:03 | |
tansell | Morning people | 19:13 |
*** nash has joined #tp | 19:21 | |
*** Demitar has quit IRC | 21:13 | |
*** tansell has quit IRC | 21:13 | |
*** Demitar has joined #tp | 21:13 | |
*** tansell has joined #tp | 21:13 | |
*** mithro has joined #tp | 21:31 | |
*** llnz has quit IRC | 22:33 | |
mithro | hey people | 22:36 |
mithro | hey ezod | 22:36 |
mithro | poke me when/if you are around | 23:00 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!