| 00:25.25 | *** join/#picogui file (file@mctn1-7473.nb.aliant.net) |
| 01:05.00 | file | $20 USD for 128MB PC133 SDRAM, brand new - not opened, lifetime warranty |
| 01:05.07 | file | good/bad? :) |
| 01:06.49 | gonkulator | I wouldn't buy a 128 meg stick unless that was all the motherboard could take |
| 01:11.24 | file | ic |
| 01:13.14 | *** join/#picogui kidder (~s@h24-65-171-188.gv.shawcable.net) |
| 01:25.41 | njs | [ |
| 01:25.52 | njs | want my address? :-) |
| 01:26.20 | gonkulator | '[' isn't a letter |
| 01:26.30 | njs | bah |
| 01:26.42 | gonkulator | :D |
| 01:27.47 | njs | there's also X |
| 01:28.08 | njs | and I have R installed. |
| 01:28.09 | *** join/#picogui file (file@mctn1-2088.nb.aliant.net) |
| 01:28.26 | gonkulator | X is a program, not a unix command |
| 01:28.33 | gonkulator | and I have no idea what R is |
| 01:28.35 | njs | w is a program too. |
| 01:28.47 | njs | R is a free clone of S, a stat package |
| 01:28.54 | gonkulator | oh, ok |
| 01:29.22 | njs | if you don't want to count programs, zsh has "r" as a shell builtin :-) |
| 01:29.48 | njs | (and many shells have [ as a builtin :-P) |
| 01:31.48 | njs | 's'ok, I don't like brownies much anyway :-) |
| 01:31.50 | gonkulator | and if you knew what ferrand brownies were like, you wouldn't want one |
| 01:32.08 | gonkulator | I think the main ingredients are cat food and peanut butter |
| 01:40.07 | *** join/#picogui scanline (~micah@aden2-42-dhcp.resnet.Colorado.EDU) |
| 01:40.29 | gonkulator | wb scanline |
| 01:40.39 | scanline | hi |
| 01:40.46 | scanline | accidentally disconnected yoshi's ethernet while moving my speakers |
| 01:40.59 | scanline | now they're pointed out my door so we can have music in Brede's room across the hall |
| 01:42.57 | gonkulator | heh |
| 01:42.58 | gonkulator | oh |
| 01:43.07 | gonkulator | my brother just got super monkey ball 2 |
| 01:43.20 | gonkulator | he challenged me to one of those 50 lap races.... |
| 01:45.47 | gonkulator | hmm... |
| 01:45.56 | gonkulator | I wonder how things are going with the RTD people |
| 01:46.56 | scanline | you should come visit anyway :) |
| 01:47.05 | gonkulator | if it is looking like there will be no strike, OR if there is an easy route to boulder from denver, I'll come up tomorrow afternoon |
| 01:47.15 | scanline | okeydokey |
| 01:47.28 | gonkulator | if I come tomorrow, I'll bring my quintuple boot machine |
| 01:47.51 | gonkulator | I'll have to, for work on monday |
| 01:48.26 | gonkulator | windows 95, 98, 2000, XP and a slackware derivitive called Tiny Linux |
| 01:49.25 | *** join/#picogui invader_zak (noname@aden2-135-dhcp.resnet.Colorado.EDU) |
| 01:51.36 | gonkulator | howdy invader_zak |
| 01:53.36 | third | Can Tiny Linux fit on a single floppy? |
| 01:55.07 | gonkulator | no |
| 01:55.10 | gonkulator | it is slackware based |
| 01:55.24 | gonkulator | the base install is a 12 floppy set after the 2 floppy boot set |
| 01:55.54 | gonkulator | and it uses the 2.2.6 kernel |
| 01:55.57 | gonkulator | so it is kinda old |
| 01:56.13 | gonkulator | but I really only needed it to have a bootloader for the win* |
| 02:06.01 | *** join/#picogui file (file@mctn1-3895.nb.aliant.net) |
| 02:06.36 | third | I see. |
| 02:06.51 | gonkulator | yeah |
| 02:07.06 | gonkulator | for some odd reason, different versions of windows really don't play nice with eachother |
| 02:07.27 | third | Yes, I found that out the hard way. |
| 02:08.03 | file | gonkulator: hehe |
| 02:08.05 | third | I think Bill set it up like that on purpose, because no one could be that lame! LOL |
| 02:09.12 | third | I still haven't found a way to write to win2k partitions. |
| 02:09.31 | gonkulator | are you talking the partition table, or what? |
| 02:11.11 | third | Yes. I can see it when I run knoppix, but I can't write to it. |
| 02:11.36 | gonkulator | did you format it NTFS, or FAT32? |
| 02:11.52 | gonkulator | linux support for NTFS is still experimental |
| 02:11.53 | third | I think it was NTFS. |
| 02:11.59 | gonkulator | yeah |
| 02:12.20 | gonkulator | it will see the partition just long enough to puke on it and say "forget it" |
| 02:12.30 | gonkulator | metaphorically speaking |
| 02:12.45 | third | Oh yes, I found that out the hard way also. |
| 02:13.14 | lalo | scanline: ayt? |
| 02:13.17 | scanline | yep |
| 02:13.30 | lalo | yay :-) |
| 02:13.32 | Dentoid | scanline, ptk? |
| 02:13.36 | Dentoid | loe? |
| 02:13.38 | scanline | ptk? |
| 02:13.40 | Dentoid | ike! |
| 02:13.44 | Dentoid | kmo |
| 02:13.51 | gonkulator | aak |
| 02:13.53 | lalo | npk |
| 02:13.59 | Dentoid | scanline, just kidding. |
| 02:13.59 | gonkulator | pft |
| 02:14.00 | scanline | fop |
| 02:14.04 | scanline | ploo! |
| 02:14.05 | Dentoid | stfu |
| 02:14.07 | Dentoid | :) |
| 02:14.08 | gonkulator | scanline: hair treatment! |
| 02:14.09 | scanline | moop! |
| 02:14.13 | gonkulator | fop! |
| 02:14.16 | scanline | moop! |
| 02:14.19 | gonkulator | or what was that... |
| 02:14.23 | gonkulator | lol |
| 02:15.41 | lalo | scanline: I want the textbox to send an event when it has been edited, but only after edition "settled down", so that clients can update observers |
| 02:16.09 | scanline | hmm |
| 02:16.25 | lalo | I know how to code it (piggybacked on the cursor flashing timer) but I wanted to ask you, 1st, if you agree :-P |
| 02:16.28 | scanline | well, you could set a timer whenever they press a key, then when that timer fires send the event |
| 02:16.33 | lalo | and 2nd, about the logic you're using to number events |
| 02:16.41 | scanline | I'm not sure if I agree though... |
| 02:16.49 | scanline | it's adding latency on purpose |
| 02:17.05 | lalo | latency? how so? |
| 02:17.28 | scanline | the client only gets an event after the timer expires, so it won't see changes in real time |
| 02:17.47 | lalo | yes - this avoids protocol latency |
| 02:18.00 | lalo | the idea is that if you go in a typing spree, the client won't get the event for *each* key |
| 02:18.08 | lalo | just when you pause a bit |
| 02:18.20 | scanline | guess it's fine for now, I just want to have more capaple observers in 2.0 :) |
| 02:18.28 | lalo | of course. |
| 02:18.53 | lalo | ok, WE_CHANGED? or WE_EDITED? |
| 02:19.04 | scanline | changed is good |
| 02:19.41 | *** join/#picogui merlin262 (~andrew@crtntx1-ar1-4-60-243-225.crtntx1.dsl-verizon.net) |
| 02:19.57 | lalo | so |
| 02:20.24 | lalo | there is some kaballah in numbering event codes, right? |
| 02:20.26 | njs | observers need more detailed messages than "something changed", of course :-) |
| 02:20.58 | scanline | yes, and more detailed ways of specifying when they care |
| 02:21.08 | scanline | lalo: a bit, yes :) |
| 02:21.43 | scanline | lalo: start with the PG_EVENTCODING_* constant you want to use to encode the event, then add to that until the number is unique |
| 02:22.07 | scanline | non-widget events are also or'ed with 0x1000, but that's not important for this |
| 02:23.04 | lalo | if I get it right, WE_CHANGED would be 0x005, unless you think it's a good idea to send the data that was typed |
| 02:23.37 | scanline | that's fine |
| 02:23.47 | scanline | for this simple of an observer there's no reason to send anything more |
| 02:24.56 | lalo | my opinion too |
| 02:28.01 | scanline | hmm... less uses a "reverse linefeed" code to scroll backwards :) |
| 02:28.39 | gonkulator | this RTD strike fecking blows |
| 02:28.57 | lalo | now, do I go hack nifty or should I try to find out why pgserver doesn't want to run in the vr3? |
| 02:29.12 | lalo | I'm beginning to feel pgserver does this everytime I compile a romdisk :-/ |
| 02:36.40 | scanline | lalo: I'm thinking we release 0.45 when the terminal works |
| 02:37.31 | third | Don't feel bad, lalo! I can't even get my apps to compile. |
| 02:39.11 | lalo | scanline: somehow I was expecting you'd do that :-) |
| 02:39.57 | lalo | I considering naming this flyingcircus release "0.4pre", since it has python 2.3a2, ZODB4a1, and you could describe this picogui as 0.45pre |
| 02:40.14 | lalo | it's an all-alpha release |
| 02:40.22 | scanline | hehe |
| 02:40.47 | scanline | well, less seems to work now |
| 02:40.48 | lalo | yay, nifty buffers now do the whole observer thing... this was less work than I expected |
| 02:41.13 | scanline | what are you adding? modified indicator? |
| 02:41.18 | lalo | I figure I could implement remote frames via tcp/ip |
| 02:41.40 | njs | So if you have the same buffer open in two windows, and type in one, does the observer hack mean that updates in the other window lag? |
| 02:41.52 | lalo | not yet, but it's in the todo, and, well, I guess I could just go and do it now :-) |
| 02:41.59 | lalo | njs: yes, that |
| 02:42.22 | lalo | the update only happens when you stop typing |
| 02:42.26 | scanline | not an easy thing to fix in the current architecture, but in 2.0 it will be as simple as attaching two textboxen to the same string |
| 02:43.42 | scanline | it will be spiffy :) |
| 02:43.43 | file | Goodnight everyone. |
| 02:43.46 | scanline | bye file |
| 02:44.10 | njs | you sound just like the smarter newbies on #fresco, when they start grokking CORBA :-) |
| 02:44.11 | lalo | bye file |
| 02:44.47 | scanline | njs: thanks, I think.. |
| 02:45.22 | njs | scanline: heh. just the bright-eyed-ness :-) |
| 02:45.28 | scanline | :) |
| 02:45.42 | scanline | yay for vapourware! |
| 02:48.58 | scanline | whee |
| 02:49.18 | scanline | http://old.picogui.org/download/pterm-less.png |
| 02:49.59 | gonkulator | you can call it "picogroupi" |
| 02:50.08 | scanline | ? |
| 02:51.10 | lalo | ok, modified indicator done |
| 03:09.14 | third | I can't get the caption to work with this command: pgserver --xres=640 --yres=480 '--video-sdl.caption=Welcome to PicoGUI!' What am I doing wrong? |
| 03:14.41 | gonkulator | look at the wiki |
| 03:14.51 | lalo | hey |
| 03:15.02 | lalo | pgserver *is* working after all :-D |
| 03:15.07 | lalo | just took a bit |
| 03:16.08 | lalo | but I have no pgboard |
| 03:19.30 | lalo | whoa, I don't have pppd installed on my gentoo |
| 03:19.54 | gonkulator | lalo: how dare you! |
| 03:20.04 | gonkulator | :) |
| 03:24.15 | third | That didn't work either, gonkulator. |
| 03:25.12 | gonkulator | I know the wiki is kinda flakey, gotta be patient with it |
| 03:25.45 | gonkulator | for whatever reason, I seem to remember specifying the resolution in the "640x480" format |
| 03:26.53 | scanline | third: sdlfb or sdlgl, not just sdl |
| 03:27.15 | scanline | and it's "-m 640x480" |
| 03:27.36 | scanline | gonkulator: the wiki isn't flaky any more, thanks to lalo.. it's just mostly empty ;) |
| 03:27.41 | gonkulator | oh yeah! |
| 03:28.24 | scanline | farrand... |
| 03:28.32 | gonkulator | oops |
| 03:28.36 | gonkulator | s/fer/far/ |
| 03:29.07 | gonkulator | main ingredients: cat food, shampoo, peanut butter |
| 03:29.29 | third | Hold on. |
| 03:29.39 | gonkulator | hold on to what? |
| 03:30.08 | gonkulator | I'll keep, holding on |
| 03:30.37 | third | I can't get captions out of ANY of those commands. |
| 03:31.07 | third | Here's the last command I used: pgserver -v sdlgl -m 640x480 '--video-sdl.caption=Welcome to PicoGUI!' |
| 03:31.20 | third | LOL!! |
| 03:31.22 | scanline | third: sdlfb or sdlgl, not just sdl |
| 03:31.54 | third | I tried both sdlfb and sdlgl. |
| 03:31.57 | scanline | and the "-m 640x480" won't have any effect, since that's the default resolution for all the sdl drivers |
| 03:32.06 | scanline | third: well first, what driver are you using? |
| 03:32.37 | third | I'm using the sdlgl driver. |
| 03:32.49 | third | pgserver -v sdlgl -m 640x480 '--video-sdl.caption=Welcome to PicoGUI!' |
| 03:32.53 | scanline | oh, right.. |
| 03:33.00 | gonkulator | ~lart me |
| 03:33.27 | third | Mabey pgserver only likes you. LOL!! |
| 03:33.33 | scanline | --video-sdl.caption=Welcome to PicoGUI!' |
| 03:33.34 | scanline | err |
| 03:33.36 | scanline | --video-sdl.caption=Welcome to PicoGUI! |
| 03:33.38 | scanline | gah! |
| 03:33.55 | scanline | "--video-sdlgl.caption=Welcome to PicoGUI!" should work |
| 03:34.06 | scanline | gonkulator: yes |
| 03:34.30 | gonkulator | it looks about half as bad as scanline's toe |
| 03:34.45 | gonkulator | er, did |
| 03:35.13 | scanline | third: I just ran "./pgserver -vsdlgl '--video-sdlgl.caption=Welcome to PicoGUI!'" to verify.. it works fine |
| 03:36.25 | lalo | cute |
| 03:36.40 | lalo | scanline: I can segfault pgserver by loading something big enough in a field widget |
| 03:36.57 | lalo | found that accidentally when I tried "print globals()" in nifty :-P |
| 03:37.02 | scanline | hmm.. where's the segfault? |
| 03:37.35 | third | Now it works! |
| 03:37.41 | lalo | I tried gdb, and it says it's something about drawing |
| 03:37.43 | third | I don't know what I was doing wrong all this time! |
| 03:37.52 | lalo | I'll check the backtrace for you in a minute |
| 03:37.55 | scanline | k |
| 03:38.39 | lalo | probably it's trying to resize itself so that the text fits, and there is no space? |
| 03:39.02 | scanline | that shouldn't cause a segfault |
| 03:39.17 | lalo | I typed "make install" and this stupid makefile decided it would be cool to recompile everything :-/ so you'll have to wait a few minutes |
| 03:40.12 | scanline | haha |
| 03:49.05 | third | Whenever I try to make my apps, I get this: ../libtool: -e: command not found |
| 03:49.05 | third | <PROTECTED> |
| 03:52.06 | lalo | scanline: where can I flood? :-) |
| 03:52.14 | lalo | want a query? |
| 03:52.54 | lalo | short story: paragraph_scroll_to_cursor() |
| 03:55.48 | gonkulator | scanline: will the place with pool tables be open? |
| 04:03.47 | scanline | lalo: ah, that POS... it needs to be rewritten anyway to fix the scrolling |
| 04:03.57 | scanline | gonkulator: doubtful |
| 04:04.02 | scanline | gonkulator: but I'm not sure |
| 04:04.12 | *** join/#picogui third ([lImzcWcrz@adsl-65-66-56-23.dsl.stlsmo.swbell.net) |
| 04:05.27 | gonkulator | scanline: okey dokey |
| 04:06.14 | third | The funniest thing just happened. I launched pgserver in fullscreen mode! I couldn't get out, so I had to logon to another tty to shut it off. When I did, my X session froze, so I had to close the whole thing. |
| 04:06.21 | third | LOL!! |
| 04:06.34 | gonkulator | ctrl-alt-slash |
| 04:07.31 | third | What does that do, gonkulator? |
| 04:07.37 | gonkulator | it kills pgserver |
| 04:07.46 | third | Ahhhhhhhhhh!!!!!!! |
| 04:08.21 | third | :-) |
| 04:09.48 | *** join/#picogui merlin_ (~andrew@crtntx1-ar1-4-60-243-225.crtntx1.dsl-verizon.net) |
| 04:15.57 | third | Nooooooooo, don't go, gonkulator!!!! :( |
| 04:17.37 | scanline | lalo: The headings on picogui.org are really huge... the CSS uses dtml-headingSize1, but I can't find what sets that |
| 04:23.06 | lalo | scanline: the stylesheet_properties |
| 04:23.19 | lalo | I made the headings big on purpose, tough |
| 04:23.23 | scanline | ah |
| 04:23.47 | scanline | I'll leave them alone then |
| 04:23.49 | lalo | it's for the benefit of the wiki, because it selects something from h3 to h6 depending on nesting level and I wanted those to look different from each other |
| 04:24.05 | lalo | so I set h1 and h2 to enormous and it goes down progressively |
| 04:30.35 | lalo | why is char posted before keydown? |
| 04:31.32 | scanline | it's not specified whether char or keydown is sent first, so it's up to the driver |
| 04:32.42 | lalo | ic |
| 04:43.32 | *** join/#picogui jimlay_ (~jimlay@imtgon.nibandit.com) |
| 05:21.06 | lalo[out] | after another rewarding night of text editor hacking, it's time to go home :-) |
| 05:22.32 | scanline | bye lalo |
| 05:41.19 | *** join/#picogui third ([Nl16HAmLq@adsl-65-65-201-68.dsl.stlsmo.swbell.net) |
| 05:52.42 | third | To compile applications in /picogui/apps, do I run make there, or go inside each sub directory and run make for each one? |
| 05:52.51 | scanline | you can do either |
| 05:55.52 | third | I've tried both, but I always end up with this: ../libtool: -e: command not found |
| 05:56.17 | third | Is there something I didn't do? |
| 05:56.21 | captain_proton | scanline: fixed bug(s) yet? |
| 06:09.40 | lalo[out] | hmm |
| 06:09.43 | lalo[out] | it's not my vr3 |
| 06:09.50 | lalo[out] | there's something wrong with pgboard |
| 06:10.24 | lalo[out] | it happens on my pc too, it just doesn't display anything |
| 06:11.01 | third | Yes, everything stops at pgboard with me too. |
| 06:25.32 | third | So far, the only thing that might remotely make sense to me, is that there's something going on with this line in the make file| sed -e 's/^\\$$//' -e '/^$$/ d' -e '/:$$/ d' -e 's/$$/ :/' \: |
| 06:31.37 | third | If any of you compiled any apps, how did you do it? |
| 06:48.12 | lalo[out] | usually I do "make" in apps and it works |
| 06:48.20 | lalo[out] | but it's been a while since I did it |
| 06:51.38 | third | It simply doesn't work for me. It's really frustrating me. |
| 06:51.53 | lalo[out] | well |
| 06:51.53 | third | What distro are you running, lalo[out]? |
| 06:52.03 | lalo[out] | go in the apps you want and try them individually |
| 06:52.13 | njs | third: are you using CVS? |
| 06:52.20 | lalo[out] | I'm running gentoo now... mostly because scanline and the guys convinced me to :-P |
| 06:52.26 | third | I've tried both methods. |
| 06:52.39 | lalo[out] | and some apps compile? |
| 06:52.49 | third | I don't know if it's the LATEST. I downloaded it last night, though. |
| 06:53.35 | third | None of the apps have compiled for me. |
| 06:53.49 | njs | third: because if you are, you might want to check your versions of autotools, libtool (unless that's included in the tree), etc. |
| 06:54.22 | third | I'm sorry, I think uspread compiled. |
| 06:55.27 | lalo[out] | did cli_c compile successfully? |
| 06:57.09 | third | Yes, cli_c seems to have compiled sucessfully. |
| 06:58.11 | lalo[out] | let's try a simple app |
| 06:58.44 | lalo[out] | what about, hmm, connectfour |
| 06:58.54 | lalo[out] | what goes wrong when you try to compile it? |
| 07:00.54 | third | Hold on. |
| 07:01.24 | third | /bin/sh ../libtool --mode=link gcc -o connectfour connectfour.o rules.o ai.o ai1.o ai2.o ai3.o ai4.o ai5.o ai6.o ai10.o -lpgui -lutil |
| 07:01.25 | third | ../libtool: s%^.*/%: No such file or directory |
| 07:01.53 | third | I KNOW I have libtool. |
| 07:05.41 | njs | third: for things like libtool, "having them" is generally not nearly so important as "having exactly the same version of them as the developers use" |
| 07:09.27 | third | What version is used with picogui? |
| 07:10.55 | lalo[out] | looks like you don't have sed |
| 07:11.05 | third | I'm using: (GNU libtool) 1.4.3 (1.922.2.110 2002/10/23 01:39:54) |
| 07:11.20 | lalo[out] | (sorry for the delay, was digging sources to see how this could happen) |
| 07:12.35 | third | Is it possible for one to do a man on sed without having it? If not, then I have it. |
| 07:13.05 | lalo[out] | type 'sed' in the command line and see what happens :-P |
| 07:13.20 | lalo[out] | if you have it, it should display a pageful of help |
| 07:13.22 | third | Yes, I have it. |
| 07:14.47 | lalo[out] | did you run autogen.sh? |
| 07:14.54 | lalo[out] | somehow it seems to have missed your sed |
| 07:17.26 | third | I did in the /apps directory, but the sub directories don't have autogen.sh. |
| 07:18.37 | lalo[out] | np |
| 07:18.42 | lalo[out] | the one in apps runs the others |
| 07:19.28 | lalo[out] | did it generate a shell script named libtool in apps? |
| 07:19.37 | lalo[out] | check what's in line 338 |
| 07:20.05 | third | Let me see. |
| 07:20.56 | third | Yes, it did. |
| 07:21.58 | third | progname=`$echo "$0" | ${SED} 's%^.*/%'` |
| 07:22.03 | lalo[out] | aha. |
| 07:22.31 | lalo[out] | perhaps I should delete mine and generate it again :-P |
| 07:22.48 | third | That's line 338 of the libtool script. |
| 07:22.52 | lalo[out] | right |
| 07:23.06 | lalo[out] | it's like mine, but mine uses 'sed' instead of '${SED}' |
| 07:23.46 | third | So, what will happen, if I change that line to look like yours? |
| 07:24.19 | lalo[out] | hopefully, it would work |
| 07:24.32 | lalo[out] | what is your autoconf version? |
| 07:24.48 | third | I have one more question before I change that line. |
| 07:25.33 | third | Make that two questions. |
| 07:25.56 | third | The first question was inspired by your last question. |
| 07:26.47 | third | How do you know what autoconf version you have? |
| 07:27.28 | lalo[out] | there are some ways |
| 07:27.35 | lalo[out] | the way I used was to ask my packaging system |
| 07:27.42 | lalo[out] | what is your distro? |
| 07:28.04 | third | RedHat 7.3. |
| 07:29.23 | third | My second question was, going to be about the syntax for running an app, such as uspread. |
| 07:30.39 | third | My syntax looks like this: pgserver -vsdlgl '--session.uspread' But I get nothing but a blank pgserver from tht. |
| 07:30.40 | third | that |
| 07:31.55 | lalo[out] | that's correct |
| 07:31.56 | third | x2pgui just compiled, when I went in to that directory to do a make on it. |
| 07:32.02 | lalo[out] | that's what you're supposed to get :-) |
| 07:32.16 | lalo[out] | ah, sorry, I missed the --session |
| 07:32.36 | lalo[out] | it's something like, --session=/usr/local/bin/uspread |
| 07:32.37 | third | ??? I thought uspread was a spreadsheet program. |
| 07:32.55 | third | I see. |
| 07:33.01 | third | Hold on. |
| 07:34.14 | lalo[out] | it is supposed to be, but it isn't useful yet |
| 07:35.23 | third | Well, the good news, is that I got it to even run at all! :-) |
| 07:37.08 | lalo[out] | yup :-) |
| 07:37.33 | lalo[out] | there aren't may apps that actually do something |
| 07:37.40 | third | What does x2pgui do? |
| 07:38.24 | lalo[out] | pgedit is what you'd expect from a "notepad"-like editor, and pterm is more or less complete; the games do what they promise, and then there is nifty |
| 07:39.49 | lalo[out] | x2pgui: It will allow an X display and a pgserver to act as if they were two displays connected to one machine. When you move your mouse pointer off the screen in a direction of your choosing, the pointer will appear on the other screen instead. |
| 07:39.53 | lalo[out] | (from the README) |
| 07:39.56 | lalo[out] | I never tried it |
| 07:41.31 | third | Is see. |
| 07:42.22 | third | I |
| 07:42.49 | lalo[out] | hmm. picosm (session manager - a login box, xdm-type thingie) works |
| 07:42.59 | third | What should my line 338 look like? |
| 07:43.09 | lalo[out] | so do pgboard and pqw - or at least they used to, pgboard seems to be broken right now |
| 07:43.36 | lalo[out] | mine is: |
| 07:43.38 | lalo[out] | progname=`$echo "$0" | sed 's%^.*/%%'` |
| 07:46.00 | third | Ok, I made the change, but I'm still coming up with: ../libtool: -e: command not found |
| 07:48.13 | lalo[out] | there are other instances of the same problem |
| 07:48.18 | lalo[out] | tell you what |
| 07:48.29 | lalo[out] | undo this change, let's fix this right |
| 07:48.58 | third | Ok. |
| 07:49.02 | lalo[out] | look near the top of the file (use your editor's search feature) for a line that looks like that: SED="(something)" |
| 07:50.21 | third | The first line I came accross was: Xsed="${SED}"' -e 1s/^X//' |
| 07:51.37 | lalo[out] | not this one |
| 07:51.40 | lalo[out] | see if there is another |
| 07:55.29 | lalo[out] | if not |
| 07:55.42 | lalo[out] | just add it: SED="sed" |
| 07:56.25 | third | Yes, there's another. |
| 07:57.06 | third | I count three in total. |
| 07:57.16 | lalo[out] | eep |
| 07:57.20 | lalo[out] | what do they look like? |
| 08:01.44 | third | 1) Xsed="sed -e s/^X//" |
| 08:02.08 | third | 2) Xsed="${SED}"' -e 1s/^X//' |
| 08:02.27 | third | 3) Xsed="${SED}"' -e 1s/^X//' |
| 08:02.50 | lalo | but not Xsed |
| 08:02.56 | lalo | it has to be SED=somethign |
| 08:04.09 | third | The first one is on line 30, the second on line 356, and the third on line 3931. |
| 08:18.33 | *** join/#picogui Soopaman (~soopaman@h24-66-55-163.wp.shawcable.net) |
| 08:19.26 | Soopaman | evening guys |
| 08:19.45 | Soopaman | are any of you solely using nix on apple laptops? |
| 08:26.44 | Soopaman | anyone here a mac+linux user |
| 08:38.59 | third | Not me, but I've seen it done. I just happen to have a copy of yellow dog, from the last linux meeting I attended on Sunday. |
| 09:27.30 | lalo | holy whatever, scanline - I thought you were sleeping! |
| 09:27.45 | scanline | oh |
| 09:27.46 | scanline | hi lalo |
| 09:27.48 | scanline | I was playing risk |
| 09:28.04 | lalo | :-) |
| 09:28.27 | lalo | I'm testing an ebuild |
| 09:28.35 | lalo | and you committed stuff to the terminal |
| 09:29.22 | scanline | yeah, I somehow broke terminal_vt102.c right before I committed it.. not sure how |
| 09:29.25 | scanline | it's fixed now |
| 09:29.43 | scanline | hi nemo |
| 09:29.57 | nemo | g'mornings |
| 09:30.22 | lalo | hey nemo |
| 09:30.36 | captain_proton | scanline: do you have a dynamically-set title field for the terminal? |
| 09:30.40 | nemo | I'm not really here... I'm about to go get dinner ;) |
| 09:30.50 | scanline | lalo: hmm... the palette modification and mouse reporting should be spiffy for a new xchat-picogui :) |
| 09:30.55 | scanline | once they're implemented of course |
| 09:31.05 | lalo | pallete modification? |
| 09:31.12 | scanline | captain_proton: not yet, haven't implemented any of the xterm-specific escapes like title and mouse reporting |
| 09:31.22 | nemo | remind me later (about 15 hours time) to tell you guys about my tetris logging stuff though. ;) |
| 09:31.27 | scanline | lalo: yep, the linux console defined a code for setting the RGB values of any palette entry |
| 09:31.32 | lalo | ah, yes |
| 09:31.43 | scanline | lalo: most X-based terminal emulators don't support it, but it could be really useful, so I will |
| 09:31.59 | scanline | lalo: currently xchat-picogui synthesizes a theme to set the terminal palette, which gets pretty messy |
| 09:32.05 | nemo | greyscale... pastels... different coloured backgrounds... so on |
| 09:32.10 | lalo | damn, there is something terribly borked with rhythmbox - perhaps I should upgrade it |
| 09:32.38 | scanline | hehe.. once I implement mouse reporting, links should run nicely |
| 09:32.43 | nemo | nice |
| 09:33.17 | njs | ew, I always wish I could turn off mouse reporting when using links :-) |
| 09:33.48 | captain_proton | scanline: you could make it really creepy and add a pterm mode to links so it draws images |
| 09:34.21 | scanline | ooh, that would be creepy... and stuff... |
| 09:34.25 | lalo | scanline: rejoice, we have a halfway-working cvs ebuild. |
| 09:34.35 | njs | isn't it w3m that does images in xterm? |
| 09:34.38 | scanline | lalo: cool! |
| 09:34.48 | captain_proton | njs: hm, true |
| 09:34.54 | captain_proton | ok, add pterm support to w3m =) |
| 09:35.05 | scanline | I don't know how it would draw the images, since you can't really position a window over the terminal widget in picogui |
| 09:35.10 | scanline | guess you could set a background image |
| 09:35.31 | njs | scanline: heh, yes, have it paint into the background and leave blank space in the text so the background shows through :-) |
| 09:35.31 | scanline | I need to make the terminal widget handle backgrounds like the textbox widget- i.e. you can use any fillstyle as a background |
| 09:35.51 | lalo | for it to really work, we need to finish the thingie that maps USE settings to profile settings - but that's just a matter of sitting patiently for a few hours and figuring out what depends on what |
| 09:35.55 | nemo | scanline: http://www.nut.house.cx/~nemo/extras/settermcol |
| 09:36.02 | scanline | will probably fixify the background support when I make the terminal renderer more efficient |
| 09:36.11 | nemo | ...that's my old (horrible) script to set console "themes" |
| 09:38.53 | scanline | captain_proton: committed, again... I really think it's fixed this time :) |
| 09:39.16 | *** join/#picogui Talez (~talez@talez.arach.net.au) |
| 09:41.39 | captain_proton | ok, no pgserver crash |
| 09:41.46 | captain_proton | now why don't i get a real terminal? |
| 09:41.51 | scanline | good. but the fonts don't work, right? |
| 09:42.00 | captain_proton | i just get a black box |
| 09:42.19 | scanline | that fix prevented celw==0 from crashing it, but there's still something wrong with your fonts that keeps it from working correctly |
| 09:42.39 | scanline | shouldn't change a thing |
| 09:43.01 | captain_proton | i might get a white box instead of a black one |
| 09:43.05 | scanline | try |
| 09:43.06 | scanline | err |
| 09:43.09 | captain_proton | yep |
| 09:43.09 | scanline | try "./pgserver --font-freetype.dump_list" |
| 09:43.47 | scanline | make sure you have at least one fixed width font (":fixed" at the end of the descriptor) |
| 09:44.39 | scanline | err.. not necessarily at the end, anywhere in the descriptor |
| 09:44.43 | captain_proton | quite a few fixed fonts |
| 09:44.53 | scanline | nimbus_mono_l.pfb is probably what you want to be using |
| 09:44.57 | scanline | hmm |
| 09:45.13 | scanline | do you have anything in the [font-freetype] section of ~/.pgserverrc? |
| 09:45.37 | captain_proton | i don't have a .pgserverrc |
| 09:45.41 | captain_proton | i have a giant command line =) |
| 09:45.45 | scanline | ah, fun... |
| 09:45.53 | scanline | what's your command line? |
| 09:46.15 | captain_proton | one sec, i'll prune the theme parts |
| 09:46.24 | captain_proton | pgserver -v x11 --appmgr=managed_rootless --font_engine=freetype --font_freetype.path=/usr/share/fonts/truetype/ |
| 09:46.31 | scanline | you might find a config file to be a little easier to manage :) |
| 09:46.41 | captain_proton | eh - this works for now |
| 09:47.08 | scanline | hmm, that should work... maybe one of the fonts you have in /usr/share/fonts/truetype is confusing it. Try pointing it to the 'fonts' directory in picogui CVS |
| 09:48.07 | captain_proton | no difference |
| 09:49.25 | scanline | try adding --font-freetype.default_fixed=:14:bold |
| 09:49.47 | captain_proton | nope |
| 09:50.37 | captain_proton | hm? |
| 09:50.51 | scanline | open it in gdb, set a breakpoint at terminal_frontend.c:116 and run it |
| 09:50.57 | scanline | print DATA->celw |
| 09:51.06 | scanline | err.. |
| 09:51.11 | scanline | gdb can't expand macros :) |
| 09:51.45 | scanline | that would be ((struct terminaldata *)(self->subclasses[0].data))->celw |
| 09:52.40 | captain_proton | gdb is being cranky |
| 09:53.22 | njs | scanline: picogui is single-thread, I assume? |
| 09:53.31 | scanline | njs: currently yes |
| 09:53.52 | scanline | Long ago I tried making it multithreaded, but it just made things more complicated with no real benefits |
| 09:54.11 | scanline | the 2.0 architecture will make multithreading optional at compile-time |
| 09:54.43 | njs | so it just runs everything from an event loop, and you don't have any problems with operations taking too long? |
| 09:54.51 | scanline | njs: right |
| 09:55.01 | njs | nod |
| 09:55.04 | njs | just curious |
| 09:55.18 | scanline | captain_proton: after you get to that point, print ((struct freetype_fontdesc *)fd->data)->face |
| 09:55.24 | scanline | err.. dereference that |
| 09:55.42 | captain_proton | oof, i think i need to unselect libpgserver |
| 09:56.05 | scanline | ah... if you're using libpgserver, your 'pgserver' binary isn't a binary, it's a shell script that libtool generates |
| 09:57.07 | njs | I have a really clever idea how to implement an architecture where you have a redraw thread that continuously traverses the scene graph and a mutator thread that modifies the scene graph per clients's requests without contention between the two threads, but I have yet to come up with any situation where this architecture is one you'd actually want to implement :-) |
| 09:57.51 | scanline | njs: that's not too much different from pg2... |
| 09:58.05 | njs | (well, it's possible that your redraw traversal could block on the graphics GPU, in which case remaining able to service requests would be useful.) |
| 09:58.16 | scanline | pg2 will have a separate thread/process/module that observes the scene graph and generates commands for the video driver |
| 09:58.45 | njs | mm. not sure that's really comparable. |
| 09:58.48 | scanline | it also makes sense if you're sending graphics over the network, as in remote X or VNC |
| 09:58.58 | njs | nod |
| 09:59.47 | njs | once your redraw thing has observed a change in the scene graph, it still has to go traverse it, and you have to have some way to make sure that traversals and further mutations don't bump into each other. |
| 10:00.49 | captain_proton | (gdb) print ((struct terminaldata *)(self->subclasses[0].data))->celw |
| 10:00.50 | captain_proton | $1 = 0 |
| 10:01.18 | njs | one way is to have the redraw thread keep its own private copy of the scene graph, which it applies mutations to as it gets notifications, and periodically traverses (queueing mutations in the mean time). But that's really a single-threaded model. |
| 10:01.22 | scanline | print *((struct freetype_fontdesc *)fd->data)->face |
| 10:01.31 | captain_proton | (gdb) print *(((struct freetype_fontdesc *)fd->data)->face) |
| 10:01.32 | captain_proton | $3 = {file_path = 0x80b9cb0 "/usr/share/fonts/truetype/85855.fon", relative_path = 0x80b9cc1 "truetype/85855.fon", fs = {name = 0x80a8b60 "Terminal", style = 131073, |
| 10:01.32 | captain_proton | <PROTECTED> |
| 10:01.41 | scanline | njs: that's a lot like how the separate widget graph and scene graph will interact |
| 10:01.55 | scanline | captain_proton: gah... |
| 10:02.09 | scanline | captain_proton: run it again using the fonts that came with picogui |
| 10:02.09 | captain_proton | scanline: you don't filter for *.ttf? ;) |
| 10:02.09 | njs | scanline: nod. |
| 10:02.18 | scanline | captain_proton: no, because freetype can handle things other than ttf |
| 10:02.30 | scanline | captain_proton: I routinely use it with Type1 and BDF fonts |
| 10:02.52 | Soopaman | http://www.kuro5hin.org/story/2003/3/21/141438/512 |
| 10:02.53 | njs | scanline: I think the way the separate widget graph/scene graph concept fits together with what I'm talking about is, if you have a widget graph/scene graph split, what I'm talking about is the scene graph management, which happens to have only a single client. |
| 10:02.59 | scanline | the "gah" was because that's a windows font |
| 10:03.14 | njs | (that client being the widget graph module, which happens to act as a proxy for all the user-level clients.) |
| 10:03.27 | captain_proton | arf |
| 10:03.36 | captain_proton | run --font_engine=freetype --font_freetype.path=/home/jupiter/projects/picogui-old/fonts <-- correct? |
| 10:03.38 | scanline | doesn't have to only have a single client :) |
| 10:03.47 | scanline | captain_proton: sure |
| 10:03.48 | captain_proton | because its still trying to load /usr/share/fonts/truetype for some reason |
| 10:04.00 | scanline | hmm |
| 10:04.02 | scanline | pj |
| 10:04.03 | scanline | err, oh |
| 10:04.09 | scanline | dash, not underscore in font-freetype |
| 10:05.45 | captain_proton | (gdb) print ((struct terminaldata *)(self->subclasses[0].data))->celw |
| 10:05.46 | captain_proton | $1 = 5 |
| 10:05.46 | captain_proton | (gdb) print *(((struct freetype_fontdesc *)fd->data)->face) |
| 10:05.46 | captain_proton | $2 = {file_path = 0x80a42f8 "/home/jupiter/projects/picogui-old/fonts/clean_5x8.pcf", relative_path = 0x80a4321 "clean_5x8.pcf", fs = {name = 0x80a42e8 "Clean", style = 1, |
| 10:05.46 | captain_proton | <PROTECTED> |
| 10:05.53 | scanline | good |
| 10:05.55 | scanline | it should work now |
| 10:06.06 | lalo | ok... DevGirl is threatening bloody murder on the phone :-P cya tomorrow |
| 10:06.13 | njs | re: the X fork, http://www.advogato.org/person/freetype/diary.html?start=10 is worth reading (or pointing other people at) |
| 10:06.16 | scanline | bye lalo :) |
| 10:06.27 | zak | i am so tired |
| 10:06.32 | scanline | nemo: thanks for that link, I like the kernel's palette :) |
| 10:06.43 | scanline | didn't think to look there for a good default palette |
| 10:07.36 | captain_proton | scanline: still not getting fonts |
| 10:07.45 | scanline | >:( |
| 10:07.47 | njs | that kuro5hin article sucks :-) are the comments better? |
| 10:10.35 | scanline | ooh, vibrant colors |
| 10:11.19 | captain_proton | hrmph |
| 10:11.37 | captain_proton | it doesn't seem to be allocating a pty or forking |
| 10:11.57 | scanline | that's a bit bizarre |
| 10:12.24 | captain_proton | pterm works fine, but my python one doesn't |
| 10:12.29 | scanline | ah |
| 10:12.43 | scanline | if you want some python code for a picogui terminal, you could copy the one from jetstream |
| 10:18.45 | captain_proton | 'night scanline |
| 10:18.49 | scanline | good night |
| 10:19.17 | *** join/#picogui scanlime (~micah@aden2-42-dhcp.resnet.Colorado.EDU) |
| 10:19.37 | scanlime | wow, irssi seems to run alright in pterm |
| 10:30.02 | *** join/#picogui LordVan (~lordvan@62.47.64.183) |
| 10:30.15 | *** part/#picogui LordVan (~lordvan@62.47.64.183) |
| 11:02.45 | scanline | whee... |
| 11:02.49 | scanline | captain-seizure running in pterm |
| 11:04.11 | scanline | and hogging all of the CPU... |
| 11:06.37 | njs | Does picogui worry about palletized color modes? |
| 11:07.11 | scanline | a little.. it can handle palettes, but only statically- the driver gets to assign colors, not the apps |
| 11:07.42 | scanline | dynamic palettes are really only useful on 8bpp devices, and there are so few of those around these days that nobody bothered to do more than add support for arbitrary static palletes |
| 11:07.53 | njs | nod |
| 11:09.01 | njs | this paper is talking about some of the headaches involved in X's palette support, and I was curious whether such things were ignorable these days, and I figured that if anyone would still care about them, it'd be you guys :-) |
| 11:09.23 | scanline | hehe |
| 11:09.41 | scanline | well, most embedded devices either use true color (or close enough, like 12 or 16 bit color) or they use grayscale |
| 11:09.49 | scanline | the only exception I can think of is the tuxscreen, which uses 8bpp |
| 11:10.12 | scanline | I usually use a 216-color palette or something similar on it |
| 11:10.22 | njs | nod, seems reasonable |
| 11:10.42 | scanline | palettes do introduce a lot of headaches.. and these days I think nobody cares :) |
| 11:30.20 | scanline | wow, colonel-seizure is small and effective |
| 11:37.03 | *** join/#picogui prae (~prae@sherpadown.net) |
| 11:55.06 | *** join/#picogui prae_ (~prae@sherpadown.net) |
| 12:37.10 | *** join/#picogui Dentoid (dento_3000@h242n1fls35o814.telia.com) |
| 14:00.24 | *** join/#picogui Piete (~abri@61.104.220.136) |
| 14:12.53 | third | Hey scanline, here's what I got to compile so far: flyingtux, gremlin, cdclock, listtest, menutest, offscreen, omnibar-helio, paneldemo, mainMenu, scrctl, scrsaver, themedemo, vidpopup, uspread, pgmerlin, and customtheme. |
| 14:13.07 | third | compiled |
| 14:45.45 | *** join/#picogui Oktal (~mat@pc1-rdng3-5-cust199.winn.cable.ntl.com) |
| 17:26.00 | *** join/#picogui Oktal (mat@pc1-rdng3-5-cust199.winn.cable.ntl.com) |
| 17:26.54 | *** join/#picogui Oktal (mat@pc1-rdng3-5-cust199.winn.cable.ntl.com) |
| 17:33.54 | *** join/#picogui prae (~prae@sherpadown.net) |
| 17:52.24 | *** join/#picogui Oktal (mat@pc1-rdng3-5-cust199.winn.cable.ntl.com) |
| 18:09.55 | *** join/#picogui kergoth (~kergoth@dsl081-228-056.chi1.dsl.speakeasy.net) |
| 18:18.35 | *** join/#picogui d (~brandon@h-66-167-168-251.DNVTCO56.covad.net) |
| 18:36.42 | *** join/#picogui Oktal (~mat@pc1-rdng3-5-cust199.winn.cable.ntl.com) |
| 18:45.46 | Soopaman | scanline, are you around? |
| 18:47.38 | file | scanline has been idle 7hrs 15mins 20secs |
| 18:48.06 | Soopaman | heh |
| 18:52.48 | *** join/#picogui kidder (~s@h24-65-171-188.gv.shawcable.net) |
| 18:53.35 | file | kidder: hey |
| 19:01.31 | kidder | hello |
| 20:42.32 | *** join/#picogui file (~jcolp@mctn1-3683.nb.aliant.net) |
| 21:13.14 | captain_proton | scanline: is there any way i can associate arbitrary data with a widget? |
| 21:13.22 | *** join/#picogui d (~brandon@h-66-167-168-251.DNVTCO56.covad.net) |
| 21:14.00 | scanline | captain_proton: in python you can just set properties on the widget |
| 21:14.15 | scanline | mywidget.arbitraryName = 42 |
| 21:15.12 | captain_proton | whats the python syntax to get the size of an array again? |
| 21:16.34 | scanline | len(array) |
| 21:17.37 | scanline | Apparently I had swapped red and green in two different places, so normally it looked ok, but when you tried to load a custom palette they would be swapped |
| 21:21.03 | *** join/#picogui scanlime (~micah@aden2-42-dhcp.resnet.Colorado.EDU) |
| 21:21.22 | scanline | scanlime: poing |
| 21:21.28 | scanlime | scanline: spiffy |
| 21:25.06 | scanlime | handling what? |
| 21:25.25 | captain_proton | terminal stuffs |
| 21:25.37 | scanline | eh.. more specifically? |
| 21:25.52 | captain_proton | lots of terminal widgets in a single application |
| 21:26.20 | scanline | a class that encapsulates the terminal widget, tab widget, and the pseudoterminal, and a list of such classes? |
| 21:27.47 | captain_proton | perhaps |
| 21:31.49 | captain_proton | all this python is going to be dangerous |
| 21:31.57 | captain_proton | i'm going to start putting colons after my if statements in C++ |
| 21:33.13 | scanline | :) |
| 21:37.36 | captain_proton | ...wow |
| 21:37.43 | captain_proton | ptys in python are so much easier than in c |
| 21:49.14 | scanline | indeed |
| 21:49.55 | scanline | pterm's default color scheme is much better now |
| 21:50.57 | captain_proton | hmm, getting an invalid parent |
| 21:51.00 | captain_proton | but i shouldn't be |
| 21:52.43 | captain_proton | scanline: care to tell me what obviousness i'm missing? |
| 21:53.45 | Dentoid | Ooh. Gay pr0n imminent. |
| 21:53.51 | Dentoid | Ehm. |
| 22:03.45 | captain_proton | ahem |
| 22:05.15 | captain_proton | scanline: fix faster1 |
| 22:06.51 | Dentoid | It's just all undocumented features. :) |
| 22:06.58 | scanline | right! |
| 22:08.19 | *** join/#picogui file (file@mctn1-0092.nb.aliant.net) |
| 22:17.43 | nemo | scanline: you *like* the kernel colour scheme? even the yellow=brown and too-dark blue? |
| 22:18.00 | scanline | nemo: I fixed the brown |
| 22:18.12 | scanline | it's a lot better than the default I was using :) |
| 22:18.17 | nemo | ahh :) |
| 22:18.38 | scanline | but now picogui's terminal supports the palette setting escape, so settermcol works on it |
| 22:18.45 | scanline | well, with some minor modification... |
| 22:19.06 | nemo | *nodS* v. cool :) |
| 22:19.17 | scanline | settermcol sends escape codes without colors following them for colors that the current theme doesn't define |
| 22:19.30 | scanline | I kludged that by copying it's kernel color scheme and pasting above it calls the theme function |
| 22:19.45 | scanline | this has the side effect of making it set the kernel color scheme when you just run "settermcol help" |
| 22:19.47 | nemo | oh... yeah... settermcol is so kludgy |
| 22:20.46 | nemo | hmm... that means you can't merge two themes so easily... |
| 22:20.57 | scanline | captain_proton: fixed it |
| 22:21.21 | captain_proton | scanline: nifty |
| 22:21.53 | nemo | anyways, I should go wake up and shower |
| 22:22.08 | scanline | it uses addWidget() now, so as not to aggrivate bug #6, and there was a bug in the pty code that was confusing cli_python's event loop |
| 22:35.48 | captain_proton | hmm |
| 22:38.54 | captain_proton | is there a python equivalent to pgCustomizeSelect ? |
| 22:42.10 | scanline | nope |
| 22:42.31 | scanline | I should ask lalo about the best way to implement such a thing... |
| 22:42.42 | captain_proton | should i just loop on eventPoll() ? |
| 22:43.15 | scanline | it's a disgusting solution, but will work for now... just make sure to sleep so it doesn't use all the CPU |
| 22:44.01 | captain_proton | =) |
| 22:49.21 | scanline | time.sleep() takes a floating point argument |
| 22:57.04 | *** join/#picogui Soopaman (~soopaman@h24-66-55-163.wp.shawcable.net) |
| 22:59.08 | captain_proton | err |
| 22:59.10 | captain_proton | why am i doing that |
| 23:03.04 | captain_proton | AttributeError: write |
| 23:03.05 | captain_proton | ? |
| 23:03.28 | scanline | are you trying to call the write() method on a file descriptor? |
| 23:03.39 | captain_proton | no |
| 23:03.41 | captain_proton | on the terminal widget |
| 23:03.45 | scanline | oh |
| 23:03.57 | scanline | I think lalo changed that in the writeto/writecmd patch |
| 23:04.17 | scanline | yeah |
| 23:04.19 | scanline | it's writedata() now |
| 23:04.30 | scanline | err |
| 23:04.43 | captain_proton | AttributeError: writedata |
| 23:04.55 | scanline | it's stream()... but I liked write() better |
| 23:05.33 | captain_proton | woo |
| 23:07.01 | scanline | committed, it's write() now. |
| 23:09.48 | captain_proton | hm, now i get a deprecation warning |
| 23:10.18 | captain_proton | textbox_frontend.c: In function `textbox_trigger': |
| 23:10.19 | captain_proton | textbox_frontend.c:260: warning: `return' with a value, in function returning void |
| 23:10.29 | captain_proton | =) |
| 23:10.43 | captain_proton | gl_init.c: In function `setvbl_gl': |
| 23:10.43 | captain_proton | gl_init.c:139: warning: `return' with a value, in function returning void |
| 23:10.51 | captain_proton | yay for colorgcc |
| 23:11.01 | scanline | ah |
| 23:11.10 | scanline | thanks, I found a few warnings yesterday similar to those |
| 23:13.11 | Oktal | btw i hope to have a working picogui server using crystalspace next weekend |
| 23:13.23 | scanline | spiffy |
| 23:13.40 | captain_proton | ./epterm.py:61: DeprecationWarning: handler <bound method TerminalPage.terminalResizeHandler of <__main__.TerminalPage instance at 0x81cb26c>> expects 2 arguments |
| 23:13.40 | captain_proton | <PROTECTED> |
| 23:13.40 | captain_proton | ? |
| 23:14.36 | scanline | your handler should take three arguments, not two |
| 23:14.52 | captain_proton | <PROTECTED> |
| 23:14.54 | captain_proton | what other argument? |
| 23:15.26 | scanline | hmm |
| 23:15.31 | scanline | that is indeed three |
| 23:18.23 | nemo | scanline: can I grab your adjusted settermcol... I'm thinking I should rewrite it to satisfy the needs of both console and pgterm better :) |
| 23:18.37 | scanline | :) |
| 23:18.39 | scanline | ok |
| 23:19.10 | scanline | I'm thinking though that an improved version of pterm will have a GUi-thingy for changing the palette |
| 23:19.24 | captain_proton | scanline: ok ;) |
| 23:19.46 | nemo | scanline: definately should. *nods* ... but it's always good to be able to do stuff guiless too :) |
| 23:21.06 | scanline | indeed |
| 23:22.22 | nemo | besides, 20nov2001 was the last time I touched that script, if the datestamps of ~/bin/* are anything to go by... |
| 23:24.47 | scanline | captain_proton: wow.. one of those warnings was a potential crash bug in low memory situations :) |
| 23:25.03 | captain_proton | scanline: gee, i guess i'm a good bugfinder =) |
| 23:25.54 | scanline | need to teach you how to use the bug database :P |
| 23:26.01 | captain_proton | haha |
