00:56:42  * FearTheCowboyquit (Read error: Connection reset by peer)
00:56:50  * FearTheCowboyjoined
00:56:50  * FearTheCowboyquit (Changing host)
00:56:50  * FearTheCowboyjoined
02:02:28  * auroraeosrosequit (Ping timeout: 245 seconds)
03:31:04  * bherilajoined
03:42:26  * bherilapart
06:28:08  * ender`joined
10:46:24  * auroraeosrosejoined
13:55:30  * FearTheCowboyquit
14:46:07  * bherilajoined
15:01:32  * Jeanne-Kamikazejoined
15:51:20  * madewokherdjoined
17:00:13  * FearTheCowboyjoined
17:00:13  * FearTheCowboyquit (Changing host)
17:00:13  * FearTheCowboyjoined
17:00:20  <FearTheCowboy>Weekly #OneGet community meeting starts RIGHT NOW! join via Lync - https://t.co/2nieM91dnE Everyone Welcome
17:02:59  <FearTheCowboy>auroraeosrose ... coming?
17:03:33  <auroraeosrose>if lync cooperates
17:03:44  <auroraeosrose>link wrong?
17:03:47  * auroraeosrosemumbles
17:03:57  <FearTheCowboy>uh, works for me
17:04:00  <auroraeosrose>oh, just ... really slow
17:34:32  <madewokherd>come to think of it, dbus is really good for simple types and not really needing definitions of everything ahead of time
17:34:48  <FearTheCowboy>that's got a lot of virtue :D
17:36:54  <madewokherd>the main issue is windows compatibility
17:37:26  <madewokherd>in theory it's just a wire protocol and you don't even need the real dbus libraries (especially if you're not using arrays, variants, signals, session/system busses)
17:37:37  <madewokherd>but I have to wonder if all the language support is going to carry over
17:38:30  <madewokherd>"The Windows port from the windbus and dbus4win projects has been merged into the freedesktop dbus development branch and the spec has been updated with windows specific stuff"
17:38:34  <madewokherd>I may need to reread that spec
17:41:09  <FearTheCowboy>hmm
17:41:42  <ender`>...late again
17:45:16  <ender`>is the meeting over?
17:47:29  <madewokherd>I think it's no good
17:47:52  <madewokherd>too hard to get standard dbus tools to talk to, say, a parent process
17:48:15  <FearTheCowboy>Yeah, it's over
17:48:21  <FearTheCowboy>pity.
17:48:23  <ender`>that was short
17:48:34  <FearTheCowboy>it was a short one today. nothing terribly big
17:48:40  <madewokherd>I'm looking at the python bindings and I can't figure it out
17:49:06  <madewokherd>it's fine if you want a session bus, or even your own special bus for providers
17:49:56  <ender`>does dbus on windows still open a console in the background for it's "daemon" process?
17:49:57  <madewokherd>but then you need a service and that gets complicated
17:50:09  <madewokherd>I have no idea
17:56:46  <ender`>at least the way i've seen dbus on windows, it could run as a service, but that wasn't necessary - if the service wasn't running, the application spawned dbus-daemon (IIRC) in the background, which on windows unfortunately opened a console window
18:56:42  <madewokherd>even having a bus (rather than two-party communication) is too much I think
19:12:28  <ender|>FearTheCowboy: around?
20:08:44  * madewokherdquit (Read error: Connection reset by peer)
20:21:09  * madewokherdjoined
22:18:48  * ender`quit (Quit: Debian comes in three flavours: stale, rusting and broken.)
22:20:42  * Jeanne-Kamikazequit (Quit: Leaving)