Hi, Thanks James for making it clearer.. in my mind notification server = the main MSN server being used for presence/chat (it's called the notification server) and the "supports actions" in my head meant that a peer supports receiving chat messages of type 'actions' (which is a specific msn message type).
anyways, well.... this looks complicated and we won't be planning on implementing that. You could take a look at the notify plugin for aMSN as its purpose is to replace the amsn notifications with external notifications (using 'notify-send').. If that's different than what you request then I guess it could be patched to use your own notification-daemon or something, but since this is a plugin, the aMSN team is not responsible, you would have to patch it yourself or find the original author and ask him kindly. It seems fairly easy, and the path to nofify-send is configurable, so if your application is using a notify-send compatible command arguments, then it should just work. I hope this answers your question. p.s: note that amsn is a Tcl program and is multiplatform, so the core code is meant to be multiplatform and use Tcl. For extra stuff like desktop integration and platform specific tasks, then a plugin would be created, which is the purpose of the 'notify' plugin : http://amsn.svn.sourceforge.net/viewvc/amsn/trunk/amsn- extras/plugins/notify/ -- amsn shouldn't use notifications with actions https://bugs.launchpad.net/bugs/328607 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
