| 04:13:29 | mibus | Zzzzzz |
| 04:43:57 | mibus | hey colin_werk |
| 04:47:21 | mibus | Zzzzzzz |
| 04:50:26 | colin_werk | Hi mibus |
| 04:51:06 | mibus | how ya going? |
| 04:51:21 | mibus | using gtk2 for any GPE stuff yet? i just ported gpe-appmgr over |
| 04:51:29 | mibus | looks *very* nice on the desktop |
| 04:51:39 | mibus | haven't setup gtk2 for cross-compiling yet so i'll have to wait :( |
| 04:52:05 | colin_werk | mibus: Cool. I have gpe-nmf which is GTK2 only |
| 04:52:37 | colin_werk | We found olirc which is a nice, fairly small IRC client for GTK. |
| 04:53:09 | colin_werk | See scap |
| 04:53:13 | mibus | cool |
| 04:53:27 | colin_werk | I never prorammed in GTK2 though |
| 04:53:35 | mibus | its much the same as gtk1 |
| 04:53:42 | mibus | but with a little less crap in it IMHO |
| 04:53:47 | mibus | and some nice additions |
| 04:53:52 | mibus | like MVC for text-boxes etc. |
| 04:54:44 | colin_werk | MVC? |
| 04:54:50 | mibus | model-view-controller |
| 04:55:00 | mibus | you have the data and the display totally seperate |
| 04:55:11 | colin_werk | Ah, nice. |
| 04:55:36 | mibus | it is, yes ;) |
| 04:55:51 | mibus | it stops having multiple copies of data and synchronising it all the time etc. |
| 04:56:34 | colin_werk | I'm hacking gpe-ownerinfo ATM to show a owner photo. A very small clickable one that links to a bigger one. |
| 04:57:04 | colin_werk | I'd go much faster if I actually knew GTK, or C for that matter :) |
| 04:58:39 | mibus | :D |
| 05:06:16 | mibus | at least you dont have to use gdk-imlib for image loading |
| 05:06:18 | mibus | *shudder* |
| 05:07:11 | colin_werk | Hah! |
| 05:07:25 | colin_werk | I have to. Or at least, I want to, later. |
| 05:07:58 | colin_werk | I want to overlay two images, and gdk-imlib has a compose function. |
| 05:08:27 | colin_werk | The photo and a small triangle or arrow to show that it can be clicked, since I don't want it to look like a button. |
| 05:09:28 | colin_werk | Then I need to scale to two different sizes. |
| 05:10:28 | mibus | why not use gdk-pixbuf!!?? |
| 05:17:23 | colin_werk | Ugh. Yeah. I mean gdk-pixpuf, sorry. |
| 05:20:36 | Jacmet | morning |
| 05:21:40 | mibus | howdy |
| 05:28:03 | colin_werk | Hi Jacmet |
| 05:51:06 | mibus | crap - i just broke my gnome2 install :-( |
| 05:51:24 | mibus | the joys of cvs :D |
| 08:31:44 | pb_ | grr, my screen is playing up again. |
| 09:14:37 | | hmmm... gpe bugs is see gpe bugzilla |
| 09:14:37 | colin_werk | ibot: gpe bugs? |
| 09:14:58 | | bugger all, i dunno, colin_werk |
| 09:14:58 | colin_werk | ibot: gpe buzilla? |
| 09:15:13 | | i think gpe bugzilla is at http://europa.armlinux.org/bugzilla |
| 09:15:13 | colin_werk | ibot: gpe bugzilla? |
| 09:15:30 | | colin_werk: I forgot gpe bugzilla |
| 09:15:30 | colin_werk | ibot: forget gpe bugzilla |
| 09:15:58 | | OK, colin_werk. |
| 09:15:58 | colin_werk | ibot: gpe bugzilla is http://europa.debian.org/bugzilla |
| 09:16:05 | pb_ | ah, good thinking. |
| 09:22:16 | colin_werk | For olirc, I guess we could try to get maintainership on SF to pick up development again |
| 09:22:34 | pb_ | Yeah, that's a thought. |
| 09:22:36 | colin_werk | maintainership for olirc, that is |
| 09:22:41 | pb_ | :-) |
| 09:29:29 | colin_werk | Yann GROSSEL <y.grossel@hexanet.fr> was around in Feb this year |
| 09:32:49 | pb_ | hmm, right. |
| 09:48:18 | pb_ | colin_werk: Do you think gpe-ownerinfo could be made transparent, like gpe-login? |
| 09:52:55 | colin_werk | pb_: transparent, like in "look through"? I never noticed gpe-login was transparent |
| 09:54:18 | pb_ | colin_werk: http://handhelds.org/scap/port.4161.png |
| 09:55:32 | pb_ | ibot, message for mallum: I installed matchbox_0.3.3.20020826_arm.ipk; there seems to be something wrong with the default placement of icons in the dock, see http://handhelds.org/scap/port.4148.png |
| 09:56:27 | pb_ | colin_werk: mallum said he could probably make xkbd a bit transparent. |
| 09:57:03 | colin_werk | pb_: Whee, great! Care to file a bug, telling me what I need to do? |
| 09:57:14 | colin_werk | Ah, and a half-transparent xkbd... yeah. |
| 09:57:21 | pb_ | ok, sure. |
| 09:57:21 | colin_werk | dc would like it. |
| 09:57:48 | pb_ | ha, yes. |
| 09:59:17 | colin_werk | When we select the bg image, we should take care to leave the lower left area free so that it can display the owner photo without distracting the user. see gpeownerinfo in cvs on how it is supposed to be, roughly |
| 10:00:29 | pb_ | Yeah, that makes sense. |
| 10:00:41 | colin_werk | pb_: Oh. Does transparency work on GtkTables? If not, I need to rewrite gpe-ownerinfo. If yes, gpe-appmgr can use it too |
| 10:00:59 | colin_werk | pb_: BTW, mibus told me he ported gpe-appmgr to GTK2 |
| 10:01:00 | pb_ | I can't think of any particular reason why it shouldn't. In fact, gpe-login may even use a table itself. |
| 10:01:13 | pb_ | Yeah, mibus sent me mail about it. Sounds cool. |
| 10:01:16 | colin_werk | drools |
| 10:04:58 | colin_werk | The GTK API docs should list all their functions etc. again in HTML comments/meta tags, with the underscores replaced by spaces, so that Google sees them as separate words. Would help to find the right functions |
| 10:24:13 | pb_ | damn usbnet crashed my machine :-( |
| 10:25:56 | colin_werk | :/ |
| 10:27:47 | pb_ | It's a really weird failure: complete lockup, with the Caps and Scroll Lock leds on the keyboard flashing at about 1Hz. |
| 10:30:55 | pb_ | hi mccarthy |
| 10:30:59 | mccarthy | hello |
| 10:31:10 | mccarthy | I am thinking of releasing the recurring gpe-calendar today |
| 10:31:37 | mccarthy | I want a little pixmap to show which ones recur (and I need to fix the future view with regard to recurrence) |
| 10:31:47 | pb_ | ok. |
| 10:31:54 | mccarthy | pb_: should future view only show the *next* value of a recurring event? |
| 10:32:19 | pb_ | mccarthy: No, I think it should probably show all of them. |
| 10:32:26 | mccarthy | any ideas where to get a small recycle looking pixmap? |
| 10:32:41 | pb_ | "reload" icon from a web browser maybe? |
| 10:32:44 | mccarthy | pb_: but if something recurs *forever*?! |
| 10:33:07 | mccarthy | thats partly why I wanted an icon so we only need to show one maybe |
| 10:33:12 | pb_ | mccarthy: if it recurs forever, it probably doesn't happen very often. |
| 10:33:34 | mccarthy | pb_: but the *future* view would still be infinitely long :( |
| 10:34:26 | pb_ | mccarthy: indeed, the future encompasses an infinite amount of time :-) |
| 10:34:55 | mccarthy | would you be opposed to a "show one" approach? |
| 10:35:14 | pb_ | mccarthy: the code for the future view just needs to be a bit smart about obtaining data for events, so it just gets enough information to fill the visible area. |
| 10:35:17 | mccarthy | (at least for now) |
| 10:35:44 | pb_ | No, not particularly. |
| 10:35:51 | mccarthy | oh, well I have never actually looked at the code for future view (I dont think....) |
| 10:36:09 | mccarthy | I need to get the alarm working! |
| 10:36:31 | pb_ | Has Nils produced that document yet? |
| 10:36:41 | mccarthy | not that I know of |
| 10:36:42 | PaxAnima | mccarthy: how do you plan to do the alarm thingy? |
| 10:36:48 | colin_werk | mccarthy: If you add a recur icon, can you also add an alarm icon (a hollow one and a opaque one)? We had nice little bells in storm, and I think the icons are in CVS even |
| 10:36:56 | pb_ | Sounds like we should dispatch Colin to Netphen to give Nils a kicking. |
| 10:37:05 | colin_werk | :) |
| 10:37:14 | colin_werk | I can call him first :) |
| 10:37:22 | mccarthy | colin_werk: I should get them in *storm* CVS? |
| 10:37:39 | mccarthy | and why do I want 2 alarm pixmaps? |
| 10:37:41 | pb_ | mccarthy: I think the icons Colin is talking about are in gpe-icons CVS. |
| 10:37:52 | mccarthy | oh. cool. |
| 10:37:56 | colin_werk | mccarthy: I think I checked them into gpe-icons |
| 10:38:13 | mccarthy | colin_werk: why do I want 2 alarm pixmaps? |
| 10:39:28 | colin_werk | . |
| 10:39:37 | mccarthy | I only see gpe-alarm.png and it is not very pretty |
| 10:39:41 | colin_werk | Argh, it swalloed my reply. |
| 10:39:52 | colin_werk | One sec. |
| 10:40:46 | colin_werk | http://storm-pim.sourceforge.net/screenshots/storm-7.png shows the yellow bell |
| 10:41:15 | pb_ | mccarthy: mmm, looks like you're right: they must have been in the old "storm" directory that we deleted. |
| 10:41:34 | colin_werk | mccarthy: the hollow bell for "silent" alarms, or for events hat should not alarm at all? |
| 10:41:44 | colin_werk | Well, storm CVS has them. |
| 10:41:53 | mccarthy | pb_: I never realized that your future view is really (only events over the next year) view |
| 10:42:14 | mccarthy | colin_werk: yep. that little bell looks nice |
| 10:42:23 | mccarthy | did you guys do anything for recurrence? |
| 10:42:29 | mccarthy | img-wise? |
| 10:42:54 | colin_werk | http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/storm-pim/storm/pixmaps/ |
| 10:43:04 | colin_werk | mccarthy: No |
| 10:44:16 | colin_werk | http://storm-pim.sourceforge.net/screenshots/storm-4.png has that "2 circled arrows" pixmap you could use, a bit scaled down maybe |
| 10:44:52 | pb_ | mccarthy: just looking at your event-db changes: it looks like you output all your recurrence tags even for non-recurring events? |
| 10:46:06 | mccarthy | pb_: yeah, I need to fix that like you do with the alarm flag.... but I think your alarm thingie is busted anyhow... it seems to "generate" alarms by itself... |
| 10:46:50 | pb_ | mccarthy: there are probably some issues with alarm handling on things that were migrated from an old database. |
| 10:47:20 | mccarthy | I will try to fix "all this and more" at lunchtime :) |
| 10:47:28 | pb_ | ok, great. |
| 10:47:53 | pb_ | ideally, I would like just a single tag for "recurrence" which contains a textual description of when the event should recur. |
| 10:48:00 | mccarthy | I would like to add a "tentative" button to the event-ui and then have those items listed gray or something so you can "pencil in" something |
| 10:48:13 | pb_ | sounds like a nice idea. |
| 10:48:19 | mccarthy | also, the month-view doesn't highlight the current day |
| 10:49:19 | mccarthy | I would *love* to re-write the year-view so that it worked (and looked) more like the month-view, but I think I will have to just bug you until you do it since I dont understand the month-view |
| 10:49:40 | pb_ | I'm holding off on doing that in case you change your mind again :-) |
| 10:49:46 | mccarthy | pb_: there is a small bug in month-view BTW. Check out september (next month).... not enough wekk rows! |
| 10:50:07 | pb_ | mccarthy: hmm, want to file that (and the lack of a current-day highlight) in bugzilla? |
| 10:50:10 | mccarthy | pb_: I wont change my mind. I *love* the month-view, now ;) |
| 10:50:20 | pb_ | mccarthy: okay then :-) |
| 10:51:09 | mccarthy | I will do the current day highlight myself today, I think, but I can file the other... also I forgot to file the datesel issue that you need to click ahead-month *twice* the first time for some reason (it jumps to the last day of the current month the first time) |
| 10:51:26 | pb_ | still? I thought that one was fixed. |
| 10:51:48 | mccarthy | hmmm... it wasn't yesturday.... I can update and check |
| 10:52:04 | pb_ | ok. well, file if it's still happening. |
| 10:52:32 | mccarthy | can I take img from dillo? |
| 10:52:37 | pb_ | sure. |
| 10:52:57 | mccarthy | I like there recur arrows. I just need to change the colors (I think) |
| 10:55:10 | pb_ | mccarthy: as for alarms, maybe we should try to cooperate with opie to produce some kind of unified alarm framework. Wanna try talking to Max? |
| 10:55:44 | mccarthy | ahhh, I dont wanna write the rtc code... I cannot follow nils' stuff *at all* |
| 10:57:05 | mccarthy | I hacked it to restart the app that it is trying to signal, but it crashes *after* the alarm goes off (if you try to connect to it again) |
| 10:57:20 | mccarthy | otherwise we would be good (for now) |
| 10:57:26 | pb_ | hmm. |
| 10:57:47 | mccarthy | I am gonna give it a quick gdb later and see if it is trivial to fix then send diffs to nils |
| 10:58:08 | mccarthy | (but he wont like them, he wants to chage *everything*, I just want it to *work*) |
| 10:58:22 | mccarthy | what are the flags on diff to make a nice "patch"? |
| 10:58:54 | pb_ | well, I kind of agree with Nils on that (!) - I would prefer to come up with a solution that is good in general, rather than perpetuate a hack that just solves our immediate problem. |
| 10:58:58 | pb_ | diff -up is usually good. |
| 10:59:19 | pb_ | but some people prefer -c to -u, it's a matter of taste (and, to some extent, depends on the changes) |
| 11:00:33 | mccarthy | pb_: but if the gpe-calendar is the only thing *currently* using the alarming stuff (pun intended) then as long as we (you and I) agree to fix it when Nils comes up with something *good* then the hack is fine for a release... |
| 11:02:38 | pb_ | So long as it does really work reliably, yeah, I guess that's true. I'm just nervous about getting stuck with this hack for a long time. |
| 11:03:08 | mccarthy | but instead we are stuck with something that doesnt *work* for a long time... :( |
| 11:03:23 | mccarthy | but I get your point, once it works the driving force to fix the hack becomes smaller |
| 11:03:42 | pb_ | indeed. |
| 11:04:59 | pb_ | still, we also don't want to end up in the same situation we had with the database, where we are waiting an indeterminate amount of time for Nils / DaveH to produce something that never actually materialises :-} |
| 11:05:41 | mccarthy | but what he *already* did is really nice, I just dont understand it enough to fix it properly (so far) |
| 11:05:58 | pb_ | ah ok. |
| 11:06:06 | pb_ | I haven't ever really looked at the stuff he's done so far. |
| 11:06:32 | mccarthy | if you use what he did already, it works *great* as long as gpe-alarm is *still running* when the alarm goes off |
| 11:06:48 | mccarthy | I have tried to relax this requirement |
| 11:07:38 | pb_ | I see. |
| 11:08:01 | mccarthy | also, I am too lazy/stupid to set up gpe-calendar to take a signal from the rtcd and then open an alarm dialog, so I tried to hack it so that you can have gpe-alarm act as an alarm dialog for *any* app if you want it to |
| 11:08:35 | mccarthy | both of these ideas *almost* work right now |
| 11:34:57 | mccarthy | later |
| 16:34:03 | mccarthy | anyone wanna help a newbie with WEP?! |
| 17:07:03 | pb_ | ugh WEP |
| 17:09:13 | mccarthy | pb_: do you use wep? |
| 17:09:41 | pb_ | yeah. |
| 17:10:31 | mccarthy | 64 or 128? |
| 17:10:34 | pb_ | 128 |
| 17:10:42 | pb_ | I don't remember a whole lot about setting it up though. :-} |
| 17:10:42 | mccarthy | with wap AP? |
| 17:10:47 | mccarthy | (does it matter?) |
| 17:11:04 | mccarthy | can you look at your /etc/pcmcia/wireless.opts? |
| 17:11:22 | pb_ | no, this was just between two machines in adhoc mode, no AP. |
| 17:11:22 | mccarthy | or, since I am on a different continent, can you zap it to me?! |
| 17:11:31 | mccarthy | (I would have trouble pimpin off yours) |
| 17:12:14 | pb_ | not right now, unfortunately. I lost my iPAQ config in an upgrade a week or so ago (accidentally said "y" when ipkg asked me if I wanted to overwrite a config file); the only other machine with the configuration on is my laptop, which is at the office and switched off. |
| 17:12:44 | mccarthy | OK. no hurry. If you remember youcan email it to me (if you dont mind) |
| 17:13:08 | mccarthy | thanks. work is weird today. gotta go. |
| 17:13:23 | mccarthy | (damn students, who said they could come *back*?!) |
| 17:14:46 | BBrox | What happened to armlinux.org ? |
| 17:14:56 | pb_ | all its nameservers are dead. |
| 17:15:20 | pb_ | well, the primary and one of the secondaries is dead; it does actually have one surviving secondary. |
| 17:16:58 | BBrox | Errrrm |
| 17:18:43 | pb_ | ? |
| 17:21:46 | BBrox | Well, I 'errrrrm'ed the whole DNS situation :-) |
| 17:22:08 | pb_ | ah :-) |
| 18:26:11 | ulf | Hi |
| 18:28:10 | pb_ | hi |
| 18:28:45 | ulf | Just installed gpe on my ipaq... |
| 20:00:42 | mallum | hey |
| 20:01:43 | pb_ | hi mallum |
| 20:02:48 | mallum | hey pb_, just got your botmail |
| 20:03:02 | pb_ | ah yes. |
| 20:04:15 | mallum | when did it happen on startup with an empty dock ? |
| 20:04:21 | pb_ | yeah. |
| 20:04:53 | pb_ | I started up for the first time, and the dock was completely empty except for the little ^ symbol. So I added a few apps, and they all wound up piled on top of each other. |
| 20:05:00 | mallum | ah, I can tell by looking at at whats happened , thats fixed now :) |
| 20:05:08 | pb_ | ah cool :-) |
| 20:05:24 | pb_ | also, I didn't have much luck moving apps around in the dock. |
| 20:05:37 | mallum | how did you do it ? |
| 20:05:50 | pb_ | tap and hold, choose "move", then tried to drag an icon. |
| 20:07:01 | mallum | and it didn't let you ? |
| 20:07:19 | mallum | it will only move apps to where there is free space |
| 20:07:52 | pb_ | Well, I did manage to move a monolaunch. But when I tried with mmenu, it just behaved as if I hadn't selected "move" at all - as soon as I put the stylus on the icon, the menu popped up. |
| 20:08:16 | pb_ | Same with xstroke. |
| 20:08:54 | mallum | you have to make sure the hotspot is on a solid area of the actual app |
| 20:09:24 | pb_ | hmm, right. I can see that might be tricky with xstroke. Should be ok with mmenu though, that icon is completely opaque isn't it? |
| 20:09:28 | mallum | cos the windows are shaped the event passes write through I have a plan to improve this though |
| 20:10:00 | mallum | yeah should be fine with mmenu, I guess cos the icons are so small theres a bit of a knack to it |
| 20:10:28 | pb_ | when I said "the menu pops up", I meant the mmenu menu, not the dock menu. So I guess I must have been hitting the icon. |
| 20:10:51 | pb_ | and with xstroke, it kept changing mode when I tried to drag it, so again it must have been noticing the clics. |
| 20:10:53 | pb_ | clicks. |
| 20:11:40 | pb_ | I see the pointer is visible as a dot now too, was that deliberate? |
| 20:13:03 | ade | pb_ love this olirc .. works wonders |
| 20:13:18 | pb_ | heh :-) |
| 20:13:58 | mallum | pb_: pointer ? |
| 20:14:05 | pb_ | cursor |
| 20:15:05 | ade | wow , what happend to armlinux ?? |
| 20:15:22 | pb_ | <BBrox> What happened to armlinux.org ? |
| 20:15:22 | pb_ | <pb_> all its nameservers are dead. |
| 20:15:22 | pb_ | <pb_> well, the primary and one of the secondaries is dead; it does actually have one surviving secondary. |
| 20:15:55 | ade | oh dear |
| 20:16:07 | ade | will it come alive again ? |
| 20:16:21 | pb_ | maybe, yeah. |
| 20:17:18 | pb_ | moving europa to a different domain seemed like the most expedient course of action for the time being, though. |
| 20:19:29 | ade__ | wish my dad would stop upgrading win2k to sp3... takes all bandwidth and keeps rebooting |
| 20:20:44 | mallum | pb_: are you running with the cursor hidden then ? |
| 20:21:00 | mallum | pb_: the cursor should change to a <=> when you select move |
| 20:21:02 | pb_ | yes. |
| 20:21:11 | pb_ | I always have the cursor hidden on my ipaq. |
| 20:22:47 | mallum | ah and it dont change to a '<=>' ? |
| 20:24:27 | pb_ | Nope, it stays as just a dot. |
| 20:26:56 | mallum | pb_: hmm and is that all it is normally ? |
| 20:27:02 | pb_ | yeah |
| 20:27:19 | pb_ | well, depends what you mean "normally". It used to be completely invisible with older matchboxes. |
| 20:36:06 | mallum | pb_: ok, play with it some more and see if it improves, without a cursor though its gonna be difficult to signal back to the user when they have a grab etc |
| 20:36:37 | pb_ | mallum: yeah, I think there needs to be some other way of indicating that, maybe an icon in one corner of the screen or something. |
| 20:37:42 | mallum | pb_: yeah, although it would be nice to make the cursor appear when it *needs* too, but hidden most of the time |
| 20:39:12 | pb_ | mmm, possibly. I'm not completely convinced that would be desirable. |
| 20:42:00 | mallum | pb_: play with it a little more and see how you get on, I can make the dock 'do something' other than change the cursor if it can detect a no cursor setting ( XSETTINGS ? ) ... I'll get a new build out too over the weekend with better positioning and improved grabbing |
| 20:42:16 | mallum | pb_: thanks for the cyclone mail BTW - have you tried it ? |
| 20:42:45 | pb_ | mallum: not yet, I might try it at the weekend. |
| 20:43:12 | pb_ | mallum: ok, I'll continue playing with the dock and report back. |
| 20:43:17 | mallum | pb_: cool |
| 20:43:28 | mallum | pb_: do you know whats new in the bootloader ? |
| 20:43:47 | pb_ | mallum: not exactly. The big news is that it is supposed to be able to boot linux kernels directly, no need for catsboot. |
| 20:45:39 | mallum | pb_: ah nice |
| 20:45:52 | mallum | wonders if it now understands directorys |
| 20:46:09 | mallum | pb_: also I got a mail from wookey re matchbox article |
| 20:48:43 | pb_ | oh right, what did wookey have to say? |
| 20:48:47 | mallum | pb_: he using matchbox for some psion based linux distro and may be able to get me a free psion |
| 20:48:56 | pb_ | cool :-) |
| 20:49:28 | mallum | he seems like a nice chap |
| 20:49:35 | pb_ | yeah, he is. |
| 20:55:11 | mallum | pb_: Have you seen this gpe matchbox mail ? |
| 20:55:20 | pb_ | no |
| 20:58:04 | pb_ | ok, I found it in the archives. For some reason mail from the list is taking ages to reach me at the moment, it must be going via some obscure relay. |
| 20:58:54 | mallum | pb_: I dont really understand it / know what to say |
| 20:59:09 | pb_ | Me neither, really. |
| 20:59:33 | pb_ | I agree with his point about it being a bit confusing that the current window is left out of the drop-down list, though I'm not quite sure what to do about it. |
| 20:59:58 | pb_ | But I don't think we should be doing anything to make gpe-appmgr appear special. |
| 21:02:13 | mallum | pb_: no appmgr should be a desktop window or summin |
| 21:02:30 | mallum | pb_: but I dont think morbis wants to take that root |
| 21:02:40 | pb_ | (ho, ho) |
| 21:02:58 | pb_ | But yeah, I think you're right. |
| 21:03:17 | mallum | pb_: its trivial to add the current window to dropdown list, but Im not sure if it really makes a lot of difference |
| 21:03:34 | mallum | pb_: apart from using more screen space ? |
| 21:04:02 | mallum | 'Ashish Ganatra' sounds like a nice fellow |
| 21:04:14 | ade|dvd | lol |
| 21:04:41 | pb_ | mallum: well, it's annoying if you pull down the menu, go to click on a window and miss by one entry. When you pull down the menu again, everything has moved around - it would be less disorienting if the menu stayed the same. |
| 21:08:04 | pb_ | mallum: it sounds like George chucked your friend Ashish off the list. |
| 21:08:46 | mallum | pb_: bummer |
| 21:09:08 | mallum | pb_: why get rid of such a smart promising kid |
| 21:10:36 | ade|dvd | its been a while since ibeing called a ' mutha fucka' |
| 21:11:03 | mallum | pb_: I'll maybe mak ethe menu like that for the next cvs release and see how it goes down |
| 21:11:35 | pb_ | cool. |
| 21:26:37 | mallum | pb_: I went to this Perl 6 talk last night |
| 21:26:51 | pb_ | oh yeah, what was it like? |
| 21:27:30 | mallum | pb_: pretty cool, I havn't touched Perl for a while ( got pretty sick of it ), but Perl 6 seems like its gonna be a whole new language more or less |
| 21:27:48 | mallum | pb_: with a lot fo the cludge removed and some really insane new stuff |
| 21:28:54 | pb_ | excellent. |
| 21:29:28 | mallum | there planning to replace regular expressions |
| 21:29:34 | mallum | ! |
| 21:29:43 | pb_ | wow |
| 21:31:15 | mallum | seems like a lot of stuff stolen from python too |
| 21:31:18 | PaxAnima | replace Regexp? |
| 21:33:13 | mallum | yeah with this new more readable more powerful stuff |
| 21:35:20 | PaxAnima | readable AND more powerfull? could be fun to watch |
| 22:46:47 | ade | cya |
