Interested in Plasma SoC

[Aaron J. Seigo]

On Wednesday 05 March 2008, Riccardo Iaconelli wrote:
> > application itself. =)
>
> In the library, you mean, right? ;-)

yeah, kpart-like.

> Plasmagik functionalities must be accessible from any apps.... remember our
> chats?

i wonder how we should best go about exposing the functionality. do we have 
use cases defined for this, with which to design the API/interface for 
plasmagik against? for unpacking, listing packages, etc it certainly needs to 
be in a library (we have classes for that in libplasma, of course), but what 
are the package creation use cases? is it mostly "design studio" type 
applications?

to create a package, Plasmagik needs:

* a PackageStructure (or a PackageStructure rc file)
* an optional base directory to start in

does the host application need to be notified when packaging is complete? or 
is that something that plasmagik itself can handle without having to report 
back (making it more like a fire-and-forget assistant dialog?)

-- 
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/20080305/db8744bc/attachment.pgp