[02:19] *** elvum has joined #kamaelia
[04:32] *** Lawouach_ has joined #kamaelia
[04:40] *** salmon_ has joined #kamaelia
[06:22] *** Uraeus has joined #kamaelia
[07:01] *** SamHasler has joined #kamaelia
[07:09] *** MS- has parted #kamaelia
[07:39] *** salmon_ has joined #kamaelia
[08:00] *** Uraeus has joined #kamaelia
[08:06] *** MS- has joined #kamaelia
[08:06] < MS-> greetings
[08:28] < Lawouach> hello
[08:29] < Lawouach> my gosh, I'm going nuts with integrating the scheduler with Qt
[08:29] < Lawouach> not that it's not possible but there are all kinds of pitfalls
[08:29] < Lawouach> mainly due to threads issues
[08:30] < MS-> heya
[08:30] *** MS- listens
[08:30] < MS-> I'd like to get that working nicely fwiw
[08:31] < Lawouach> well would I
[08:31] < Lawouach> I've tried many scenarios
[08:31] < Lawouach> hang on
[08:32] < Lawouach> first
[08:32] < Lawouach> I tried simply running Axon.background()
[08:32] < Lawouach> That works well except if your components at some point try to interact with the GUI
[08:32] < Lawouach> in theory Qt4 signals are thread-safe but perhaps not from a Python thread
[08:33] < Lawouach> so there are some nasty GUI deadlocks in that scenario
[08:33] < MS-> They probably need to be a QThread
[08:33] < MS-> (If I've got the right class - I know they provide threading primitives)
[08:33] < Lawouach> yeap
[08:33] < Lawouach> so I tried that
[08:34] < Lawouach> This meant running scheduler.run.main() myself in a loop like this:
[08:34] < Lawouach> http://pastebin.ca/1420301
[08:35] < Lawouach> but I've experience some deadlocks too
[08:36] < Lawouach> eventually I decided to try implementing the scheduler as a QThread but without using Axon's scheduler
[08:36] < Lawouach> it didn't pan out as well as I wanted
[08:37] < Lawouach> I was almost tempted to run each application component I wrote in its own thread and rid of the scheduler
[08:37] < MS-> http://pastebin.ca/1420301 isn't too different from http://code.google.com/p/kamaelia/source/browse/trunk/Code/Python/Axon/Axon/background.py
[08:37] < Lawouach> but that doesn't sound good to me
[08:37] < MS-> What OS is this on OOI?
[08:38] < Lawouach> Linux
[08:38] *** MS- just wondering about possible OS level issues
[08:38] < Lawouach> Qt4.5
[08:38] < MS-> not that then
[08:38] < Lawouach> same deadlock experienced on MacOSX
[08:38] < Lawouach> The deadlock issue might also come from one of my components accessing the GUI without a signal
[08:38] < MS-> Yeah, I was mainly worried about windows really, since it's pretty braindead
[08:39] < Lawouach> I have a large set of components so it might be possible
[08:39] < MS-> quite possibly
[08:40] < MS-> If you can post the code anywhere for me to look at that'd be appreciated. If it's something that can't be public, I'm fine with that - just pass over a private channel (eg email :) )
[08:41] < Lawouach> it's public but large :)
[08:41] < Lawouach> it's basically widgets for headstock
[08:41] < MS-> I see. Well, point me at it and I'll take a look
[08:41] < MS-> I'm going afk in a few minutes BTW (just had a phone call dragging me off somewhere... :) )
[08:42] < Lawouach> http://trac.defuze.org/browser/oss/animato
[08:42] < Lawouach> np
[08:43] < Lawouach> animato is an application that would eventually allow for creating and running load test scenarios of XMPP servers
[08:43] < Lawouach> the GUI actually uses jlib for the various XMPP widgets
[08:43] < Lawouach> http://trac.defuze.org/browser/oss/jlib
[08:44] < Lawouach> those widgets are a mapping of headstock Axon components
[08:44] < Lawouach> the main class is http://trac.defuze.org/browser/oss/animato/animato/gui/mainwindow.py
[08:44] < Lawouach> where you'll see two different schedulers attempt
[08:45] < Lawouach> you should just run it like this:
[08:45] < Lawouach> cd animato
[08:45] < Lawouach> python animato/gui/mainwindow.py
[08:46] < Lawouach> this requires Qt 4.5 and PyQt 4 bindings latest snapshot
[08:47] < Lawouach> though might work with 4.4 and binary PyQt4 bindings
[08:57] < MS-> So to confirm in order to install this, I need:
[08:57] < MS-> headstock
[08:57] < MS-> jlib
[08:57] < MS-> animato
[08:57] < MS-> (which all look simple to install) and if necessary: upgrade to qt 4.5 and latest pyqt 4 bindings?
[08:57] < Lawouach> yeap
[08:57] < Lawouach> that's right
[08:57] < MS-> cool
[08:57] < Lawouach> for headstock you'll need bridge too
[08:57] < Lawouach> on my repo as well
[08:57] < MS-> k
[08:57] < Lawouach> I advise getting them from svn though
[08:59] < MS-> decided to : svn co https://svn.defuze.org/oss/ : to simplify things :)
[08:59] < Lawouach> yeap
[08:59] < Lawouach> that's what I do too :)
[08:59] < Lawouach> my repo isn't so big ;p
[09:00] < MS-> :)
[09:01] < Lawouach> if you plan on running it you'll need obviously an xmpp server
[09:01] < Lawouach> you can just grab the ejabberd installer
[09:01] < MS-> TypeError: argument 4 of QCoreApplication.translate() has an invalid type
[09:01] < Lawouach> it's really easy to run
[09:01] < Lawouach> oh?
[09:01] < MS-> appears to not work with the version of Qt I have installed
[09:01] < Lawouach> which module/line?
[09:01] < MS-> (was trying it on the offchance)
[09:02] < Lawouach> well the app will launch without the server
[09:02] < MS-> I didn't expect it to work FWIW
[09:02] < Lawouach> only when you start the clients will it ask for one :)
[09:02] < Lawouach> still
[09:02] < Lawouach> which Qt version are you using?
[09:03] < MS-> a stock installed version with SuSE 10.3 - appears to be qt 4.3
[09:03] < Lawouach> oh right
[09:03] < Lawouach> yeah rather old
[09:03] < MS-> As I said - I didn't expect it to work, but an easy check :)
[09:04] < Lawouach> http://www.qtsoftware.com/downloads
[09:04] < Lawouach> the Qt: Framework Only would be enough
[09:04] < MS-> ta
[09:04] < Lawouach> it's a self installer I think
[09:04] < Lawouach> along with the source if you need to recompile
[09:05] < MS-> OK, that's going to take a little while :)
[09:05] < Lawouach> yeap
[09:05] < MS-> I think I'll get lunch :)
[09:05] < Lawouach> and if you need to recompile it will also be rather long
[09:05] < Lawouach> yeap
[09:05] < Lawouach> I'll be online this afternoon :)
[09:05] < MS-> cool
[09:34] < Lawouach_> back
[11:58] *** elvum has parted #kamaelia
[12:34] *** PJ_Coudert_ has joined #kamaelia
[14:56] *** eikenberry has joined #kamaelia
[16:01] *** MS- has joined #kamaelia
[16:09] < eikenberry> http://www.kamaelia.org/Developers/Roadmap
[16:09] < eikenberry> Is that just behind or is it no longer relevant?
[16:13] < MS-> I think it's no longer relevant tbh. Lots of it is aspirational, but it was also dependent, rather heavily, on continued contribution by ex-gsoc students.
[16:14] < MS-> That said, I think actually kick starting a 6-weekly release candidate cycle is probably a good idea
[16:15] < MS-> (with the expectation that a full release would happen for every other release candidate)
[16:15] < MS-> On a personal level I've been a little overloaded, which has been the reason for slipping a bit
[16:16] < MS-> On a more useful note, I'm shifting projects at work, which will be a good fit for kamaelia which is useful :)
[16:17] < MS-> I think I need more realistic targets/goals for the roadmap at the moment :)
[16:24] < MS-> Maybe bi-monthly is more realistic.
[16:26] < MS-> I think I'll go with that.
[16:27] < MS-> FWIW, whilst the release schedule is definitely out of kilter, I'm still actively working on kamaelia. I've been spending some time looking at improving examples and performance given reports in recent months
[16:28] < MS-> Along with how to make it easier for people to add things into Kamaelia - specifically through the Kamaelia.Apps namespace.
[16:33] < aa_> MS-: (hi) is kamaelia/you making an appearance at europython?
[16:35] < MS-> I've yet to decide tbh - I should - but I'm not sure what to talk about this time :) I have a feeling that something based around real world uses of concurrency/kamaelia though
[16:35] < MS-> would be a good/useful idea.
[16:36] < MS-> Candidate things there being : backend transcoder for a website that serves user contributed videos as flvs ,
[16:36] < MS-> the greylisting server
[16:36] < MS-> whiteboard
[16:36] < MS-> & speak n write
[16:37] < MS-> But there's others as well, like a system for accepting & replying to SMS messages
[16:37] < MS-> The feedback I've generally had is "more real world examples"
[16:38] < MS-> But, more suggestions/etc very welcome
[16:39] *** salmon_ has joined #kamaelia
[16:43] < MS-> Gah, call for submissions closed.
[16:43] < MS-> hm
[16:43] < MS-> wonder if I can put something in (probably not :-/ )
[17:06] < MS-> eikenberry: Does this look better now: http://www.kamaelia.org/Developers/Roadmap ?
[17:10] *** vmlemon_ has joined #kamaelia
[17:13] < vmlemon_> Hi
[17:13] < MS-> hiya
[17:14] *** vmlemon_ just had "fun" setting up one of the 3 HSDPA dongles under Fedora
[17:15] < vmlemon_> Who would have thought that *not* setting the SUID bit on an executable would have made all the difference, between stuff working, and not working? :(
[17:18] < vmlemon_> Still, I get higher speeds and lower latency, for all the pain
[17:31] < eikenberry> MS-. Yes. Thanks. :)
[17:48] < Lawouach> evening
[17:48] *** vmlemon_1 has joined #kamaelia
[17:53] *** vmlemon_1 is now known as vmlemon_
[18:05] < MS-> Lawouach: evening
[18:55] *** Uraeus has joined #kamaelia
[19:02] *** vmlemon_ has joined #kamaelia
[19:53] *** salmon_ has joined #kamaelia