straightforward use of engines

[Aaron J. Seigo]

On Wednesday 02 April 2008, Jordi Polo wrote:
> The twitter engine has several interfaces, but I only wanted to use the
> send information "interface" (or should I call it hack?).

yes, this needs to be replaced by Plasma::Service at some point.

> As I have the twitter applet up and running I suppose that each
> DataEngineManager::self()->load("twitter"); will do exactly that and create
> a new engine.

remember that if you call DataEngineManager::load yourself, call unload when 
you are done with it.

> - The engines have their own configuration gui. The configuration gui of

s,engines,service,

in this case, you'd request a service for a given user, the service would know 
it needs a password and would then prompt for it. unlike engines, services 
will be allowed to both have (transient) GUI's and config storage.

> It may be a solved 

on paper, not yet in code.

> or trivial problem. 

not really =)

-- 
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 Trolltech
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/panel-devel/attachments/20080402/bf6f8f63/attachment.pgp