<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 2.4 (Linux)">
<style type="text/css">
<!--
@page { size: 8.5in 11in; margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style>
<p style="margin-bottom: 0in;">I just wanted to clarify some things so
I know exactly what I should be working on. I should also mention
that I'm a bit of a Qt4/KDE newbie :-).</p>
<p style="margin-bottom: 0in;">It was mentioned that the Upload class
is hopefully going to be moved to KNS by 4.1. What is keeping this
from happening? Is there anything that can be done to assure that
this happens for 4.1?</p>
<p style="margin-bottom: 0in;">Plasmagik is essentially a GUI that
applications can add to easily package and upload content to kns. It
should vary depending on the PackageStructure that it is being
passed.
</p>
<br><br><div class="gmail_quote">2008/3/5 Aaron J. Seigo <<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wednesday 05 March 2008, Riccardo Iaconelli wrote:<br>
> > application itself. =)<br>
><br>
> In the library, you mean, right? ;-)<br>
<br>
</div>yeah, kpart-like.<br>
<div class="Ih2E3d"><br>
> Plasmagik functionalities must be accessible from any apps.... remember our<br>
> chats?<br>
<br>
</div>i wonder how we should best go about exposing the functionality. do we have<br>
use cases defined for this, with which to design the API/interface for<br>
plasmagik against? for unpacking, listing packages, etc it certainly needs to<br>
be in a library (we have classes for that in libplasma, of course), but what<br>
are the package creation use cases? is it mostly "design studio" type<br>
applications?<br>
<br>
to create a package, Plasmagik needs:<br>
<br>
* a PackageStructure (or a PackageStructure rc file)<br>
* an optional base directory to start in<br>
<br>
does the host application need to be notified when packaging is complete? or<br>
is that something that plasmagik itself can handle without having to report<br>
back (making it more like a fire-and-forget assistant dialog?)</blockquote><div><br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 2.4 (Linux)">
<style type="text/css">
<!--
@page { size: 8.5in 11in; margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style>
<p style="margin-bottom: 0in;">I basically have the same questions.</p>
<p style="margin-bottom: 0in;">One of the goals of this project is to
remove assumptions based on the plasmoid package structure.
Currently, plasmagik forces you to add both "pics/images" and
"code/main.js". I assume that this is based on the plasmoid
structure and we want a more general GUI that can adapt based on
whether the user is creating a wallpaper, SVG Theme, etc. How will
the application pass to the GUI what type of package it wants to
make? Based on the PackageStructure that gets passed?</p>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div><div></div><div class="Wj3C7c"><br>
--<br>
Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Trolltech<br>
</div></div><br>_______________________________________________<br>
Panel-devel mailing list<br>
<a href="mailto:Panel-devel@kde.org">Panel-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/panel-devel" target="_blank">https://mail.kde.org/mailman/listinfo/panel-devel</a><br>
<br></blockquote></div><br>