[05:34] *** Lawouach_ has joined #kamaelia
[05:34] *** vmlemon_ has joined #kamaelia
[06:07] *** vmlemon_ has joined #kamaelia
[06:07] < vmlemon_> Hi
[07:40] *** vmlemon_ has joined #kamaelia
[08:01] *** Uraeus has joined #kamaelia
[08:18] *** MS- has joined #kamaelia
[08:18] < MS-> morning
[08:40] *** ian_brasil_ has joined #kamaelia
[08:53] *** Chong- has joined #kamaelia
[08:57] *** vmlemon_ has joined #kamaelia
[09:39] *** mhrd has joined #kamaelia
[09:39] < mhrd> greetings
[09:41] *** mhrd notes r5352 commit - could mean a more compact packaging up of your greylisting server, or possibly my pop3proxy ?
[09:48] < MS-> Could do, but that's note my intent
[09:48] < MS-> s/note/not/
[09:49] < MS-> My intent is just to have an absolutely minimal thing for people to play with.
[09:49] < MS-> Also shows that most components aren't dependent on each other really
[09:50] *** mhrd ponders that it might be fun to write a tool that analyses a kamaelia program to work out what components it needs to be bundled with
[09:51] < MS-> Indeed - I was watching a presentation about "what django should learn from where zope went horribly wrong"
[09:51] < MS-> and noted that the dependency graph was the biggest problem
[09:51] < MS-> Whereas for our stuff, we probably have clumps
[09:51] < mhrd> I'm thinking that the doc generation code already contains alot of the hard work needed
[09:52] < mhrd> I might have a play sometime
[09:53] < MS-> That's part of what I was thinking as well :)
[09:53] < MS-> Either that or a liberal sprinkling of metadata :)
[09:54] < mhrd> probably need both - the doc gen analysing code, for example, won't pick up anything within a conditional statement
[09:54] < mhrd> someone is bound to do something like:
[09:54] < mhrd> if 1:
[09:54] < mhrd> . import blah
[09:54] < mhrd> :)
[09:57] < MS-> indeed
[09:58] < MS-> I've got some code that has that sort of structure in places
[09:58] < MS-> Obviously not "if 1" :)
[09:59] < mhrd> at the time I drew the line there because it was an easy clear cut off - rather that having to give detailed explanation of what kind of expressions it would/would-not be able to evaluate :-)
[10:02] *** MS- nods
[10:05] < vmlemon_> Hi
[10:07] < MS-> vmlemon_: Hi
[10:07] < MS-> mhrd: Storing the deps more machine readably though would be useful from a packaging perspective.
[10:08] < MS-> Especially in the style of Jason's freezing approach
[10:08] < vmlemon_> Out of interest, what's the problem with Zope?
[10:11] < MS-> It's the fact that Zope turned into a closed ecosystem - it was very hard to pull stuff out from it to use in non-zope systems.
[10:14] < vmlemon_> Aah
[10:15] < MS-> (this is a risk for kamaelia as well - hence why Axon is seperate and useful by itself, and also why Handle exists)
[10:15] < MS-> (the latter specifically designed to allow kamaelia stuff to be useful in non-kamaelia systems
[10:16] < MS-> Also, the former means that when building components it's easier in many cases to pull in code from other libraries rather than reinvent wheels all the time. (As fun as wheel building is)
[10:51] *** ntoll has joined #kamaelia
[10:52] *** ntoll has parted #kamaelia
[11:25] *** ian_brasil_ has joined #kamaelia
[11:44] *** Uraeus has joined #kamaelia
[11:47] *** mhrd has joined #kamaelia
[12:06] *** ian_brasil_ has joined #kamaelia
[14:04] *** MS- has parted #kamaelia
[14:13] < ian_brasil_> MS: I saw that presentation too...very interesting i thought
[14:13] < ian_brasil_> ah, too late
[15:35] *** vmlemon_ has joined #kamaelia
[15:36] *** MS- has joined #kamaelia
[15:55] *** likefile has joined #kamaelia
[15:57] *** vmlemon_ has joined #kamaelia
[16:02] *** MS- has parted #kamaelia
[16:40] *** Lawouach_ has joined #kamaelia
[16:43] < vmlemon_> Hi
[16:46] < Chong-> evening, vmlemon_ and others.
[16:57] *** Uraeus has joined #kamaelia
[17:25] *** Uraeus_ has joined #kamaelia
[18:08] *** MS- has joined #kamaelia
[18:08] < MS-> evening
[18:11] < vmlemon_> Hi MS-
[18:17] *** ian_brasil has joined #kamaelia
[21:16] *** Davbo has joined #kamaelia