Plasma Automator

[Dario Freddi]

On lunedì 16 febbraio 2009 18:33:05 Aaron J. Seigo wrote:
> 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".

Yeah, Nepomuk integration was one thing I thought about, but given my very 
small knowledge of the subject in question, I'd like some guidance here.

>
> other than network, what external stimulus might this be?
> how would this work with manually switching activities?

Starting a torrent download -> switching to a particular activity where you 
have download widgets
Open a document tagged "Work" in KOffice -> switch to the "Work" activity, 
just two small examples that came to my mind right now.

>
> why wouldn't this live inside the plasma desktop shell itself?

Sure, why not

>
> define "hook [..] into automater". is this to react to context changed
> events, or to trigger them?
>

Let me show you an example of what I mean. I create an application named foo, 
and I create an XML file for automator, that I will install with a shiny CMake 
macro. Let's say it will look like this:

<interface name="org.kde.foo">
<signal>
 <name>eventTriggered</name>
 <description>Foo triggers its wonderful event</description>
</signal>
</interface>

Automator will read this file. When the user goes into automator's config 
interface, and creates a new trigger, he will be shown possible context change 
events, through those XML files. So the user will be able to choose "Foo 
triggers its wonderful event". Internally, automator will listen to signal 
"eventTriggered" on interface org.kde.foo and then perform the action(s) the 
user associated with that event. It would look quite like DBus introspection.

Obviously, it would be great to extend this outer plasma: having somehow the 
whole desktop react through Nepomuk would be even greater, but I'll need 
someone with more expertise here.

Cheers,
Dario


-- 
-------------------

Dario Freddi
KDE Developer
GPG Key Signature: 511A9A3B

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20090216/64b0dd08/attachment.sig