[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-26 Thread Mikkel Kamstrup Erlandsen
If we want to re-instate the old system it is a matter of a few lines. But that would be a step back IMHO. And writing a full template based notification system could not be done in two hours by one. It's not a huge task, but definitely more than two hours :-) Besides, I really think we should sto

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-27 Thread Mikkel Kamstrup Erlandsen
Let me add a comment here on why we can't just emit a signal to everyone... In the future it is not impossible that many apps are connected to Zeitgeist. Indeed if we have a hook in Gtk+ or Glib then *all* apps are connected to us. Thus we'd send a signal to all desktop processes - waking them up

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-27 Thread Mikkel Kamstrup Erlandsen
I think I read somewhere in the Tracker changelogs that they committed a fix for this, but maybe I mistook a normal comment on the matter as a real committed fix... Regarding 0.3 status I think we should ship 0.3.0 without it. There's nothing stopping us having 0.3.1 next week already of we have g

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-27 Thread Mikkel Kamstrup Erlandsen
I am looking into the directed signals approach, and from a look at the DBus spec this should be possible. If we can somehow create our own dbus.lowlevel.SignalMessage then we can call set_destination(unique_name) on that. See http://dbus.freedesktop.org/doc/dbus-python/api/. Alse see http://dbus.f

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-27 Thread Mikkel Kamstrup Erlandsen
Ok. I think I know how to do this now. I just need to find the time to actually write the code :-) Look at the nested emit_signal() method here: http://dbus.freedesktop.org/doc/dbus-python/api/dbus.decorators- pysrc.html#signal -- Add event notification and subscription system https://bugs.launc

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-28 Thread Markus Korn
** Branch linked: lp:~thekorn/+junk/test_dbus_direct_signal -- Add event notification and subscription system https://bugs.launchpad.net/bugs/488967 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Framework. Status in Zeitgei

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-28 Thread Markus Korn
In the attached branch I tried to put together a sample dbus service which *should* send directed signals, but somehow it is not working as I expect it to work. There are two scripts, service.py which starts the service, and client.py (0|1), the client. starting the client with argument '1' means

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-28 Thread Markus Korn
maybe this screencasts help to understand whyt I mean ;) ** Attachment added: "out.ogv" http://launchpadlibrarian.net/36195528/out.ogv -- Add event notification and subscription system https://bugs.launchpad.net/bugs/488967 You received this bug notification because you are a member of Zeitge

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-28 Thread Mikkel Kamstrup Erlandsen
Cool that you did this test Markus! I am a bit troubled by the results though... I fear that signals are by definition always broadcasted. We may be able to work around this by setting a match rule on each signal connection on the client side, but I am not sure... Something like adding a named par

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-28 Thread Seif Lotfy
just my piece of non techi view to this issue we should make sure that it gets in with the 0.3.1 release since teamgeist also depends on it. Sorry for being absent now my lil brother is over -- Add event notification and subscription system https://bugs.launchpad.net/bugs/488967 You received

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-12-01 Thread Mikkel Kamstrup Erlandsen
I have te beginings of an implementation along the lines I describe above. It is still not ready for review, but I have it on lp:~kamstrup/zeitgeist/notification. ** Branch linked: lp:~kamstrup/zeitgeist/notification -- Add event notification and subscription system https://bugs.launchpad.net/bu

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-12-06 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist Status: Confirmed => Fix Committed -- Add event notification and subscription system https://bugs.launchpad.net/bugs/488967 You received this bug notification because you are a member of Zeitgeist Framework, which is the registrant for Zeitgeist Framework. Status

[Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-12-07 Thread Seif Lotfy
** Changed in: zeitgeist Status: Fix Committed => Fix Released -- Add event notification and subscription system https://bugs.launchpad.net/bugs/488967 You received this bug notification because you are a member of Zeitgeist Framework, which is the registrant for Zeitgeist Framework. Stat

Re: [Zeitgeist] [Bug 488967] Re: Add event notification and subscription system

2009-11-27 Thread Siegfried Gevatter
Yeah, I agree you way is the way to go (I'm just wondering why the Tracker guys didn't think of this, as I had a talk with Ivan at Bolzano and he told me they also have problems with signals and that their not optimal solution was to send a different signal for every type of data). Unrelated to th