| *** tpb has joined #tp | 00:00 | |
| *** ChanServ sets mode: +o tpb | 00:00 | |
| mithro | howdy people | 00:20 |
|---|---|---|
| mithro | sup? | 00:20 |
| nash | heyo mithro | 00:21 |
| mithro | nash: how goes everything? | 00:25 |
| nash | Getting there... | 00:25 |
| nash | We shopuld have internet toady or tomorrow | 00:26 |
| nash | Which is good | 00:26 |
| nash | Internet will follow shortly after | 00:26 |
| mithro | cool | 00:32 |
| nash | And I'll try and get some hacking done on teh train this afternoon | 01:02 |
| mithro | nash: cool! | 01:06 |
| * mithro ponders | 01:07 | |
| * mithro has so much he should be doing | 01:07 | |
| nash | Games are #1... second would be TP04 | 01:08 |
| jotham | i have my new lasers in | 01:08 |
| mithro | jotham: so, can we see a demo? | 01:08 |
| jotham | once the particle emitters are done i'll readd the battle parsing stuff to it | 01:08 |
| jotham | i'm at work right now, but sure in the next few days | 01:08 |
| mithro | jotham: that would be cool | 01:08 |
| jotham | that guy is making a whole set of spaceships | 01:08 |
| jotham | they will be GPLed | 01:09 |
| jotham | the format is C4D though since that's what he works with | 01:09 |
| nash | mithro: There is something - a documented protocol for media and battle data ;-) | 01:10 |
| mithro | nash: the battle-data is documented! (kind of :) | 01:11 |
| mithro | is it just me or is demo1 looking kind of sparse | 01:11 |
| nash | mithro: And a protocol for getting it? | 01:12 |
| mithro | nash: that is in tp04 | 01:12 |
| nash | So it's back to TP04 and rules then ;-) | 01:12 |
| mithro | well, the recent additions to libtpproto2-py make TP04 a bit closer for the python clients | 01:15 |
| mithro | greywhind: ping! | 01:17 |
| mithro | xdotx: how goes RFTS? | 01:17 |
| xdotx | mithro: hmm, well i just noticed the star map is in 1st quad. i just kinda naturally assumed 4th | 01:18 |
| mithro | xdotx: hrm? | 01:18 |
| xdotx | mithro: like graph quadrants. the y axis is up, x right. i assumed y was positive down (4th) | 01:19 |
| nash | xdotx: Doesn't matter ;-) | 01:19 |
| * xdotx nods | 01:19 | |
| nash | The universe is consistent either way | 01:20 |
| mithro | xdotx: 0,0 is in the "center of the map" | 01:20 |
| mithro | you can go x can be +/- and so can y | 01:20 |
| xdotx | but i started mapping out RFTS's star systems and suddenly noticed they were all upside down ~~ | 01:20 |
| nash | xdotx: We'll live... and everyone plays with random maps anyway... | 01:21 |
| nash | BTW Did you do advanced or basic rules? | 01:21 |
| * nash hopes advanced is the answer | 01:21 | |
| nash | it's a much better game... | 01:21 |
| xdotx | i'm going for basic rules and i plan to add more later | 01:21 |
| nash | d'oh | 01:21 |
| nash | scouts suck ;-) | 01:21 |
| xdotx | i'm dealing with an interesting problem right now actually | 01:21 |
| * nash likes interesting problems ;-) | 01:22 | |
| xdotx | the original game has mechanisms to allow you to essentially do orders in the middle of the turn | 01:22 |
| nash | Only the withdrawel orders... | 01:22 |
| xdotx | that sort of thing is not well supported | 01:22 |
| nash | Just add a retreat % ;-) | 01:22 |
| nash | It's not supported at all without additional combat only turns | 01:23 |
| xdotx | more interesting than that! what about production? | 01:23 |
| nash | What about it? | 01:23 |
| nash | You produce at the begining of a turn | 01:23 |
| xdotx | yes, immediately. | 01:23 |
| nash | So you can either add a turn for production only - so it turns from prod+move, move to prod,move,move | 01:24 |
| xdotx | and then you can use those new resources to make fleets, again, available immediately, and then move those fleets | 01:24 |
| xdotx | but i'm processing orders in the middle of the turn, which isn't well supported | 01:24 |
| nash | I thought you had to finish all production before you could move | 01:24 |
| nash | Just turn the 2 turn cycle into a 3 turn cycle | 01:25 |
| nash | Or add a 1 turn lag for production | 01:25 |
| nash | Actually that 2nd idea sucks | 01:25 |
| nash | Make it a 3 turn cycle | 01:25 |
| nash | No move or combat on the production turn, just production... then do move | 01:25 |
| xdotx | the ideas i'm playing with now are 1) do the longer turn cycle, or 2) have a sort of "do production" order, that when created.. does production. same for fleet creation | 01:26 |
| mithro | xdotx: on a side note, Thousand Parsec has the rule that "nothing can modify the universe except during turn processing" | 01:27 |
| xdotx | ah... longer turn cycle it is? | 01:28 |
| nash | xdotx: Indeed in that case | 01:28 |
| xdotx | that should be pretty straight forward | 01:28 |
| nash | Should be... on the negative it will slow the game done | 01:29 |
| nash | s/done/down/ | 01:29 |
| mithro | xdotx: and all the protocol/clients make that assumption | 01:29 |
| nash | On the positive it should make varients of different prod/non-prod turns easier to design | 01:29 |
| nash | mithro: I know one client that doesn't ;-) | 01:30 |
| mithro | nash: so you continually check that objects have changed? | 01:30 |
| nash | Not specficially - but I can... that's what the tick event is for. I do have an infrastructure for change events when they occur to update pretty much any objhect at any time. Which is why the client does turn updates async after it discovers the new turn. It doesn't assume turn events are all atomic essentially... You could in fact fire off updates during turn generation | 01:32 |
| nash | bbs | 01:34 |
| nash | mithro: Do you use adelaid bank by any chance? | 01:41 |
| mithro | nash: I believe my parents do | 01:42 |
| nash | okay | 01:42 |
| nash | Hmm... /me wonders what my customer number is | 01:42 |
| nash | Ahh.. found my mailing list problem | 02:19 |
| nash | Stupid anti-spam filters at work | 02:19 |
| mithro | nash: :/ | 02:22 |
| nash | mithro: BTW I want to get galaxie ready for a release as a _viewer_ only shortly | 02:24 |
| nash | mithro: Can I add another public key to the tp server so I can pull and push from my laptop? | 02:27 |
| mithro | nash: sure! | 02:27 |
| nash | I _may_ have just emailed it to you... can you see if you just got an email at [email protected] | 02:28 |
| nash | I assume that address works | 02:29 |
| nash | mithro: Acrtually just pasted it to you ;-) | 02:30 |
| * mithro assumes that it works too | 02:30 | |
| nash | You need to fix the formatting | 02:30 |
| mithro | hrm... maybe not | 02:31 |
| nash | No query window from me? | 02:31 |
| mithro | nash: you have two keys uploaded already? | 02:32 |
| nash | mithro: Is there a quick list of depends I need for tpserver-cpp I need | 02:32 |
| nash | mithro: Should be my desktop at home and at work - tranquillity and baboon | 02:32 |
| nash | This is serenity | 02:32 |
| mithro | okay | 02:32 |
| mithro | should be added now | 02:33 |
| mithro | hrm, no email however | 02:34 |
| nash | mithro: Probably set up to go via my home machine... so if you get it next week some time... ignore it | 02:35 |
| mithro | okay :P | 02:36 |
| nash | mithro: BTW... now you've been using git for a while... your thoughts? | 02:37 |
| mithro | nash: I like it, but the base git still need a bit of work | 02:37 |
| nash | You are using1.5 I assume? | 02:38 |
| jotham | can you think of a nicer way to do that? http://rafb.net/p/vxGwue42.html | 02:40 |
| tpb | Title: Nopaste - No description (at rafb.net) | 02:40 |
| jotham | basically i want a list with an update method that can prune members of itself out if they fail the update | 02:40 |
| *** llnz has joined #tp | 02:44 | |
| xdotx | hey llnz | 02:48 |
| llnz | hi xdotx | 02:48 |
| xdotx | brb | 02:50 |
| *** xdotx has quit IRC | 02:50 | |
| mithro | jotham: okay | 02:54 |
| mithro | jotham: there are two ways to do what you want | 02:54 |
| *** xdotx has joined #tp | 02:55 | |
| jotham | there are lots of ways | 02:55 |
| *** xdotx has quit IRC | 02:55 | |
| mithro | jotham: try line 3 being, "for i, o in enumerate(self[:]):" | 02:55 |
| jotham | i just want a nicer way, since i can't use list comprehension in the way i'm doing it | 02:55 |
| jotham | that i know | 02:55 |
| mithro | and you probably want "remove", not pop | 02:55 |
| jotham | er | 02:56 |
| jotham | pop removes at an index | 02:56 |
| jotham | which is the point of enumerate | 02:56 |
| jotham | my code works fine | 02:56 |
| jotham | i just would like to do it with list comprehension | 02:56 |
| mithro | list comprehension is about generating a new list? | 02:57 |
| jotham | it's actually faster for this kind of task, which is filtering a list | 02:57 |
| jotham | but unfortunatly the list in question is 'self' | 02:57 |
| *** xdotx has joined #tp | 02:57 | |
| jotham | so you can't self = [...] | 02:57 |
| jotham | but i was curious if there was a hax way to do that | 02:57 |
| mithro | jotham: try "self[:] = [....]" | 02:58 |
| jotham | hum that's a point | 02:58 |
| jotham | wonder if it's slower | 02:58 |
| mithro | >>> a = [1, 2, 3] | 02:58 |
| mithro | >>> a[:] = [4,5,6] | 02:58 |
| mithro | >>> a | 02:58 |
| mithro | [4, 5, 6] | 02:58 |
| mithro | seems to work, but I don't know about speed | 02:59 |
| mithro | what are you actually trying to solve? | 02:59 |
| *** greywhind has quit IRC | 02:59 | |
| jotham | yeah that works | 03:00 |
| jotham | not solving anything...i program for amusement as much as anything | 03:00 |
| jotham | both work http://rafb.net/p/JI9r0J70.html | 03:01 |
| tpb | Title: Nopaste - No description (at rafb.net) | 03:01 |
| jotham | i should profile it | 03:01 |
| llnz | bbl | 03:07 |
| nash | *sigh* Massive update to system before I can build tpserver-cpp... | 03:08 |
| jotham | i had to move a woody box to etch the other day | 03:08 |
| jotham | my main web server | 03:08 |
| jotham | it wasn't fun | 03:08 |
| jotham | apt had 999 fucked up dependancies | 03:09 |
| jotham | but it's all good now | 03:09 |
| nash | It can be a PITA at the time | 03:11 |
| nash | Recently there seems to have been a lot of massive changes in unstable | 03:11 |
| nash | After release crazy time I guess | 03:11 |
| mithro | nash: why do you need to massively update? | 03:17 |
| CIA-23 | mithro schemepy * rf73cd0e82e70 /tests/ (10 files): Added support for testing against different modules. | 03:17 |
| mithro | yay for working on things which aren't really needed but are fun an interesting | 03:18 |
| nash | Basically lots of things need new dependancies... so you get one package that depends on a particular version of libc or some other fairly core lib... and boom - suddenly you have 100 packages to upgrade | 03:18 |
| nash | mithro: I should note I'm on unstable... these things are expected to happen | 03:19 |
| mithro | nash: I was more wondering what you needed to upgrade *for* tpserver-cpp ? | 03:21 |
| nash | Ahh... no libtls for tpproto ;-) | 03:21 |
| nash | And i only have git 1.4 on my laptop whihc is irritating | 03:22 |
| mithro | xdotx: where the tpclient-pytext additions useful at all to you? | 03:24 |
| xdotx | mithro: for orders? | 03:24 |
| mithro | xdotx: yeah | 03:24 |
| xdotx | mithro: i haven't had to use them yet | 03:25 |
| mithro | xdotx: no new orders being added? | 03:25 |
| xdotx | mithro: i'm making lots of new orders, but they're working with pywx for the most part | 03:25 |
| mithro | xdotx: oh, okay :P | 03:26 |
| mithro | nash: btw, did you get my email about the SoC coming to an end? | 03:28 |
| nash | Yeah | 03:29 |
| nash | Week to go basically ... need to get ready in the next day or two :-( | 03:30 |
| mithro | nash: currently working with niphree to clean-up and finish her stuff with the metaserver | 03:31 |
| mithro | going to be a busy week for her | 03:31 |
| nash | All the students I think | 03:31 |
| nash | mithro: So what state is the metaserver in? | 03:32 |
| mithro | nash: well, we will get the following | 03:32 |
| mithro | 1. Stats | 03:32 |
| mithro | 2. Auto-IP/Backconnect support | 03:33 |
| nash | Can we browse from clients? | 03:33 |
| mithro | 3. Start of a matchmaking service | 03:33 |
| mithro | nash: you can currently browse from tpclient-pywx-dev | 03:33 |
| nash | Is the browse protocol documented and implemented? | 03:34 |
| xdotx | t.t | 03:34 |
| xdotx | why don't i get linker errors :'( | 03:34 |
| mithro | 4. Fixing up support for tp04 vs tp03 meta-protocol frames | 03:34 |
| mithro | nash: there is an "unofficial protocol" which will become part of tp04 | 03:35 |
| nash | excellent - it's something I want to implement in galaxie very soon ;-) | 03:35 |
| mithro | see the "Server Location (Meta) Protocol" section of http://www.thousandparsec.net/tp/dev/documents/protocol4.php | 03:36 |
| tpb | <http://ln-s.net/JqO> (at www.thousandparsec.net) | 03:36 |
| nash | So it's implemented in metaserver? | 03:37 |
| mithro | Not the TCP request, but the HTTP requests are | 03:38 |
| mithro | and have been for quite a while | 03:38 |
| mithro | To get the details about which servers exist the client should send a HTTP Get request to the metaserver. | 03:38 |
| mithro | An example of this is "http://metaserver.thousandparsec.net/?action=get". | 03:38 |
| tpb | Title: Thousand Parsec : Metaserver Server Listing (at metaserver.thousandparsec.net) | 03:39 |
| mithro | you get back a HTTP Header, with TP frames in the body | 03:39 |
| nash | Yeah... I was hoping for a TCP version being implemented...\ | 03:39 |
| nash | hmm... | 03:39 |
| mithro | hrm, the doco isn't really clear about that | 03:39 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * reb1933fb04ea /modules/games/rfts/ (fleet.cpp fleet.h): Adding fleet properties | 03:40 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * r0a0302c18103 /modules/games/rfts/ (planet.cpp productioninfo.cpp productionorder.cpp): tweaking planet stats | 03:40 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * rb264b42d4188 /modules/games/rfts/move.cpp: debugging move | 03:40 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * r74c199f58753 /modules/games/rfts/fleet.cpp: just laying out fleet combat todo | 03:40 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * rb0e1bdc2ac37 /modules/games/rfts/ (6 files): adding split fleet order | 03:40 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * rcc1f1021eda0 /modules/games/rfts/ (6 files): adding rename fleet order | 03:40 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * rc879503dbfe5 /modules/games/rfts/rfts.cpp: -really- adding rename fleet order | 03:40 |
| *** xdotx is now known as xdotx_brb | 03:40 | |
| nash | Nice commit | 03:40 |
| xdotx_brb | just trying to get other stuff outta the way before i start on combat | 03:41 |
| mithro | xdotx_brb: so what can we do? | 03:41 |
| mithro | these RFTS commits makes me feel like working on TIMTrader | 03:42 |
| xdotx_brb | mithro: make fleets, move them (won't see them show up in new locations), rename and split fleets, do production orders (increase planet stats / population) | 03:43 |
| xdotx_brb | i'm going to rework the population formula some, i think it's bugged right now anyways | 03:43 |
| nash | mithro: please do | 03:44 |
| mithro | nash: actually, I think the first job is to make sure we can play a complete game of Minisec from start to end.... | 03:45 |
| mithro | nash: you'll need a HTTP support to download media (include battlexml data) | 03:45 |
| nash | Okay - it's fairly easy to do a simple file download | 03:46 |
| nash | Anyway - I need to bail | 03:47 |
| mithro | nash: and supporting HTTP tunnelling would be good | 03:47 |
| mithro | specially if you are going to make it work on embedded devices | 03:47 |
| nash | mithro: And of course there is always actually implementing mtsec someday... ;-) | 03:47 |
| nash | mithro: Yep | 03:48 |
| nash | Anyway - I need to bail | 03:48 |
| nash | Talk to you later... | 03:48 |
| *** nash has quit IRC | 03:51 | |
| *** xdotx_brb is now known as xdotx | 03:59 | |
| *** greywhind has joined #tp | 04:01 | |
| mithro | xdotx: so why doesn't a fleet show up at the new location? | 04:14 |
| xdotx | mithro: that's a very good question | 04:14 |
| xdotx | i tried everything i could think of to fix that today. no luck so far | 04:15 |
| mithro | xdotx: is the position getting updated in tpclient-pytext? | 04:16 |
| mithro | IE Do you know if it's a client or server issue? | 04:16 |
| xdotx | it -seems- like it's a client issue, because i've stepped through the server code and checked values. | 04:17 |
| mithro | xdotx: want some help debuging? | 04:18 |
| xdotx | mithro: i tried checking with pytext and it updates the position, but the parent (star sys) doesn't show the fleet as a child | 04:18 |
| mithro | xdotx: when you move outside the starsystem, it should get parented to the galaxy | 04:19 |
| mithro | which happens in the reparent code | 04:19 |
| xdotx | mithro: ? i don't have galaxies | 04:20 |
| mithro | well, then it should get parented to the universe | 04:21 |
| mithro | or what ever object contains the star systems | 04:21 |
| xdotx | hmm | 04:21 |
| mithro | so if you see what happens in minisec | 04:21 |
| xdotx | the fleet doesn't show up as a child of anything after i reset the parent on it. i've tried removing and not removing it from parent first | 04:22 |
| mithro | when a fleet moves out of a starsystem, it is re-parented to the next biggest object | 04:22 |
| mithro | arg! I wish people would use SPF | 04:23 |
| xdotx | mithro: would it be a problem if the fleet doesn't use velocity, or update position while it's in transit? | 04:24 |
| mithro | xdotx: well, it would make sense to be doing tha | 04:24 |
| mithro | see // recontainerise if necessary in doOrder of Move.py | 04:25 |
| mithro | s/Move.py/move.cpp | 04:25 |
| mithro | line 113 | 04:25 |
| mithro | ugg, | 04:27 |
| * mithro really doesn't line tpserver-cpp's code :P | 04:27 | |
| * mithro pokes llnz | 04:29 | |
| xdotx | heh | 04:29 |
| CIA-23 | mithro tpserver-py * rdaaa3cc3ab7e /tp/server/discover.py: Updates for the rearrangement of libtpproto-py. | 04:29 |
| CIA-23 | mithro tpserver-py * r03e77e476a90 / (tests/Ruleset.py tp/server/__init__.py): | 04:29 |
| CIA-23 | Added some tests to make sure a ruleset kindof works. | 04:29 |
| CIA-23 | Needs py.test installed, then run | 04:29 |
| CIA-23 | rm tp.db; TEST_RULESET='timtrader' py.test ./tests/Ruleset.py | less | 04:29 |
| xdotx | to be fair move isn't part of tpserver-cpp | 04:29 |
| mithro | xdotx: just cloning your code to look at it | 04:30 |
| * xdotx nods | 04:30 | |
| mithro | xdotx: you don't seem to be changing the parent at all? | 04:31 |
| mithro | oh wait, I'm blind :P | 04:31 |
| xdotx | line 22 | 04:31 |
| xdotx | 122* :P | 04:31 |
| xdotx | oh man, i wish that was the problem | 04:32 |
| mithro | xdotx: umm, do you have to call "donewithObject" on the Fleet? | 04:32 |
| xdotx | it's called after each object does it's orders | 04:33 |
| mithro | ahh okay | 04:33 |
| xdotx | i tried adding in an extra call to it, to make sure it was done though. didn't fix it | 04:33 |
| mithro | xdotx: so in RFTS, fleets are totally "off the map" when moving between systems? | 04:34 |
| * xdotx nods | 04:34 | |
| xdotx | they're in hyperspace! (or something like that) | 04:34 |
| xdotx | can't give orders or see them | 04:35 |
| mithro | have you tried | 04:35 |
| mithro | ob->addToParent(0); | 04:35 |
| mithro | ? | 04:35 |
| xdotx | hmm. no, worth a try | 04:35 |
| mithro | that seems to be what minisec is doing | 04:35 |
| mithro | setParent isn't going to update the parent object it seems | 04:36 |
| xdotx | ah | 04:36 |
| xdotx | yeah, yeah | 04:36 |
| mithro | minisec always seems to do a | 04:36 |
| mithro | ob->removeFromParent(); | 04:36 |
| mithro | ob->addToParent(0); | 04:36 |
| mithro | s/0/<some id>/ | 04:36 |
| xdotx | wait.. why doesn't setParent do an addToParent?? | 04:36 |
| mithro | xdotx: don't ask me :P | 04:36 |
| xdotx | heh | 04:37 |
| * mithro pokes llnz again | 04:37 | |
| xdotx | i think he's eating | 04:37 |
| mithro | I think maybe setParent is meant to be called by addToParent | 04:37 |
| jotham | mithro | 04:38 |
| jotham | does damage always happen in the same round | 04:38 |
| jotham | or could it be a few rounds later | 04:38 |
| xdotx | omg that worked | 04:38 |
| mithro | xdotx: you probably want to do something a little bit more advance in the future so that you personally can see fleets in hyperspace (but can't change orders) | 04:38 |
| mithro | otherwise it would be really hard to keep track of your assets :P | 04:39 |
| xdotx | mithro: i was planning on that (fleets have velocity i can set), but i wanted to get this WORKING first | 04:39 |
| xdotx | i think the move order, in all of it's like 10 lines of glory, has been the most work :P | 04:39 |
| mithro | the RFTS code looks pretty good :P | 04:40 |
| xdotx | thanks :) | 04:41 |
| mithro | I could probably port it to tpserver-py in a couple of hours ;) | 04:42 |
| mithro | so much backscatter spam :/ | 04:42 |
| xdotx | where? | 04:45 |
| mithro | i'm getting it on my server | 04:46 |
| mithro | about 800 in the last hour | 04:46 |
| mithro | xdotx: so what else do you need help solving? :P | 04:49 |
| xdotx | mithro: i've got a couple other things. lemme finish up on planet order updates and i'll ask :) | 04:51 |
| llnz | back | 04:57 |
| mithro | hey llnz | 04:57 |
| mithro | I think minisec module needs a bit of a cleanup :P | 04:57 |
| jotham | mithro? | 04:59 |
| mithro | jotham: opps sorry | 04:59 |
| mithro | I'm not sure I understand your question? | 05:00 |
| jotham | <round number="2"> | 05:00 |
| jotham | <fire> | 05:00 |
| jotham | <source ref="frigate-59-3" /> | 05:00 |
| jotham | <destination ref="battleship-54-1" /> | 05:00 |
| jotham | </fire> | 05:00 |
| jotham | <damage> | 05:00 |
| jotham | <reference ref="battleship-54-1" /> | 05:00 |
| jotham | <amount>2</amount> | 05:00 |
| jotham | </damage> | 05:00 |
| jotham | damage to 54-1 | 05:01 |
| jotham | will it always happen in round 2 in this case | 05:01 |
| jotham | or could it be round 3, 4...etc | 05:01 |
| * llnz reads the backlog | 05:01 | |
| mithro | jotham: well, the way I was thinking is that damage could occur any time | 05:03 |
| jotham | yeah | 05:03 |
| mithro | IE if you had some type of special "acid" laser | 05:03 |
| jotham | *nod* | 05:03 |
| jotham | it'd just be dumb if you saw the damage before the weapon fired | 05:04 |
| mithro | but damage should prettymuch always be applied after fire events | 05:04 |
| jotham | graphically in the above case they'd happen at the same time | 05:04 |
| jotham | which would look dumb | 05:04 |
| jotham | so i was just curious | 05:04 |
| mithro | jotham: well I would prefer to be able to have damage events in the same round as fire events | 05:05 |
| mithro | and the viewer always makes sure the fire events are displayed first | 05:05 |
| jotham | yeah that's what i'll do | 05:05 |
| mithro | but if that is going to be too hard | 05:05 |
| jotham | i was just curious about the nature of damage | 05:05 |
| mithro | jotham: well it's pretty "generic" | 05:06 |
| mithro | jotham: btw if you think "oohhh, it would be really cool if it do X" then feel free to suggest it | 05:06 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * r967b11c673ba /modules/games/rfts/ (fleet.cpp move.cpp rftsturn.cpp): move order works :) | 05:20 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * r9f9a71e5a786 /modules/games/rfts/ (planet.cpp planet.h rfts.cpp): Production limited to every 3rd turn, build fleets on even and 3rd | 05:20 |
| mithro | hrm, no niphree :/ | 05:21 |
| mithro | xdotx: I hope you have one hell of a welcome message :P | 05:39 |
| xdotx | mithro: lol ? | 05:41 |
| mithro | well, the "can do x in turn x" | 05:42 |
| xdotx | oh, heh | 05:43 |
| mithro | xdotx: maybe you should post a message each turn which says what you can do in that turn? | 05:45 |
| xdotx | mithro: well it manually limits the orders you can do that turn | 05:46 |
| mithro | xdotx: yes, but people will be going "why can't I add a production order!?" | 05:46 |
| xdotx | heh | 05:46 |
| xdotx | mithro: and i'll be like "hahahah! all your production order are belong to me!" | 05:47 |
| xdotx | ~~ | 05:47 |
| xdotx | mithro: i'd like to think people would read at least an overview of the rules first. but honestly most probably won't | 05:49 |
| mithro | xdotx: too true | 06:01 |
| CIA-23 | llnz tpserver-cpp * r9cc1789a1e8b /tpserver/playeragent.cpp: | 06:01 |
| CIA-23 | Set orderqueueid of Order before doing inputFrame on the order. | 06:01 |
| CIA-23 | Suggested by xdotx. Makes sense. | 06:01 |
| mithro | but even then, when you connect to a game you might end up in the middle of a certain turn | 06:01 |
| xdotx | llnz: good news! | 06:05 |
| *** xdotx is now known as xdotx_brb | 06:05 | |
| mithro | llnz: btw demo1 is looking very sparse | 06:11 |
| mithro | DystopicFro: https://sourceforge.net/tracker/?func=detail&atid=723099&aid=1773673&group_id=132078 | 06:13 |
| tpb | Bug #1773673: Error inserting a string | 06:13 |
| jotham | is there a kind of hash/dict that isn't expensive to iterate over? | 06:26 |
| mithro | dict isn't that expensive to iterate over | 06:27 |
| jotham | ok | 06:27 |
| mithro | make sure you are using the iter though | 06:27 |
| mithro | IE {}.iteritems() | 06:28 |
| mithro | rather then {}.items() | 06:28 |
| jotham | *nod* | 06:28 |
| *** xdotx_brb is now known as xdotx | 06:29 | |
| mithro | infact iteration on almost all python structures is pretty fast | 06:30 |
| jotham | there are not enough hours in the day | 06:32 |
| mithro | jotham: I know :/ | 06:35 |
| CIA-23 | mithro tpserver-py * r2f9646677dbd /tp/server/ (__init__.py bases/Game.py bases/Ruleset.py): Started conversion to using an event queue rather then Unix signals. | 06:55 |
| mithro | hrmm... niphree is now 2 hours late :/ | 06:56 |
| CIA-23 | mithro tpserver-py * r029bf7109409 /tp/server/bases/ (Game.py Ruleset.py): Make the Event class easier to work with. | 07:05 |
| mithro | xdotx: so what is the good news? | 07:08 |
| xdotx | mithro: oh, just that update from llnz - having orderqueue in the inputframe | 07:08 |
| mithro | so did you have any other problems | 07:09 |
| xdotx | hmm. a question and i problem i think | 07:10 |
| xdotx | mithro, llnz: in RFTS you can see all star systems and planets at all times, but you only know the state of each planet as it was last seen by a fleet. the framework doesn't have a way to emulate this, does it? | 07:13 |
| llnz | xdotx: i'm working on it | 07:14 |
| llnz | slowly (unfortunately) | 07:14 |
| xdotx | i was thinking i could just have all star systems be visible but only show planets if there's a fleet at that system | 07:15 |
| llnz | xdotx: you could do that | 07:16 |
| mithro | xdotx: that would be my sugestion | 07:16 |
| * xdotx nods | 07:16 | |
| xdotx | i'm probably going to implement that soon / next | 07:17 |
| mithro | xdotx: so we can build thing yet? | 07:17 |
| xdotx | mithro: you should be able to build scouts and marks | 07:18 |
| xdotx | building does have a sort of strange problem though. | 07:22 |
| xdotx | llnz: i was wondering if you could take a look at it... | 07:23 |
| llnz | xdotx: sure | 07:23 |
| xdotx | the build order sets a max value for how many of each ship you can make depending on your current resource points, but the max values are ignored (?) when you first go to add a ship. | 07:24 |
| xdotx | if you add one, then remove it, the next one you add is correctly limited. BUT, then it gets even weirder - all other ships are limited to whatever the limit was for the ship you add next | 07:24 |
| llnz | xdotx: in tpclient-pywx? | 07:24 |
| * xdotx nods | 07:25 | |
| llnz | it's a bug in tpclient-pywx that it doesn't correctly follow the limits of the list order parameter | 07:25 |
| xdotx | both parts? | 07:26 |
| llnz | most probably | 07:26 |
| xdotx | well, that's good news for me then ;) | 07:26 |
| llnz | mithro: does that sound correct? | 07:27 |
| mithro | xdotx: check using text | 07:27 |
| mithro | but it sounds pretty probable | 07:29 |
| jotham | awesome i got my events working, my particle emitter kinda working, and the spires for lasers rocking | 07:31 |
| jotham | time for a bath | 07:31 |
| mithro | jotham: cool! | 07:33 |
| mithro | xdotx: how do I test your bug? | 07:40 |
| xdotx | mithro: with rfts you can do a build fleet order and select any stat. the limit for all amounts gets ignored for the first item you add. but after you clear an order, when you go to add another the limit isn't ignored, but the same limit is applied to all stats | 07:43 |
| xdotx | mithro: if it's not just rfts, then anything that uses the same list should exhibit the same bug | 07:44 |
| llnz | including minisec, build order | 07:44 |
| llnz | and possibly split fleet | 07:45 |
| * llnz wanders off | 07:52 | |
| llnz | later all | 07:52 |
| *** llnz has quit IRC | 07:52 | |
| mithro | hrm, maximum should never be set | 07:52 |
| CIA-23 | mithro tpclient-pywx * r5705a73adb59 /utils.py: Seems these where accidently removed. | 08:17 |
| CIA-23 | mithro tpclient-pywx * r195191c43227 /windows/winOrder.py: Fix a problem with the latest wxPythons. | 08:17 |
| mithro | xdotx: give that a try? | 08:18 |
| xdotx | mithro: awesome, works | 08:22 |
| mithro | cool | 08:22 |
| mithro | seems the latest wxPython may have broken that and nobody noticed | 08:22 |
| mithro | xdotx: your on Linux right? | 08:25 |
| mithro | do you recon you could take a screenshot of the client? | 08:26 |
| * xdotx nods | 08:26 | |
| * mithro recently fixed the DPI on his Laptop, which means all the fonts in pywx are too tiny now | 08:26 | |
| mithro | and was wondering how you find it | 08:26 |
| mithro | still no niphree :/ | 08:26 |
| *** guitsaru has joined #tp | 08:27 | |
| mithro | hello guitsaru | 08:29 |
| guitsaru | hey | 08:29 |
| xdotx | mithro: http://lusoc.mine.nu/tpclient-pywx.png | 08:30 |
| mithro | whats with all the transparenecy? :P | 08:31 |
| xdotx | beryl ;) | 08:31 |
| mithro | makes it hard to see the edges | 08:32 |
| xdotx | got it for fun a while ago, but found it really useful | 08:32 |
| mithro | the font size looks okay | 08:32 |
| xdotx | yeah the font looks fine. but as for edges, i don't have window borders on anything but the design window | 08:33 |
| mithro | xdotx: I mean the "main" window | 08:33 |
| xdotx | ah | 08:33 |
| mithro | xdotx: what is your DPI set in Appearence->Fonts->Details ? | 08:36 |
| mithro | your screen res is 1280x1024 | 08:38 |
| xdotx | er | 08:40 |
| xdotx | mithro: Appearance...? | 08:43 |
| mithro | System -> Preferences -> Appearance | 08:43 |
| xdotx | don't have that one, but i did find my font DPI | 08:43 |
| xdotx | 96 | 08:43 |
| mithro | okay | 08:44 |
| xdotx | mithro: you on KDE? | 08:45 |
| mithro | no | 08:45 |
| mithro | Gnome | 08:45 |
| xdotx | hmm. i don't have an "appearance" in my preferences. but there's "Fonts", fyi | 08:46 |
| mithro | hrm.... | 08:46 |
| mithro | what version of ubuntu? edgy? | 08:46 |
| xdotx | feisty | 08:46 |
| mithro | ahh, I upgraded to gusty - maybe it's new | 08:47 |
| xdotx | is it using gnome 2.14? | 08:49 |
| xdotx | er, 2.18.1 | 08:49 |
| mithro | 2.19.6 is appears | 08:50 |
| * xdotx nods | 08:50 | |
| xdotx | that seems like the difference then | 08:50 |
| mithro | probably | 08:52 |
| xdotx | ack, sun's comin' up again. better go to bed | 08:57 |
| mithro | xdotx: when do you go back to school? | 08:57 |
| xdotx | mm early sept | 08:57 |
| mithro | xdotx: sleep is for the weak! :P | 08:57 |
| xdotx | agreed! | 08:57 |
| mithro | so you going to continue working on RFTS till then? | 08:58 |
| xdotx | ...maybe i will stay up ;P | 08:58 |
| xdotx | i plan on continuing so i can implement tp04 for RFTS and i'd like to help with tpserver-cpp as well | 08:58 |
| * mithro will be around again tommorrow | 08:58 | |
| xdotx | but i know i'll be very busy during school working on my own project(s) | 08:59 |
| mithro | xdotx: you just need to figure out how to make TP part of your school work :P | 08:59 |
| xdotx | heheh. i might be able to do some projects like that, but i doubt it | 09:00 |
| xdotx | oh, but in the time before school starts back up i'll very likely put in some more work. I plan on having RFTS done next week, but it won't be polished, that's for certain. | 09:04 |
| xdotx | i'm going to be taking a trip back home for a week in about 10 days, but i plan on having my laptop (things are pretty boring at home ;P) | 09:06 |
| *** DystopicFro has quit IRC | 09:13 | |
| jotham | damn that was a sweet path | 09:16 |
| jotham | *bath | 09:16 |
| xdotx | mint favoured bubbles? | 09:17 |
| jotham | hah, no flavors/scents freak me out | 09:17 |
| jotham | http://the.fieldsofnoise.org/Archive/temp/spaceships-dist.tar.bz2 | 09:20 |
| tpb | <http://ln-s.net/pBy> (at the.fieldsofnoise.org) | 09:21 |
| CIA-23 | mithro libtpproto-py * r424ce9df0621 /tp/netlib/xstruct.py: Sometimes we don't need an argument. | 09:21 |
| CIA-23 | mithro libtpproto-py * rdc24b21158fd /tp/netlib/server.py: Poll can be given a timeout. | 09:21 |
| mithro | jotham: what is that? | 09:21 |
| jotham | just the same as the other day, but with some lasers, timers, events, and a basic emitter | 09:21 |
| mithro | woot! | 09:22 |
| jotham | will get it to load in the proper battle xmls soon enough | 09:22 |
| mithro | should it stop emitting? | 09:22 |
| jotham | it has a series of timers triggering the emitter | 09:23 |
| CIA-23 | mithro tpserver-py * r78731d00c12c /tp/server/ (__init__.py bases/Game.py bases/Ruleset.py): Reworked events to able to reference a game, but not game specific. | 09:24 |
| mithro | jotham: and they stop after a while? | 09:24 |
| jotham | what do? | 09:24 |
| jotham | well it wouldn't be like that in the real thing, the bullets would fly toward a target for starters | 09:24 |
| jotham | and it wouldn't be random emission | 09:24 |
| jotham | that was just me testing out the stuff to make sure it's working | 09:24 |
| mithro | after running for about 1 minute the emitters stop emitting | 09:25 |
| jotham | that's becasue it's a list of timers... | 09:25 |
| jotham | theres only like 12 of them | 09:25 |
| mithro | ahh okay | 09:25 |
| mithro | we need some sound effects :P | 09:25 |
| jotham | bah i've been reading about that | 09:26 |
| jotham | it's gonna be shitty | 09:26 |
| xdotx | lol. i found a hack in tpserver-cpp | 09:26 |
| jotham | (this is just me implimenting all the bits and pieces of the graphics engine btw...) | 09:26 |
| mithro | watching this in silence is a bit errie | 09:26 |
| mithro | xdotx: oh? | 09:26 |
| xdotx | clearly marked "//HACK" | 09:26 |
| jotham | now = pygame.time.get_ticks() | 09:26 |
| jotham | for t in [1500, 2000, 2500, 3000, 3500, 3700, 6000, 6700, 9000, 4300]: | 09:26 |
| jotham | timers.append(Timer(t+now, ship0.fire)) | 09:26 |
| jotham | that's what you are watching in effect | 09:26 |
| mithro | jotham: so I assume this would work well for missiles too? | 09:27 |
| jotham | sure, right now the bullets are just going on a constant vx,vy | 09:27 |
| jotham | but you'd want them guided | 09:27 |
| xdotx | he forces all objects visible after adding the player. which is precisely why i can't seem to hide things in my onPlayerAdd | 09:27 |
| jotham | with smoke/particles and crap | 09:27 |
| jotham | which is fine | 09:28 |
| jotham | like i said, i've been rewriting all the graphics side of battleviewer again from scratch | 09:28 |
| jotham | while i've programmed plenty, this is my first real attempt at a pygame application | 09:28 |
| jotham | ..and it's very manual | 09:28 |
| *** DystopicFro has joined #tp | 09:31 | |
| DystopicFro | mithro: ping? | 09:33 |
| mithro | DystopicFro: hi! | 09:33 |
| DystopicFro | ahoyhoy | 09:33 |
| * DystopicFro needs to be more consistent in naming methods | 09:33 | |
| mithro | DystopicFro: you get the bug report :P | 09:33 |
| DystopicFro | fixed the text insertion bug | 09:33 |
| mithro | not pushed? | 09:34 |
| DystopicFro | just changed the code, pushing now | 09:34 |
| CIA-23 | frodough tpruledev * r425b27bd1f3b /src/tpcl/Representation.py: Fixed Text insertion | 09:35 |
| DystopicFro | mithro: anyway, I take it you've looked at the expression editor lately...what do you think of the quick insert menu? | 09:35 |
| mithro | I like the quick insert menu | 09:35 |
| mithro | I think you shouldn't have to hold control however | 09:35 |
| mithro | I think left-click == pop-up, right-click == copy menu? | 09:36 |
| mithro | ohhh, Undo and Redo! | 09:37 |
| DystopicFro | *nods* I was messing with the control-click, to see how that felt | 09:37 |
| DystopicFro | mithro: yea, that's definitely on the to-do list | 09:37 |
| mithro | Undo/Redo doesn't seem to work | 09:37 |
| mithro | in that now I can't insert | 09:38 |
| DystopicFro | mithro: hrm...the right click menu is a part of the styledtextctrl | 09:39 |
| mithro | DystopicFro: is there any point with a pop-up on the *..*, why not just add another item? | 09:39 |
| DystopicFro | Well | 09:39 |
| DystopicFro | Take the cond expression | 09:39 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * rc2103508b6b9 /modules/games/rfts/ (fleet.cpp rfts.cpp): set all planets invisible except if a fleet is present | 09:39 |
| DystopicFro | You can either add a new case to test for | 09:39 |
| DystopicFro | or you can add the else clause | 09:39 |
| DystopicFro | or you can just close it off | 09:39 |
| * mithro tests out cond | 09:40 | |
| * DystopicFro prays that works | 09:40 | |
| xdotx | ok. bed time. 'night all / 'morning / 'evening | 09:40 |
| mithro | xdotx: gnight | 09:40 |
| mithro | DystopicFro: found another bug | 09:40 |
| mithro | Traceback (most recent call last): | 09:40 |
| mithro | File "/home/tim/oss/tp/tpruledev/src/gui/TpclEditorDialog.py", line 219, in f | 09:40 |
| mithro | tpcl_editor.root_expression.Expand(offset, option) | 09:40 |
| mithro | File "/home/tim/oss/tp/tpruledev/src/tpcl/Representation.py", line 520, in Expand | 09:40 |
| mithro | return self.template.GetElementValue(index).Expand(offset, option) | 09:40 |
| mithro | File "/home/tim/oss/tp/tpruledev/src/tpcl/Representation.py", line 520, in Expand | 09:40 |
| mithro | return self.template.GetElementValue(index).Expand(offset, option) | 09:40 |
| mithro | File "/home/tim/oss/tp/tpruledev/src/tpcl/Representation.py", line 534, in Expand | 09:40 |
| mithro | self.template.ExpandExpansionPoint(index, expr, cont_exp) | 09:40 |
| mithro | File "/home/tim/oss/tp/tpruledev/src/tpcl/Representation.py", line 216, in ExpandExpansionPoint | 09:41 |
| mithro | del self.template[index] | 09:41 |
| mithro | AttributeError: 'TpclTemplate' object has no attribute 'template' | 09:41 |
| mithro | DystopicFro: there isn't really any point of having the rest of the menu on an expansion point? | 09:41 |
| mithro | DystopicFro: damn users, huh? :P | 09:42 |
| DystopicFro | mithro: probably not, just haven't quite gotten around to finalizing the UI yet | 09:43 |
| DystopicFro | need all the features first >.< | 09:43 |
| DystopicFro | mithro: I love the feedback, helps with motivation and all that o.O | 09:43 |
| mithro | DystopicFro: well, on something like the (+ *..*) there is only really one option, add a new point | 09:44 |
| mithro | and you probably always want the *..* there so that if you change your mind later you can keep adding points | 09:44 |
| DystopicFro | bah one line typos | 09:44 |
| mithro | DystopicFro: btw, when do you go back to Uni? | 09:45 |
| CIA-23 | frodough tpruledev * r4c4905e8e2f5 /src/tpcl/Representation.py: Fixed closure on variable length expressions | 09:45 |
| DystopicFro | mithro: first class on monda | 09:45 |
| DystopicFro | s/monda/monday/ | 09:45 |
| DystopicFro | this coming, Aug 20 | 09:46 |
| * DystopicFro has the distinct feeling that mithro favors quick and simple | 09:46 | |
| * mithro favours KISS :P | 09:47 | |
| DystopicFro | mithro: my current conception of using the expression editor with the RDE is to get the string for the TPCL code in the same way that the editor does | 09:47 |
| DystopicFro | and if I do that then leaving in the *...* will b0rk the evaluation of the code | 09:48 |
| mithro | DystopicFro: well, just use a property which does a "return self.string.replace(' *..*', '')" | 09:49 |
| mithro | call it something like "eval" string? | 09:50 |
| mithro | hrm... but then you can't re-add them when starting up the editor? | 09:50 |
| DystopicFro | well | 09:51 |
| mithro | when starting up the editor your parse scheme into your internal representation? | 09:51 |
| DystopicFro | I plan on storing all expressions generated by the expression editor in a format that can be reconstructed from the block store | 09:51 |
| mithro | okay | 09:52 |
| DystopicFro | a feature that I would like to add eventually is to parse existing code into the internal representation | 09:52 |
| DystopicFro | but that's not provided for at the moment | 09:52 |
| mithro | scheme is REALLY easy to parse as long as it doesn't have macros in it :P | 09:52 |
| DystopicFro | aye, not so worried about that, just haven't gotten around to it yet o.O | 09:53 |
| mithro | Btw you don't seem to have a "List Literal"? | 09:53 |
| DystopicFro | you can use a quoted expression for that? | 09:53 |
| mithro | yeah | 09:53 |
| mithro | but lists are fairly common | 09:53 |
| mithro | so are "alists" | 09:54 |
| mithro | a list would be "`(*EXP* *..*)" | 09:54 |
| DystopicFro | Aye, well, the list of functions is far from complete >.< I think I got up to the middle of string procedures before I called it quits | 09:54 |
| DystopicFro | Ah, I have no support for that yet >.< | 09:54 |
| mithro | an alist would be "`((*EXP* . *EXP*) *..*)" (where *..* adds (*EXP* . *EXP*) ) | 09:55 |
| mithro | alists == dictionaries | 09:55 |
| mithro | an alist would be "`((*KEY* . *VALUE*) *..*)" (where *..* adds (*KEY* . *VALUE*) ) | 09:56 |
| mithro | (s/dictionaries/very inefficient but portable dictionaries/) | 09:56 |
| DystopicFro | heh | 09:56 |
| mithro | sadly there is no portable "hash" specification | 09:57 |
| * mithro pretends to be old and grumpy | 09:57 | |
| DystopicFro | >.< | 09:57 |
| DystopicFro | mithro: anyway, what I have in mind for the quick insert menu is to allow the user to specify any and all categories of expressions that he wants | 09:58 |
| DystopicFro | and also to have a history of the last 10 or so expressions | 09:59 |
| mithro | DystopicFro: that sounds useful | 09:59 |
| DystopicFro | would that sate your need for having what you want to insert at your fingertips? | 09:59 |
| mithro | DystopicFro: yeah, I guess so | 09:59 |
| mithro | DystopicFro: but don't be surprised at a patch if I get using it a lot ;) | 10:00 |
| DystopicFro | lol | 10:00 |
| DystopicFro | mithro: well, like I said before, once all of the backing structures are in place (like the blockstore and such) it won't be too much trouble to change the interface up | 10:01 |
| DystopicFro | alright, off to a bit of coding for me | 10:02 |
| mithro | DystopicFro: okay | 10:13 |
| CIA-23 | frodough tpruledev * rba37adc38724 /src/gui/xrc/.gitignore: Ignoring wxg and pyc files in ./gui/xrc | 10:44 |
| CIA-23 | frodough tpruledev * r51442cb2eb67 /src/ (6 files in 4 dirs): Added Info dialog for TPCL blocks | 10:44 |
| *** DystopicFro has quit IRC | 10:57 | |
| CIA-23 | mithro tpserver-py * r28c582dd45d3 /tp/server/ (4 files in 2 dirs): Removed excess prints. | 11:02 |
| CIA-23 | mithro tpserver-py * r3f085a385719 / (tests/Ruleset.py tp/server/bases/Ruleset.py): | 11:02 |
| CIA-23 | Added an "update" method to rulesets. | 11:02 |
| CIA-23 | Used to update a currently running game with data from on disk. | 11:02 |
| CIA-23 | mithro tpserver-py * re108c41cc914 /tpserver-py-tool: | 11:02 |
| CIA-23 | Wrap the game creation in a transaction. | 11:02 |
| CIA-23 | If the initialise fails the game won't be created. | 11:02 |
| CIA-23 | mithro tpserver-py * r3f6229d17196 /tp/server/ (3 files in 3 dirs): Add support for GameAdded event. | 11:02 |
| CIA-23 | mithro tpserver-py * r8811dee6bf8f /tp/server/bases/SQL.py: Also pull the game ID back out on an insert. | 11:02 |
| CIA-23 | mithro tpserver-py * r0175384f7e91 /tp/server/bases/Game.py: | 11:03 |
| CIA-23 | Only print out that we are removing the lock when local. | 11:03 |
| CIA-23 | Also include the game id in the lock printout. | 11:03 |
| CIA-23 | mithro tpserver-py * r063e345df7f1 /tp/server/bases/Game.py: Make sure that the event object restores the database to the correct game. | 11:03 |
| mithro | arg, how did it become 2:00am | 12:24 |
| *** DystopicFro has joined #tp | 12:33 | |
| mithro | wb DystopicFro | 12:34 |
| DystopicFro | ahoy | 12:34 |
| mithro | there was something I wanted to tell you just after you disconnected | 12:34 |
| DystopicFro | oy? | 12:35 |
| mithro | but I have totally forgotten it now | 12:35 |
| DystopicFro | oh :( | 12:35 |
| * mithro tries to think what he was doing | 12:35 | |
| mithro | here are some other questions I thought up | 12:36 |
| mithro | - Have you figured out where to put the "help" stuff? | 12:36 |
| mithro | - It would be nice if the Preview window also did highlighting | 12:36 |
| mithro | - For some reason you can't maximise the editor frame | 12:37 |
| mithro | Do you think you will continue developing on the project when you start classes again? | 12:37 |
| DystopicFro | mithro: 1) The "Detailed Info" button works now, I'm still thinking about implementing a help browser | 12:38 |
| DystopicFro | 2) Haven't done that because I don't want to incur the overhead of another STC, but I guess it wouldn't be too bad | 12:38 |
| DystopicFro | 3) Pretty sure that's because it's a dialog | 12:39 |
| DystopicFro | 4) As I'm able to | 12:39 |
| mithro | DystopicFro: the Detailed Info button doesn't seem to do anything for me | 12:39 |
| mithro | ahh! I remeber now | 12:40 |
| mithro | http://dystopicfro.blogspot.com/2007/08/on-generalization-of-servers.html | 12:40 |
| tpb | <http://ln-s.net/pEl> (at dystopicfro.blogspot.com) | 12:40 |
| mithro | I commented there | 12:40 |
| DystopicFro | mithro: make sure you've selected a block in the tree control | 12:40 |
| DystopicFro | ah...hm...yes, I haven't gotten around to posting it to the mailing list yet >.< | 12:42 |
| DystopicFro | I'll write up my status report for this past week and then I'll send that to the mailing list | 12:42 |
| mithro | DystopicFro: yeah, I've selected a few different blocks | 12:45 |
| DystopicFro | hrm... | 12:46 |
| DystopicFro | very weird...it's working over here | 12:47 |
| mithro | I have tried Proc Def, Literals and Proc Calls | 12:48 |
| mithro | def OnInfo(self, event): | 12:49 |
| mithro | """\ | 12:49 |
| mithro | Opens a dialog without a parent for the moment | 12:49 |
| mithro | """ | 12:49 |
| mithro | event.Skip() | 12:49 |
| mithro | DystopicFro: you forget to push something? | 12:49 |
| DystopicFro | nar | 12:49 |
| DystopicFro | just pushed again to make sure | 12:49 |
| DystopicFro | def OnInfo(self, event): | 12:49 |
| DystopicFro | """\ | 12:49 |
| DystopicFro | Opens a dialog without a parent for the moment | 12:49 |
| DystopicFro | """ | 12:49 |
| DystopicFro | sel_id = self.block_tree.GetSelection() | 12:49 |
| DystopicFro | if sel_id.IsOk(): | 12:49 |
| DystopicFro | block = self.block_tree.GetPyData(sel_id) | 12:49 |
| DystopicFro | if block: | 12:49 |
| DystopicFro | info_dialog = BlockInfoDialog(self, block.name, block.display, block.description) | 12:49 |
| DystopicFro | info_dialog.ShowModal() | 12:49 |
| DystopicFro | event.Skip() | 12:49 |
| * mithro tries pulling again | 12:50 | |
| mithro | umm, your doco is wrong on TPCL requirements function | 12:51 |
| mithro | If the component is allowed to be added to a design then the function should return a pair with True and a string to be displayed (empty strings are acceptable), otherwise it should return a pair with false and a string which describes the reason for not being able to add the component. The function is given a design object which has appears as if the component was already added. Returns - Bool | 12:51 |
| mithro | The "Returns - Bool" conflicts the with defintion that it returns a pair | 12:52 |
| * DystopicFro nods | 12:53 | |
| DystopicFro | thanks for catching that - most everything to do with tpcl expressions right now is a mish-mash of placeholders and more permanent stuff | 12:53 |
| mithro | DystopicFro: yeah, I see that :P | 12:53 |
| DystopicFro | one thing that I need to do is complete the default store of TPCL Blocks and then verify all the data | 12:54 |
| mithro | DystopicFro: I'm happy to help with that sometime | 12:54 |
| DystopicFro | mithro: any help there would be appreciated - the info on the blocks is stored in ./tpcl/data/tpcl_base.xml | 12:56 |
| mithro | okay | 12:56 |
| mithro | probably won't get a look till the weekend | 12:56 |
| CIA-23 | frodough tpruledev * r2a1f84603a94 /src/tpcl/data/tpcl_base.xml: Brought doc text up to date | 12:59 |
| DystopicFro | well, when you do get a look at it things will be up to date in terms of doc on the XML structure then >.< | 12:59 |
| mithro | DystopicFro: we probably should sit down sometime and talk about how to "install" the program | 13:04 |
| *** xdotx_ has joined #tp | 13:04 | |
| DystopicFro | mithro: agreed - or you can point me in the direction of some docs in that regard I can do most of the legwork | 13:04 |
| DystopicFro | I can ping you with any questions that I have | 13:04 |
| DystopicFro | which reminds me | 13:05 |
| mithro | DystopicFro: the best example so far is the setup.py in tpclient-pywx-dev | 13:05 |
| mithro | python just doesn't have a good method for install applications rather then just modules | 13:05 |
| DystopicFro | mithro: is ElementTree distrubuted with Python 2.4? I have almost lost sanity trying to find it in the default install | 13:05 |
| *** xdotx has quit IRC | 13:05 | |
| mithro | DystopicFro: no, elementtree doesn't come with 2.4 | 13:05 |
| mithro | # Need to find an ElementTree implimentation! | 13:06 |
| mithro | ET = None | 13:06 |
| mithro | errors = [] | 13:06 |
| mithro | try: | 13:06 |
| mithro | import elementtree.ElementTree as ET | 13:06 |
| mithro | except ImportError, e: | 13:06 |
| mithro | errors.append(e) | 13:06 |
| mithro | try: | 13:06 |
| mithro | import cElementTree as ET | 13:06 |
| mithro | except ImportError: | 13:06 |
| mithro | errors.append(e) | 13:06 |
| mithro | try: | 13:06 |
| mithro | import lxml.etree as ET | 13:06 |
| mithro | except ImportError: | 13:06 |
| mithro | errors.append(e) | 13:06 |
| mithro | try: | 13:06 |
| mithro | import xml.etree.ElementTree as ET | 13:06 |
| mithro | except ImportError: | 13:06 |
| mithro | errors.append(e) | 13:06 |
| mithro | if ET is None: | 13:06 |
| mithro | raise ImportError(str(errors)) | 13:06 |
| mithro | that is what I use to import ElementTree | 13:06 |
| DystopicFro | kk, just checking...I thought you had said that it had been included since 1.5 | 13:07 |
| DystopicFro | so | 13:07 |
| mithro | DystopicFro: no, since 2.5 | 13:07 |
| DystopicFro | well | 13:07 |
| DystopicFro | now I feel a little bit less insane. | 13:07 |
| mithro | with Python 2.5 they made a pretty big effort to pull in all the really useful, stable modules | 13:08 |
| mithro | so Python 2.5 has ctypes, elementtree and a few other modules too | 13:08 |
| DystopicFro | alright, I'll have to check all of those different implementations, though, to see which ones I can use my writeout method with | 13:09 |
| mithro | DystopicFro: okay | 13:09 |
| mithro | DystopicFro: I believe they are all linked from the elementtree website | 13:10 |
| * DystopicFro nods | 13:11 | |
| mithro | cElementTree is in ubuntu | 13:11 |
| mithro | and so is lxml I believe | 13:12 |
| mithro | DystopicFro: so any questions before I go to bed? | 13:22 |
| *** Demitar has quit IRC | 13:29 | |
| DystopicFro | mithro: sorry about that, just trying to get cElementTree working - no joy | 13:31 |
| DystopicFro | don't have any questions at the moment >.< | 13:31 |
| DystopicFro | good sleeps | 13:31 |
| mithro | DystopicFro: okay, see you around | 13:31 |
| * mithro heads to bed | 13:33 | |
| mithro | gnight everyone | 13:34 |
| CIA-23 | frodough tpruledev * rd5cdd9a52fbd /src/ (5 files in 2 dirs): | 14:08 |
| CIA-23 | Switched to mithro's method of importing ElementTree | 14:08 |
| CIA-23 | This also required that I changed the writeout method. It works for | 14:08 |
| CIA-23 | ElementTree. It should work for lxml.etree as well. cElementTree not | 14:08 |
| CIA-23 | so much. | 14:08 |
| CIA-23 | frodough tpruledev * ra0e2bee3940b /src/elementtree/ (12 files): Deleted ElementTree package from ./src/elementtree | 14:08 |
| *** Demitar has joined #tp | 14:57 | |
| *** greywhind has joined #tp | 16:40 | |
| *** xdotx_ is now known as xdotx | 17:34 | |
| *** Demitar has joined #tp | 17:42 | |
| *** nash has joined #tp | 17:54 | |
| * nash waves | 17:57 | |
| xdotx | hey nash | 18:00 |
| nash | Heyo xdotx | 18:02 |
| * nash wonders if llnz is around | 18:05 | |
| nash | I have a pile of tpproto patches to submit... and I'd like them reviewed before I send them | 18:05 |
| xdotx | i call him first! :P i want this playview visibility hack fixed | 18:09 |
| nash | Fight! | 18:10 |
| xdotx | heheh | 18:11 |
| *** zipola has quit IRC | 18:13 | |
| nash | xdotx: Don't worry - mine are mostly formating, add some FIXMEs to things that look dodgy, and a sanity check or two | 18:13 |
| nash | Also a bail out on malformed messages in a few blaces | 18:13 |
| nash | s/blaces/places/ | 18:14 |
| xdotx | nash: i'm actually not sure what all is going to have to be changed/fixed for the visibility thing. it's not as easy as moving a couple lines around, like i'd hoped | 18:15 |
| nash | Ahh... I recall some of this... it's ugly | 18:15 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * re23ff9c0d8ea /modules/games/rfts/ (7 files): just a bit of reorganizing | 18:22 |
| CIA-23 | fr33.em4il tpserver-cpp-rfts * rfaf26c5fc599 /modules/games/rfts/ (6 files): | 18:22 |
| CIA-23 | Star system exploration / planet visibility reworked. Pending a fix (or | 18:22 |
| CIA-23 | another hack) for the playview visibility hack. | 18:22 |
| nash | You have the weirdest email address | 18:29 |
| xdotx | nash: it's free email :P. stems from an old joke on yahoo's email setup page | 18:47 |
| nash | xdotx: I know what it is... Although I don't know the joke? | 19:00 |
| xdotx | nash: just me and some friends messing around in cs class in highschool | 19:01 |
| nash | okay | 19:01 |
| CIA-23 | frodough tpruledev * rf5ed91ecab8e /TPCLEE_README: | 19:03 |
| CIA-23 | Added readme for TPCL Expression Editor | 19:03 |
| CIA-23 | Just some quick notes on usage. | 19:03 |
| xdotx | http://yro.slashdot.org/yro/07/08/14/2027231.shtml -- too funny | 19:24 |
| tpb | <http://ln-s.net/pJr> (at yro.slashdot.org) | 19:24 |
| nash | xdotx: It's an interesting game... I wonder if they'll ask for more money from them | 19:43 |
| nash | mithro: You there? | 20:50 |
| nash | So xdotx: When do you merge rfts to mainline? | 21:33 |
| * xdotx shrugs | 21:34 | |
| xdotx | nash: llnz said he would occasionally | 21:34 |
| nash | You should poke him... that way we can get more testing for both | 21:34 |
| *** DystopicFro has joined #tp | 21:37 | |
| nash | Heyo Fro | 21:38 |
| nash | xdotx: Okay... trying to build RFTS I get: | 21:41 |
| nash | (in configure) syntax error near: _LT_SHELL_INIT(lt_ltdl_dir='') | 21:42 |
| nash | (the lt_ltdl_dir is the error) | 21:42 |
| nash | apparently | 21:42 |
| nash | Any ideas? | 21:42 |
| * nash hates autofoo | 21:42 | |
| xdotx | hmm | 21:49 |
| * nash wonders if he needs a new version of auto something-or-other | 21:50 | |
| xdotx | nash: what version of automake? | 21:50 |
| nash | 1.9.6 | 21:50 |
| xdotx | that's correct | 21:51 |
| nash | autoconf is 2.60a | 21:51 |
| xdotx | i recently reset up everything on my laptop and ran in to some problems. had to use older versions of some stuff | 21:51 |
| xdotx | i'm running autoconf 2.61 | 21:51 |
| nash | Upgrading now | 21:53 |
| nash | nope | 21:54 |
| nash | autoconf is 2.61 | 21:55 |
| nash | libtool version? | 21:55 |
| xdotx | that was my next guess: 1.5.22 here | 21:55 |
| nash | 1.5.24 - so pretty close | 21:56 |
| nash | Any other ideas? | 22:01 |
| xdotx | mm, sec | 22:01 |
| xdotx | hmm. yeah, no ideas. | 22:05 |
| xdotx | autoconf, automake and libtool are the only preconfigure tools used | 22:06 |
| nash | what does the LT_SHELL_INIT line look like in your configure.sh? | 22:06 |
| nash | It's during the ./configure pass | 22:06 |
| xdotx | hmm, i don't see an LT_SHELL_INIT in my configure | 22:09 |
| nash | With an _ at the front | 22:10 |
| nash | Still... that is interesting... | 22:10 |
| xdotx | nash: you have the libltdl dir in tpserver-cpp right? | 22:12 |
| nash | yep | 22:12 |
| *** mithro has quit IRC | 22:17 | |
| xdotx | nash: the only thing i see in configure --help for libtool seems quite unrelated | 22:18 |
| nash | Typical autoconf stuff :-( | 22:21 |
| xdotx | :/ | 22:23 |
| *** mithro has joined #tp | 22:25 | |
| mithro | nash: ping? | 22:26 |
| nash | mithro: pong | 22:26 |
| nash | Dude - you got any ideas about my autofoo errors for tpserver-cpp? | 22:26 |
| mithro | nash: no | 22:27 |
| mithro | it sounds like there is something wrong with libltdl | 22:28 |
| mithro | but I have no problem building | 22:28 |
| nash | I have a version 3 and a version 7 available | 22:29 |
| nash | Moving to the v3 - I had v7 | 22:30 |
| nash | mithro: Did you see my patches on the tp-devel list? | 22:30 |
| mithro | what does "./autogen.sh" do? | 22:30 |
| xdotx | runs aclocal, autoconf, automake | 22:30 |
| xdotx | etc | 22:31 |
| nash | That fixed it... | 22:31 |
| mithro | xdotx: I know what it does, just wanted to know what it did for nash | 22:31 |
| nash | Should I use mzscheme or guilde? | 22:31 |
| xdotx | :P | 22:31 |
| nash | mithro: Ran without issue | 22:31 |
| mithro | so it's the configure that is dieing with the error? | 22:31 |
| nash | Yeah. | 22:32 |
| nash | Well was | 22:32 |
| nash | DOwngrading libtldl fixed it | 22:32 |
| nash | So what is recommended scheme or guile? | 22:32 |
| nash | mithro: ? | 22:34 |
| mithro | nash: it shouldn't even be using your distro installed libltdl | 22:35 |
| nash | It is | 22:35 |
| mithro | nash: guile is recommened but both should work fine in theory | 22:35 |
| nash | configure barfed when there wasn't one | 22:35 |
| mithro | nash: the patches are for libtpproto-cpp right? | 22:35 |
| mithro | nash: poke Lee about it | 22:35 |
| nash | Any version of guile? | 22:36 |
| mithro | tpserver-cpp includes a local libltdl because the debian one is borked | 22:36 |
| mithro | nash: 1.6 or 1.8 should work | 22:36 |
| nash | cool | 22:36 |
| nash | And yeah... I just wanted to know they got to the list... I haven't seen them back yet | 22:36 |
| mithro | okay cool | 22:43 |
| mithro | nash: so why where you hacking on libtpproto-cpp? | 23:12 |
| mithro | I though C programmers hated C++ | 23:12 |
| xdotx | hmm. you know.. i just noticed, C++ == C | 23:24 |
| mithro | xdotx: ? | 23:26 |
| xdotx | mithro: since it's a post-inc on C... | 23:27 |
| mithro | maybe they should have called it ++C :P | 23:28 |
| xdotx | it's like they're trying to say "C++ looks greater than C, but really it's the same" | 23:28 |
| * xdotx <3s C++ though | 23:28 | |
| xdotx | C is too hacky | 23:29 |
| * mithro wishes C++ was strongly typed | 23:29 | |
| xdotx | it is! just.. not always :P | 23:34 |
| xdotx | the only hacks are the whole zero thing and enums | 23:34 |
| mithro | xdotx: void* destories C++'s type system | 23:40 |
| xdotx | mithro: i forgot about that. | 23:43 |
| xdotx | hmm. why was that left in from C? | 23:43 |
| mithro | xdotx: dunno | 23:43 |
| xdotx | nobody uses it | 23:43 |
| mithro | xdotx: I'm not so sure :P | 23:43 |
| * xdotx twitches | 23:43 | |
| jotham | i know quite a few people who code in C++ like they were in C for the most part, just using C++ as a kind of 'super C' | 23:44 |
| jotham | afterall, templates are just very elaborate macros | 23:44 |
| jotham | </2 cents> | 23:45 |
| xdotx | ionno. i love templates. they're much stronger than macros, but definitely comparable | 23:47 |
| xdotx | they're getting an upgrade soon :) | 23:47 |
| xdotx | you'll be able to formalize template requirements with "concepts" | 23:48 |
| xdotx | jotham: and i would say those people are clearly not C++ programmers | 23:50 |
| jotham | they are C programmers | 23:50 |
| jotham | i thought that was clear =) | 23:50 |
| xdotx | ah ;) | 23:51 |
| jotham | i found C++ to be too unproductive | 23:52 |
| jotham | but i know a lot of C++ guys who love it | 23:52 |
| jotham | i used to use C++ whenever i needed to speed python code up, but i think i need to learn to do it with C instead of C++ | 23:52 |
| * xdotx nods | 23:53 | |
| xdotx | i could see using C for that over C++ | 23:53 |
| xdotx | optimizing small things is better done in C, for certain | 23:53 |
Generated by irclog2html.py 2.5 by Marius Gedminas - find it at mg.pov.lt!
