Finally found some time to hack on the Notification changes again. I basically cleaned up the library and made the server listen to the important bits so I could debug the calls. There are now a couple of neat things you can do by attaching a widget. First, the notification follows the widget and second your updates happen in the mainloop so you don’t have to send the notification every time you change something, Just change an attribute and on the next iteration of the loop it is updated (well actually in an idle handler). Ok so the last part doesn’t require a widget but my need to have the notification follow the widget on its own brought with it the auto updating feature.

I tried getting Colin’s bubble widget to display in the server but quickly found out neither the server or the bubble widget were what was needed. I’m most likely going to take a bit from both and most likely roll it into the notification applet or the panel with the option to turn it off and use another server if one would like.

At this point there are a few cleanups I would like to do to the library and then figure out with the Notification guys where it should reside. I will then go on to adapt a couple of usecases and finish up the input/events model. Hopefully others will jump in and give of their expertise.

I leave you with a short demo. Click on the screenshot to view an OGG I create with Istanbul. If you will notice there is quite a lag when running processor intensive applications like recording screen captures in realtime.

[read this post in: ar de es fr it ja ko pt ru zh-CN ]