On Sunday 15 February 2009, Dario Freddi wrote: > You set a preference in automator that switches your activity to "Home" > when you get connected to your own wifi. So automator catches the signal, > switches activity, and notifies you.
this sounds a lot like plasma activity -> plasma context -> nepomuk -> profit. the add on seems to be "changing plasma activity, which causes the rest of the cascade, based on external stimulus". other than network, what external stimulus might this be? how would this work with manually switching activities? why wouldn't this live inside the plasma desktop shell itself? > Applications could expose their DBus signals through XML files, that will > let automator catch a variety of events. So every developer can hook its > application into automator with a very minimum effort, define "hook [..] into automater". is this to react to context changed events, or to trigger them? > supposed that its > application is already exposed in DBus. all kde apps are visible on the bus. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
