| *** tpb has joined #tp | 00:00 | |
| *** ChanServ sets mode: +o tpb | 00:00 | |
| nash_ | heyo | 00:20 |
|---|---|---|
| nash_ | hmm... I've got me a underscore | 00:21 |
| *** nash has quit IRC | 00:21 | |
| *** nash_ is now known as nash | 00:21 | |
| *** nash_ has joined #tp | 00:21 | |
| nash | ahh | 00:22 |
| *** nash_ has quit IRC | 00:22 | |
| nash | mithro: pong | 00:22 |
| mithro | nash: any idea whats up with galaxie? | 00:22 |
| mithro | is it that I need a newer ecore like llnz suggested? | 00:22 |
| nash | Yeah | 00:24 |
| nash | I believe that is the case | 00:24 |
| nash | That was the API break I mentioned. | 00:24 |
| nash | Not sure why it worked for you before at all however if you updated | 00:24 |
| nash | I didn't go through it on the weekend for you - packing :-( | 00:26 |
| CIA-3 | mithro tpclient-pywx-development * r8b9f4c8eab60 /windows/winMain.py: Removed unused values. | 01:16 |
| CIA-3 | mithro tpclient-pywx-development * r8413cdb765db /windows/winInfo.py: Fixes for translation of the resource stuff. | 01:16 |
| CIA-3 | mithro tpclient-pywx-development * r2acb168e2db8 / (12 files in 2 dirs): | 01:16 |
| CIA-3 | Removed a lot of excess prints. | 01:16 |
| CIA-3 | Removed the old debug stuff which was broken anyway. | 01:16 |
| CIA-3 | mithro tpclient-pywx-development * r817360c4d8e5 / (15 files in 4 dirs): Make the client installable. | 01:16 |
| mithro | nash: so the fix is to wait for a new ecore to filter down? | 01:27 |
| nash | For that one.. unfrotunately yes :-( | 01:28 |
| nash | Where are you getting them from? | 01:29 |
| * nash wonders why they aren't already there | 01:29 | |
| mithro | from edevelop | 01:29 |
| mithro | the latest debs where from the 17th of July | 01:29 |
| * nash looks to see when the changes went in | 01:30 | |
| nash | Jul 26th | 01:33 |
| nash | More recent then I thought | 01:33 |
| nash | One of the weird things is since august there has been nightly automatic building for the whole archive :-( | 01:34 |
| mithro | nash: maybe the debs have moved? | 01:50 |
| nash | It's possible | 01:50 |
| nash | There is massive website rearranging | 01:50 |
| * nash looks | 01:50 | |
| mithro | yeah I saw that | 01:53 |
| nash | http://ubuntuforums.org/showthread.php?t=97199&highlight=E17+cvs | 01:55 |
| tpb | <http://ln-s.net/nPD> (at ubuntuforums.org) | 01:55 |
| nash | There is that - but that is build from source - using the easy_e17 script | 01:55 |
| nash | Chews a lump of bandwidth obviously | 01:56 |
| nash | But you get the whole hog on the positive side | 01:58 |
| mithro | I prefer packaged stuff personally | 02:01 |
| nash | Yeek.. .that page is 52 page long | 02:06 |
| nash | Can't see it currently packaged anywhere | 02:10 |
| nash | edevelop now redirects to enlightenment org | 02:12 |
| *** llnz has joined #tp | 04:20 | |
| xdotx | llnz: how (and when) do I get the selected object to set the number of turns, during order creation? | 04:46 |
| llnz | createFrame could well be the best place | 04:47 |
| llnz | cf move order | 04:48 |
| xdotx | and i should/could use game->getOrderManager()->getOrderQueue(orderqueueid)->getObjectId() to get the selected obj? | 04:48 |
| llnz | yeah | 04:50 |
| llnz | i might make a shorter on (in Order baseclass) | 04:50 |
| llnz | s/on/one/ | 04:50 |
| xdotx | llnz: so then, what does it mean if that object is bs? | 04:50 |
| xdotx | order queue isn't associated with the object correctly? | 04:50 |
| *** greywhind has quit IRC | 04:51 | |
| llnz | if the id is 0, then no object assigned | 04:51 |
| xdotx | the order queue id looks right, but the obj id is 0 | 04:53 |
| llnz | yeah | 04:53 |
| mithro | llnz: does tpserver-cpp set the velocity correctly? | 05:14 |
| llnz | should do | 05:14 |
| mithro | hrm... | 05:14 |
| mithro | do these numbers look right? | 05:15 |
| mithro | (2633658476L, 1717981548, 0) (158475693, 122005961, 0) | 05:15 |
| mithro | pos, velcoity | 05:15 |
| llnz | about right, depends on max speed | 05:16 |
| mithro | hrm... | 05:19 |
| mithro | I'm obvisouly doing something wrong | 05:19 |
| mithro | woot, that works! | 05:22 |
| CIA-3 | llnz tpserver-cpp-rfts * r5e3d27145112 / (quickstart-minisec.conf quickstart-mtsec.conf): | 05:27 |
| CIA-3 | Added info logging to console to quickstart configurations. | 05:27 |
| CIA-3 | Because mithro asked. | 05:27 |
| CIA-3 | fr33.em4il tpserver-cpp-rfts * r39e54c8888bc / (quickstart-minisec.conf quickstart-mtsec.conf): | 05:27 |
| CIA-3 | Merge with git://git.thousandparsec.net/git/tpserver-cpp.git | 05:27 |
| CIA-3 | updating | 05:27 |
| CIA-3 | fr33.em4il tpserver-cpp-rfts * r971f0e6ab613 /modules/games/rfts/ (buildfleet.cpp fleet.cpp fleet.h rfts.cpp rfts.h): cleaning up build fleet | 05:27 |
| CIA-3 | fr33.em4il tpserver-cpp-rfts * rbce22727b568 /modules/games/rfts/ (Makefile.am fleet.cpp move.cpp move.h rfts.cpp): working on move order | 05:27 |
| CIA-3 | fr33.em4il tpserver-cpp-rfts * r0d8e74940035 /modules/games/rfts/ (fleet.cpp move.cpp): fixing bug with fleet creation / orders | 05:27 |
| llnz | cool | 05:28 |
| mithro | bblr | 05:30 |
| *** mithro has quit IRC | 05:52 | |
| *** mithro has joined #tp | 05:52 | |
| *** mithro changes topic to "http://www.thousandparsec.net | 96,336 lines of code (minus 12k for libltdl) | GSoC started! | http://www.thousandparsec.net/~irc/logs" | 05:54 | |
| mithro | xdotx: seeing lots of RFTS commits? | 05:59 |
| xdotx | mithro: the trick is to commit on 1-2 line changes ;) | 06:00 |
| xdotx | (j/k) | 06:01 |
| mithro | :) | 06:01 |
| mithro | xdotx: isn't it 3am where you are? | 06:07 |
| mithro | llnz: ping? | 06:12 |
| llnz | mithro: pong | 06:14 |
| mithro | llnz: do you get the /etc/cron.weekly/download-updates emails? | 06:15 |
| xdotx | mithro: heh, yep. it's 3 | 06:15 |
| llnz | mithro: yes | 06:15 |
| mithro | llnz: feel free to login and do the update | 06:18 |
| mithro | xdotx: so you had much progress? | 06:18 |
| xdotx | mithro: progress, but it always feels like not enough | 06:20 |
| mithro | so can you build a fleet yet? | 06:20 |
| xdotx | testing in pytext | 06:20 |
| mithro | xdotx: the building part? | 06:22 |
| * xdotx nods | 06:23 | |
| xdotx | mithro: i step through the code and it looks like it should be working | 06:23 |
| mithro | xdotx: so want some help trying to figure it out? | 06:24 |
| xdotx | mithro: sure, but i probably should be getting to bed soon | 06:27 |
| mithro | xdotx: so where should I start? | 06:28 |
| xdotx | mithro: hmm, right now i'm confused on syntax for order_insert in pytext | 06:30 |
| mithro | order_insert in pytext sucks :) | 06:31 |
| xdotx | heh alright then | 06:31 |
| mithro | it's hardcoded pretty much | 06:36 |
| mithro | what is the format for your build-fleet instruction? | 06:37 |
| mithro | is it similar to the normal buildfleet? | 06:37 |
| * xdotx nods | 06:37 | |
| xdotx | should pretty much be the same | 06:38 |
| mithro | okay | 06:39 |
| mithro | pretty much != exactly? | 06:39 |
| xdotx | i think it's exactly the same | 06:39 |
| mithro | can you check? | 06:41 |
| xdotx | mithro: yep, same | 06:44 |
| xdotx | er, wait | 06:44 |
| xdotx | no, mine doesn't have a fleet name | 06:44 |
| xdotx | just a fleet list | 06:44 |
| mithro | okay | 06:45 |
| mithro | your not going to be able to add it using tpclient-pytext then | 06:46 |
| xdotx | mithro: i'm going to try adding it with pywx and checking for objects with pytext | 06:50 |
| mithro | thats probably a good idea | 06:50 |
| mithro | just adding a few quick features to tpclient-pytext which may make it easier for you | 06:50 |
| xdotx | the object gets created (and added) on the server, but then when i check with the client for the object number (which i'm sure is correct), it's not there | 06:54 |
| xdotx | i really should get some sleep though | 06:55 |
| mithro | xdotx: okay | 07:00 |
| xdotx | mithro: i should definitely get this finished tomorrow and start on more interesting things the next day | 07:05 |
| xdotx | er, tomorrow/ later today | 07:06 |
| mithro | okay | 07:06 |
| mithro | i'll see you tommorrow | 07:06 |
| *** mithro has quit IRC | 07:26 | |
| *** mithro has joined #tp | 07:56 | |
| *** pschulz01 has joined #tp | 08:35 | |
| CIA-3 | mithro tpclient-pytext * r61dd9ee8f278 /tpclient-pytext: | 08:51 |
| CIA-3 | Make order_inserting a bit nicer with the totally dynamic orders libtpproto-py uses. | 08:51 |
| CIA-3 | order_desc <id> - Get an order description | 08:51 |
| CIA-3 | order_help <name> - Get help on how to insert an order | 08:51 |
| CIA-3 | order_insert has been updated so it does a whole bunch of error checking now too. | 08:51 |
| CIA-3 | mithro libtpproto-py * r939ff4c74aae /tp/netlib/xstruct.py: Better error message if xstruct runs out of arguments. | 08:52 |
| CIA-3 | mithro libtpproto-py * rc194874eeb07 /tp/netlib/objects/ (OrderDesc.py constants.py): | 08:52 |
| CIA-3 | Allow a client to figure out the names of arguments types. | 08:52 |
| CIA-3 | (Probably needs a cleanup...) | 08:52 |
| mithro | jotham: ping? | 08:52 |
| * llnz wanders off | 08:52 | |
| llnz | later all | 08:52 |
| *** llnz has quit IRC | 08:52 | |
| pschulz01 | mithro: Which package did you want me to have a look at? tpclient-pywx ? | 08:59 |
| mithro | pschulz01: yeah, the development versions | 09:05 |
| mithro | there is no easy way to package tpclient-pywx's stable version | 09:06 |
| pschulz01 | mithro: ? | 09:06 |
| pschulz01 | mithro: I don't understand. | 09:07 |
| pschulz01 | mithro: Is it also in git? | 09:07 |
| mithro | pschulz01: there are currently two branches of tpclient-pywx | 09:07 |
| mithro | the "stable" version which is only getting bug fixes | 09:07 |
| pschulz01 | mithro: Are they bot in git? | 09:07 |
| pschulz01 | both | 09:07 |
| mithro | and the "development" version which is getting new development | 09:07 |
| mithro | yeah | 09:07 |
| pschulz01 | Are they branched? | 09:08 |
| mithro | git://git.thousandparsec.net/git/tpclient-pywx.git <-stable | 09:08 |
| mithro | git://git.thousandparsec.net/git/tpclient-pywx.git#development <- development | 09:08 |
| pschulz01 | OK.. got that one | 09:08 |
| mithro | development branched off from stable about 6-12 months ago | 09:08 |
| pschulz01 | mithro: I just copy/merge the 'debian' dir from stable into development. | 09:09 |
| mithro | yeah possible | 09:09 |
| pschulz01 | mithro: (Although I'll have to figure out how to do that.) | 09:09 |
| mithro | a merge wouldn't be possible | 09:09 |
| mithro | just copy and commit | 09:10 |
| pschulz01 | mithro: Manual copy then. | 09:10 |
| pschulz01 | mithro: Yeah. | 09:10 |
| pschulz01 | Ok.. looking at it. | 09:10 |
| mithro | stable and development have diverged to far from each other | 09:10 |
| mithro | the new stuff which should let you install tpclient-pywx only went into the development branch | 09:10 |
| mithro | o btw the development branch of tpclient-pywx depends on the development branch of libtpclient-py too | 09:11 |
| pschulz01 | mithro: It is possible to 'cherry-pick' changes from one branch to another.. but I'm not exactly sure how to do that yet. | 09:11 |
| mithro | git-cherry-pick | 09:11 |
| mithro | I use that sometimes to back/forward port changes | 09:12 |
| pschulz01 | Does the development branch have a version? | 09:13 |
| pschulz01 | I'll have to call it something like '-devel' | 09:14 |
| mithro | 0.3.x | 09:15 |
| mithro | tim@ultraslim:~/oss/tp/tpclient-pywx-dev$ more version.py | 09:15 |
| mithro | version = (0, 3, 0) | 09:15 |
| pschulz01 | mithro: ta. | 09:16 |
| mithro | probably want a date the deb was built as well | 09:16 |
| pschulz01 | Um.. Ok - 20070706 | 09:17 |
| pschulz01 | Um.. Ok -20070706 | 09:18 |
| mithro | yeah something like that | 09:18 |
| mithro | I know you need some magic in the version number too so that 0.3.0 > 0.3.0-<date> | 09:18 |
| pschulz01 | mithro: I scare to ask in #ubuntu-motu again.. maybe I'll go ask in #debian-devel | 09:19 |
| pschulz01 | :-) | 09:19 |
| mithro | he he | 09:20 |
| mithro | packaging yet to be released things is always hard from my understanding | 09:20 |
| pschulz01 | mithro: Normally the suffix is -n where n goes 1,2,3,, etc | 09:20 |
| mithro | pschulz01: yeah but that is only for "released" software | 09:21 |
| pschulz01 | mithro: The 0.3.0 is you're number.. which should be updated by you. | 09:21 |
| DystopicFro | b [p; | 09:21 |
| mithro | hey DystopicFro's cat | 09:21 |
| pschulz01 | DystopicFro: Wa? | 09:21 |
| pschulz01 | mithro: So maybe.. 0.3.0.20070706-1 | 09:22 |
| mithro | pschulz01: 0.3.0 is the version that this client will be when released | 09:22 |
| mithro | so I guess you could call it "almost 0.3.0"? :) | 09:22 |
| pschulz01 | mithro: Package will be -1 | 09:22 |
| pschulz01 | 0.3.0-1 | 09:22 |
| mithro | hrm.... | 09:22 |
| pschulz01 | Which is 0.3.0 of the 'released' software with the '-1' packaging. | 09:23 |
| pschulz01 | mithro: (So ignore me :-) | 09:23 |
| pschulz01 | mithro: Make the daily builds.. 0.3.0.<date> | 09:23 |
| mithro | 0.3.0-1 would be the first packaged version of the 0.3.0 release right? | 09:24 |
| pschulz01 | Yes | 09:24 |
| pschulz01 | If I screw up then 0.3.0-2 is released. | 09:24 |
| mithro | yeah | 09:24 |
| mithro | but the stuff in git is not a "release" | 09:25 |
| pschulz01 | mithro: Not until you 'tag' it... | 09:25 |
| mithro | right | 09:25 |
| mithro | so for the daily builds you need something which evaluates to less then 0.3.0 | 09:26 |
| pschulz01 | mithro: Um.. I can take the latest git.. apply a tag for 0.3.0.<Todays date>, and built a release (tar) and then package that. | 09:27 |
| mithro | but | 09:27 |
| mithro | 0.3.0.<todays date> > 0.3.0 | 09:28 |
| pschulz01 | Not sure :-) Maybe not | 09:28 |
| pschulz01 | mithro: Asking in #debian-devel | 09:28 |
| mithro | pschulz01: | 09:30 |
| mithro | dpkg --compare-versions "1.0-4.1" gt "1.0-4joe5" && \ | 09:30 |
| mithro | echo "NMU version -4.1 greater than -4joe5" | 09:30 |
| mithro | http://people.debian.org/~calvin/unofficial/ | 09:30 |
| tpb | Title: Packaging tips for unofficial Debian packages (at people.debian.org) | 09:30 |
| pschulz01 | mithro: haha.. ta. | 09:31 |
| mithro | Problems will arise because dpkg will consider the final version 1.0 lower than the beta or release candidate version. The solution is to use a version like 0.99+1.0rc2-0joe1 which uses a lower version than 1.0 (0.99) and joins the release candidate version with a plus sign. This way the final version is greater than the previous one: 0.99+1.0rc2-0joe1 < 1.0-0joe1. | 09:31 |
| mithro | so you probably want | 09:32 |
| mithro | 0.2.99+0.3.0git20070707-0 ? | 09:32 |
| pschulz01 | mithro: Have to go... sorry.. but that looks like a good start. | 09:33 |
| mithro | hrm, that doesn't work RC releases :/ | 09:34 |
| mithro | tim@ultraslim:~$ dpkg --compare-versions "0.2.99+0.3.0.20070707-0" gt "0.2.99+0.3.0rc1" ; echo $? | 09:34 |
| *** pschulz01 has quit IRC | 09:34 | |
| mithro | DystopicFro: ping? | 09:44 |
| mithro | it being 7am I think he may be asleep | 09:44 |
| mithro | dunno where that message came from | 09:44 |
| mithro | well I'm off to watch some TV | 09:54 |
| *** tpb has joined #tp | 10:16 | |
| *** ChanServ sets mode: +o tpb | 10:16 | |
| *** JLP has quit IRC | 12:58 | |
| *** JLP has joined #tp | 13:04 | |
| CIA-3 | frodough tpruledev * r57e587ed3bb2 /src/gui/ (TpclEditorDialog.py xrc/EditorDialog.xrc): New GUI for TPCL Expression Editor | 13:30 |
| CIA-3 | frodough tpruledev * rd0dbc9ef4b60 /src/ (5 files in 4 dirs): | 13:30 |
| CIA-3 | Added support for indentation in TPCL Expressions | 13:30 |
| CIA-3 | Now things stay nice and pretty. Good god though this won't scale at | 13:30 |
| CIA-3 | all for larger expressions. It's probably bad even now. I need a less | 13:30 |
| CIA-3 | powerful computer for testing purposes. | 13:30 |
| mithro | JLP: ping? | 13:30 |
| mithro | DystopicFro: ping? | 13:30 |
| DystopicFro | mithro: pong | 13:33 |
| DystopicFro | ahoyhoy | 13:33 |
| mithro | hey DystopicFro | 13:33 |
| mithro | hows everything going? | 13:34 |
| DystopicFro | pretty good | 13:34 |
| DystopicFro | how's things for you? | 13:34 |
| mithro | good, just about to head to bed | 13:34 |
| DystopicFro | ah, yea, I always see you around at all hours >.< | 13:34 |
| DystopicFro | must be the wee hours of the morning over there | 13:35 |
| mithro | ahh, your files are dos formatted again | 13:35 |
| DystopicFro | bahhhhhhhhhhhhhhh | 13:35 |
| DystopicFro | bloody editor | 13:35 |
| mithro | DystopicFro: | 13:37 |
| mithro | getting lots of errors like this | 13:37 |
| mithro | Traceback (most recent call last): | 13:38 |
| mithro | File "/home/tim/oss/tp/tpruledev/src/gui/TpclEditorDialog.py", line 102, in OnInsert | 13:38 |
| mithro | self.root_expression.InsertExpression(pos, expression) | 13:38 |
| mithro | File "/home/tim/oss/tp/tpruledev/src/tpcl/Representation.py", line 390, in InsertExpression | 13:38 |
| mithro | raise ValueError('There is no expression at offset %d' % offset) | 13:38 |
| mithro | ValueError: There is no expression at offset 0 | 13:38 |
| mithro | Traceback (most recent call last): | 13:38 |
| mithro | File "/home/tim/oss/tp/tpruledev/src/gui/TpclEditorDialog.py", line 102, in OnInsert | 13:38 |
| mithro | self.root_expression.InsertExpression(pos, expression) | 13:38 |
| mithro | File "/home/tim/oss/tp/tpruledev/src/tpcl/Representation.py", line 390, in InsertExpression | 13:38 |
| mithro | raise ValueError('There is no expression at offset %d' % offset) | 13:38 |
| mithro | ValueError: There is no expression at offset 23 | 13:38 |
| DystopicFro | Bah encoding. I knew that it was too good to be true that it worked flawlessly on my comp | 13:40 |
| mithro | ? | 13:40 |
| DystopicFro | The StyledTextCtrl does funky stuff with its character encoding | 13:40 |
| mithro | inserting a boolean or number doesn't seem to work | 13:40 |
| DystopicFro | And since I base all of the operations on expressions by offset that completely messes things up | 13:40 |
| DystopicFro | ah, those things, aye, are not yet functional | 13:40 |
| DystopicFro | I was just starting to work on that | 13:40 |
| mithro | it seems to work if I put the cursor just before the *EXP* | 13:42 |
| DystopicFro | mithro: aye, I'm pretty sure that it's just an encoding issue that linux handles differently than windows | 13:43 |
| mithro | what is suppose to happen? | 13:43 |
| mithro | do I have to put the cursor at *EXP* before doing the insert? | 13:44 |
| DystopicFro | ah | 13:44 |
| DystopicFro | yes | 13:44 |
| DystopicFro | I suppose I should write a quick readme | 13:44 |
| DystopicFro | Insert pushes the currently selected expression into the expansion point under the cursor | 13:44 |
| DystopicFro | so you have to pick where you want to insert the code first | 13:44 |
| mithro | DystopicFro: have you thought of making those *EXP*'s buttons which bring up a dialog box which lets you select the TPCL code bock? | 13:44 |
| mithro | then it could only show the TPCL code blocks which make sense in that context? | 13:45 |
| DystopicFro | mithro: that's an idea that I hadn't thought of before, really | 13:46 |
| DystopicFro | but I've bounced around that issue a lot, in terms of how much assistance the editor should give | 13:46 |
| mithro | you already have a text editor in the client? | 13:47 |
| mithro | I think this is about trying to make building up expressions point and click easy | 13:47 |
| mithro | do you know if you can insert controls into the box? | 13:47 |
| DystopicFro | I'm pretty sure that widgets can't be inserted | 13:48 |
| *** CGI252 has joined #tp | 13:48 | |
| mithro | DystopicFro: arg, that sucks | 13:48 |
| DystopicFro | but there are ways to provide overt emphasis to blocks of text (i.e. borders) | 13:48 |
| DystopicFro | and then it could be a response to the clicking event that brings up another dialog | 13:48 |
| mithro | DystopicFro: if you can get that to work, it might be okay | 13:50 |
| mithro | another option might be using a HtmlWindow? | 13:50 |
| *** CGI252 has quit IRC | 13:51 | |
| DystopicFro | Aye, that's an option, but it wouldn't lex on its own and wouldn't do nice things like match parentheses | 13:51 |
| mithro | yeah | 13:52 |
| DystopicFro | My concern is in limiting things so much that a user would be very limited in what they could do | 13:52 |
| DystopicFro | what I've been striving for is a setup that will allow the user easy access to information about various functions (descriptions with examples of usage, for example) and organizing everything logically | 13:53 |
| DystopicFro | the editor takes care of syntax and everything else and lets the user worry about functionality | 13:53 |
| * mithro thinks | 13:54 | |
| mithro | take the example of wanting to create something compound component | 13:54 |
| mithro | which returns different "cloaking" strengths depending on other components on a hull | 13:55 |
| mithro | say, "if ship is armed - return 0, for each other cloak add +1, for each other electrical component add +0.1, for each cargo hold add -5, result must still be positive" | 13:57 |
| mithro | I need to write some tpcl to repsent that | 13:58 |
| mithro | need something like (if (> design.armed) (let x 0)) (let x (+ x 1*design.cloaks)) (let x (+ x 0.1* .... ? | 14:00 |
| mithro | If I could just start with | 14:02 |
| mithro | (lambda *EXP*) | 14:02 |
| mithro | I click on *EXP* and select the if | 14:02 |
| mithro | (lambda (if *BOOL* *EXP* *EXP*)) | 14:03 |
| mithro | I click on *BOOL* and select the > option | 14:03 |
| * DystopicFro nods | 14:03 | |
| mithro | (lambda (if (> *EXP* *EXP*) *EXP* *EXP*)) | 14:03 |
| mithro | click on the first *EXP* and select the armed property | 14:04 |
| mithro | (lambda (if (> design.armed *EXP*) *EXP* *EXP*)) | 14:04 |
| mithro | click on the second *EXP*, select number literal, enter 0 | 14:04 |
| mithro | (lambda (if (> design.armed 0) *EXP* *EXP*)) | 14:04 |
| mithro | and onwards.... | 14:04 |
| mithro | with that kind of format I think you might have a hope of building reasonably complicated expressions? | 14:05 |
| mithro | maybe this use case too? | 14:05 |
| mithro | I stuffed up in the above example and it should be > 1 | 14:05 |
| mithro | I click on the '0', and change it to a '2'? | 14:06 |
| mithro | or I click on the 0 and select remove | 14:06 |
| mithro | and it goes back to being *EXP* ? | 14:06 |
| mithro | does that make any sense? | 14:07 |
| DystopicFro | mithro: aye, complete sense | 14:07 |
| mithro | DystopicFro: the second question is, does it fit with what you are trying to do? | 14:07 |
| DystopicFro | the issues that I feel are present in that approach, however, are the human factor of deciding what's what - i.e., what should the *BOOL* in the if be filled with | 14:08 |
| DystopicFro | Those labels, the *BOOL*, *SYMBOL*, *EXPR* are holdovers from what I originally conceived of | 14:08 |
| DystopicFro | Which was very similar to what you're talking about | 14:08 |
| *** greywhind has joined #tp | 14:08 | |
| mithro | DystopicFro: oh? | 14:09 |
| mithro | hey greywhind | 14:09 |
| DystopicFro | But in pursuing that I started expending a lot of effort in trying to provide absolute perfection in the classification of expressions | 14:09 |
| greywhind | hey mithro | 14:09 |
| greywhind | awake later and later every day? | 14:09 |
| mithro | DystopicFro is distracting me :) | 14:10 |
| DystopicFro | and I went back and re-read a bit of the R5RS specification | 14:10 |
| DystopicFro | and realized that what I was trying to do was completely counter-productive | 14:10 |
| DystopicFro | and was introducing the potential for a lot of error and also just the possibility of artificially limiting the user | 14:11 |
| mithro | greywhind: btw, had any more thoughts? It would be really good if you could take another look helping out with a client | 14:11 |
| mithro | DystopicFro: do you have an example? | 14:11 |
| DystopicFro | Well, in the case of conditionals | 14:12 |
| DystopicFro | What's an acceptable test? | 14:12 |
| DystopicFro | If the ultimate value of an expression is a boolean value it should be acceptable, yes? | 14:12 |
| mithro | DystopicFro: yeah, sounds about right | 14:12 |
| greywhind | mithro: i would be happy to start by helping with a client, but i think that at some point (perhaps half-way?) i'd like to switch to making an AI (either a computer-controlled player AI or an "advisor") | 14:12 |
| mithro | an AI advisor would be pretty helpful | 14:13 |
| mithro | but we really need to concentrate on making the clients much more userfriendly :) | 14:13 |
| DystopicFro | mithro: and so attempting to limit what can be put in there by the context of the surroundings is both artificially limiting and error prone as it depends on what I decide is appropriate | 14:13 |
| DystopicFro | mithro: now, I'm all for perhaps including the sort of funcionality you're talking about as a secondary means of interface | 14:14 |
| DystopicFro | mithro: maybe accessed via a context menu? | 14:14 |
| mithro | DystopicFro: I personally would see it as the primary interface | 14:14 |
| mithro | DystopicFro: the idea is that ruleset designers aren't going to be huge programmers | 14:14 |
| mithro | (hence why they need a ruleset development environment :) | 14:15 |
| mithro | DystopicFro: well my interface doesn't necessarily have to "restrict" what you put in the *BOOL* part? | 14:15 |
| mithro | you could have your complete tree in the pop-up? | 14:15 |
| * mithro would also like to point out that he designed tpcl and the requirements stuff, and I can't even rattle the above simple example off the top of my head | 14:16 | |
| DystopicFro | mithro: for clarification - I see the tree being populated with all available functions that are built into TPCL as well as any expressions that the user chooses to save | 14:16 |
| DystopicFro | So I can see the list getting quickly overpopulated and hard to handle as a popup or as a secondary dialog | 14:17 |
| mithro | btw, most of the expressions won't be any more complicated then the above option | 14:18 |
| * DystopicFro still isn't convinced of the time-saving benefits of the context-menu/secondary dialog and so will implement it as well over the course of the week | 14:20 | |
| DystopicFro | mithro: I'll cobble something together that I think fits your vision and we'll see how it goes >.< | 14:20 |
| mithro | well, it's changing how the work flow goes | 14:20 |
| mithro | in your current system, I click on an option on the side, move my cursor to the position, then hit the insert key | 14:21 |
| mithro | with my system, I hit where I want the new expression to go, then select what I want to go there | 14:21 |
| * DystopicFro nods | 14:22 | |
| mithro | I don't even have to worry about "the cursor" | 14:22 |
| DystopicFro | I set up the workspace to reflect my own work flow | 14:22 |
| DystopicFro | I'll get something working where both interfaces are available and are fully functional | 14:23 |
| mithro | DystopicFro: on another note, if I was editing a complicated 20-line expression, I would probably want to use my normal editor | 14:24 |
| mithro | an "Open TPCL in another program" might be a nice option to have | 14:24 |
| DystopicFro | What I see as the biggest advantages of the RDE is that it can check your TPCL code for errors as it gets entered in | 14:25 |
| mithro | DystopicFro: I recommend you have a chat to nash about it | 14:25 |
| DystopicFro | And the two biggest features of the Expression Editor as being that it can provide a complete list of all available funcitons along with descriptions of what they do, and makes inserting them easy and free from any syntax errors or mistypings | 14:26 |
| DystopicFro | so, we're coming at it from different directions >.< | 14:26 |
| mithro | yeah it looks like we are | 14:26 |
| DystopicFro | mithro: I'll definitely have a talk with nash, hopefully things are more settled for him with the move and all that | 14:26 |
| mithro | your "Expression Editor" is more what I would call a "Helpful Text Editor", rather then an "Easy Expression Builder" | 14:27 |
| mithro | DystopicFro: ultimately he is the "boss" as far as your project is concerned | 14:27 |
| DystopicFro | mithro: definitely | 14:27 |
| DystopicFro | mithro: but after the expression editor is built it's easy enough to downsize it into an "easy expression builder" | 14:28 |
| mithro | what I actually pinged you about was intergrating tpserver-py with the ruleset editor | 14:28 |
| * DystopicFro nods | 14:28 | |
| DystopicFro | I remember the convo we had about that earlier | 14:28 |
| mithro | so, you managed to split the stuff which reads your config away from your gui? | 14:29 |
| DystopicFro | Aye, all the XML stuff is in XmlObjname modules | 14:30 |
| mithro | BTW do you use python 2.5? | 14:30 |
| DystopicFro | mitrho: aye | 14:30 |
| mithro | I see you are using element tree | 14:30 |
| mithro | here is how you should import it | 14:30 |
| mithro | # Need to find an ElementTree implimentation! | 14:30 |
| mithro | ET = None | 14:30 |
| mithro | errors = [] | 14:30 |
| mithro | try: | 14:30 |
| mithro | import elementtree.ElementTree as ET | 14:30 |
| mithro | except ImportError, e: | 14:30 |
| mithro | errors.append(e) | 14:30 |
| mithro | try: | 14:30 |
| mithro | import cElementTree as ET | 14:30 |
| mithro | except ImportError: | 14:30 |
| mithro | errors.append(e) | 14:30 |
| mithro | try: | 14:31 |
| mithro | import lxml.etree as ET | 14:31 |
| mithro | except ImportError: | 14:31 |
| mithro | errors.append(e) | 14:31 |
| mithro | try: | 14:31 |
| mithro | import xml.etree.ElementTree as ET | 14:31 |
| mithro | except ImportError: | 14:31 |
| mithro | errors.append(e) | 14:31 |
| mithro | if ET is None: | 14:31 |
| mithro | raise ImportError(str(errors)) | 14:31 |
| mithro | you shouldn't need the elementtree included in your tpruledev then | 14:31 |
| greywhind | mithro: wouldn't it be easier to use a pastebin? | 14:31 |
| DystopicFro | well | 14:31 |
| mithro | greywhind: probably :) | 14:31 |
| DystopicFro | mitrho: the reason for including elementtree is the fact that I've changed it up a bit | 14:32 |
| mithro | as xml.etree.ElementTree <-- comes default with python | 14:32 |
| greywhind | mithro: i've got a script for my IRC client that allows me to type /paste to automatically paste and link whatever's in my clipboard :) | 14:32 |
| DystopicFro | edited the output so that it prints out much more nicely | 14:32 |
| DystopicFro | but as that's not necessary | 14:32 |
| DystopicFro | I'll go ahead and alter the imports | 14:32 |
| mithro | DystopicFro: is that based on the stuff I gave you? | 14:32 |
| DystopicFro | mithro: yes, but also printing out attributes in a nicer fashion since so much data is stored as attributes | 14:33 |
| mithro | can you seperate out your code from the base elementtree? | 14:34 |
| mithro | because it could probably be useful for other things | 14:34 |
| DystopicFro | It goes against everything that I've been conditioned to structure my thoughts as | 14:34 |
| DystopicFro | but since python doesn't limit access to object members | 14:34 |
| DystopicFro | I should be able to pull it out of the elementtree package with a problem | 14:34 |
| mithro | DystopicFro: "forking" a package is generally considered bad unless you have a *really* good reason | 14:35 |
| mithro | as now every time there is a new elementtree release you have to merge their changes into your own | 14:36 |
| DystopicFro | mithro: aye, but given that the last release was in 2005 I'm not all too worried about that | 14:37 |
| DystopicFro | but then, best practices are there because they are, in fact, "best" in most cases >.< | 14:37 |
| mithro | DystopicFro: ahh, that is because elementtree is now part of stock python | 14:37 |
| mithro | IE elementtree development occurs inside the python tree :) | 14:37 |
| * DystopicFro wipes the egg off of his face | 14:37 | |
| DystopicFro | oh. | 14:38 |
| DystopicFro | Yea. Didn't see that. | 14:38 |
| mithro | DystopicFro: don't worry, only found out a week or two ago | 14:38 |
| mithro | The Element type is available as a pure-Python implementation for Python 1.5.2 and later. A C implementation is also available, for use with CPython 2.1 and later. The core components of both libraries are also shipped with Python 2.5 and later. | 14:39 |
| mithro | There's also an independent implementation, lxml.etree, based on the well-known libxml2/libxslt libraries. This adds full support for XSLT, XPath, and more. | 14:39 |
| DystopicFro | mithro: ah, kk | 14:40 |
| DystopicFro | I'll go ahead and stick those imports in later today | 14:40 |
| mithro | they are about 90% compatible for what we want to use em for | 14:40 |
| mithro | so the ./game_objects directory is what I want to look at if I'm using tpruledev code? | 14:41 |
| DystopicFro | hrm | 14:41 |
| mithro | because I'm seeing some gui imports in that directory? | 14:41 |
| * DystopicFro thinks to see if he did anything that makes it imposible to use game objects without nodes | 14:42 | |
| DystopicFro | in the game objects directory? | 14:42 |
| DystopicFro | there shouldn't be any gui imports | 14:42 |
| mithro | tim@ultraslim:~/oss/tp/tpruledev/src/game_objects$ grep gui *.py | 14:43 |
| mithro | Category.py:from gui import CategoryPanel | 14:43 |
| mithro | Component.py:from gui import ComponentPanel | 14:43 |
| mithro | Property.py:from gui import PropertyPanel | 14:43 |
| mithro | tim@ultraslim:~/oss/tp/tpruledev/src/game_objects$ grep rde *.py | 14:43 |
| mithro | ObjectUtilities.py:import rde.Nodes | 14:43 |
| mithro | ObjectUtilities.py:from rde import ConfigManager | 14:43 |
| mithro | ObjectUtilities.py:class ObjectNode(rde.Nodes.DatabaseNode): | 14:43 |
| mithro | ? | 14:44 |
| DystopicFro | hm, the Panel imports are all things that should have been deleted many weeks ago | 14:45 |
| mithro | anyway I needed to be in bed 2-3 hours ago :) | 14:45 |
| DystopicFro | kk mithro, gnight >.< | 14:45 |
| DystopicFro | I'll recheck the game_object code | 14:45 |
| mithro | DystopicFro: i'm sure I've given you much food for thought :) | 14:45 |
| DystopicFro | and ferret out any references to other parts of the code that don't need to be there | 14:45 |
| DystopicFro | so ther eare no spurious imports | 14:45 |
| DystopicFro | mithro: aye, plenty o.O | 14:45 |
| mithro | DystopicFro: last thing before we go, I think it would be good if we could do a public release of tpruledev before the end of SoC, do you think that would be possible? | 14:46 |
| DystopicFro | The RDE without the expression editor should be ready to go | 14:46 |
| DystopicFro | the expression editor I hope to have mostly done by the end of this week | 14:46 |
| DystopicFro | mithro: So, it should be entirely possible | 14:47 |
| mithro | DystopicFro: coolioes! | 14:48 |
| mithro | anyway I'm really off now | 14:49 |
| mithro | greywhind: we should chat some time later | 14:49 |
| DystopicFro | kk, gnite mithro >.< | 14:49 |
| greywhind | mithro: sure - sleep well | 14:50 |
| *** xdotx has joined #tp | 15:48 | |
| *** Epyon has quit IRC | 16:03 | |
| *** tuna-fish has joined #tp | 16:08 | |
| *** Epyon has joined #tp | 16:08 | |
| *** Demitar has joined #tp | 16:43 | |
| *** Demitar has joined #tp | 17:28 | |
| tpb | tpb has joined on worldforge | 19:58 |
| tpb | disconnected from worldforge: Ping sent at 2007-08-06T21:04:22 not replied to. | 21:06 |
| *** xdotx has joined #tp | 21:25 | |
| DystopicFro | nash: ping? | 22:34 |
| CIA-3 | frodough tpruledev * rb7bd8a5d6738 /src/ (4 files in 4 dirs): Altered GUI for Expression Editor again | 22:36 |
| nash | DystopicFro: Pong! | 22:52 |
| DystopicFro | ack >.< | 23:20 |
| DystopicFro | 10 minutes too late | 23:20 |
| DystopicFro | nash: just checking in, had a talk with mithro earlier on today | 23:21 |
| DystopicFro | nash: we have differing opinions on the direction that the expression editor should be following | 23:21 |
| nash | heh | 23:21 |
| nash | Sorry - I wasn't here earlier house was settling today | 23:21 |
| nash | Is settling I shoudl say | 23:21 |
| nash | 35 minutes | 23:21 |
| DystopicFro | >.< | 23:22 |
| DystopicFro | so that's good right? aside from the hectic hubbub of the move, everything's all set for you? | 23:22 |
| nash | Hopefully | 23:23 |
| nash | just waiting for final confirmation | 23:23 |
| nash | Anyway - so how do you and mithro disagree? | 23:23 |
| DystopicFro | just in terms of the footprint of the expression editor, really | 23:24 |
| DystopicFro | I favor something meaty, an emphasis on an overall picture of tpcl and stored code snippits | 23:25 |
| DystopicFro | mithro's vision, if I understood correctly, was much more minimal | 23:25 |
| DystopicFro | a smaller, more quickly accessed context menu to pick tpcl expressions quickly | 23:25 |
| DystopicFro | A lot of the issue, I think, came from the fact that the interface for the expression editor is far from complete | 23:26 |
| DystopicFro | it's incredibly clunky and lacks a lot of the functionality and work flow that I have planned for it | 23:26 |
| nash | Based on that... I personally prefer the bigger view | 23:26 |
| nash | Priting out a list of expressions should be fairly easy to do... | 23:27 |
| DystopicFro | nash: I'm sure that I'm horribly misrepresenting mithro's POV, but the work-in-progress editor is working fairly well, I think | 23:27 |
| DystopicFro | aye | 23:27 |
| DystopicFro | I told mithro I would implement what I understood of his idea alongside my own as well, just for comparison purposes | 23:28 |
| *** mithro has joined #tp | 23:28 | |
| nash | Quick question: What are your plans after SoC ends? | 23:28 |
| * nash waves to mithro | 23:28 | |
| DystopicFro | mithro: ahoy | 23:28 |
| mithro | howdy people | 23:28 |
| mithro | hey DystopicFro, didn't think you would still be up when I got up :) | 23:29 |
| DystopicFro | nash: school and lots of it, I'm transfering uni's so I have a lot to make up | 23:29 |
| DystopicFro | mithro: I'm usually awake late at night, just with the gf | 23:29 |
| nash | When do you start? | 23:30 |
| DystopicFro | nash: but I plan on finishing what I've started, to the point where I'm satisfied with my work | 23:30 |
| DystopicFro | classes start on the 20th | 23:30 |
| mithro | nash: don't forget we have IRC logs :) | 23:30 |
| nash | okay | 23:31 |
| DystopicFro | mithro: when you get a chance pull the latest of the expression editor, I put in something more like my original vision for the interface | 23:31 |
| DystopicFro | mithro: left-click on an expression for the option to insert at that point - it would be trivial to add a context menu with the sort of items you want there as well, I think | 23:31 |
| mithro | DystopicFro: oooh... I like that | 23:32 |
| DystopicFro | mithro: cool - I think that's what I'll expand on, then, maybe offer a smaller selection of the basic tpcl expressions in the context menu and leave the more complex stuff to the tree control | 23:34 |
| mithro | DystopicFro: you could just pop-up that tree control? | 23:35 |
| DystopicFro | mithro: totally, but I quickly see that as getting out of control as I want to have every function that's in the spec available through the expression editor | 23:37 |
| mithro | DystopicFro: have you thought of a "help" browser type window? | 23:38 |
| mithro | which has the blocks on the left, and the help info on the right? | 23:38 |
| DystopicFro | mithro: to what extent? what I've got in mind is an info box that will pop up a dialog on the currently selected block | 23:38 |
| mithro | kind of what I assume would occur when you click the info button? | 23:38 |
| DystopicFro | I can totally expand it into something more like that, though | 23:39 |
| mithro | because that would be a really useful pop-up dialog | 23:39 |
| DystopicFro | yea, right now I store all of the tpcl blocks in xml | 23:39 |
| DystopicFro | and they're marked up with descriptions and a display string | 23:40 |
| DystopicFro | which I plan to use for the info dialogs (or the help browser) | 23:40 |
| mithro | does the bit inside the stars need to be EXP? | 23:50 |
| mithro | it could use useful if they had a short description? | 23:51 |
| mithro | IE (if *TEST* *WHEN-TRUE* *WHEN-FALSE*) | 23:51 |
| *** greywhind has joined #tp | 23:53 | |
| *** greywhind has joined #tp | 23:55 | |
| DystopicFro | mithro: it can vary, yes | 23:55 |
| DystopicFro | and I completely agree | 23:55 |
| mithro | DystopicFro: just a thought | 23:55 |
| * mithro has a memory like a bucket with no bottom | 23:56 | |
| mithro | anything you can do to make it so I don't have to remeber things is good :) | 23:56 |
| DystopicFro | again, I completely agree, the more info quickly and painlessly available, the better | 23:57 |
| *** greywhind has quit IRC | 23:59 | |
Generated by irclog2html.py 2.5 by Marius Gedminas - find it at mg.pov.lt!