From kde-panel-devel  Tue Oct 23 19:07:42 2007
From: "James Smith" <smithjd15 () gmail ! com>
Date: Tue, 23 Oct 2007 19:07:42 +0000
To: kde-panel-devel
Subject: [Panel-devel] Plasmoid desklets .. extended .desktop files.
Message-Id: <992350120710231207g25da5b72rb6250dfdf9c0256a () mail ! gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=119316652919178
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============0040281356=="

--===============0040281356==
Content-Type: multipart/alternative; 
	boundary="----=_Part_3235_2646477.1193166462990"

------=_Part_3235_2646477.1193166462990
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Would it make more sense perhaps to use .desktop files to store visual
plasmoids and have .pengine in separate files? I can see being able to
toggle preview of  plasmoids in konqueror / dolphin / kicker instead of a
desktop toolbox or plasmoid catalogue as we have now. Plasmoids can be
pushed right into kicker as well, and / or dropped where desired in
containers on the desktop or the desktop proper.

Down the road this is better for third party plasmoid developers as engines
are refined and rolled up into kde releases proper. It helps to encourage
better coding practices among developers with more reuse of engine code, as
well as unifying the launcher plasmoids and plasmoids proper, and a unified
way to script the kde desktop components interactively.

I haven't played with Beta 3 yet, but it would be great to be able to use
Kioslaves to set the default directory of the containers, enabling sharing
of contents across networks.

BTW, looking forward to Kross. =)
(Agent) Smith

------=_Part_3235_2646477.1193166462990
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Would it make more sense perhaps to use .desktop files to store visual plasmoids and have .pengine in separate files? I can see being able to toggle preview of &nbsp;plasmoids in konqueror / dolphin / kicker&nbsp;instead of a desktop toolbox or plasmoid catalogue as we have now. Plasmoids can be pushed right into kicker as well, and / or dropped where desired in containers on the desktop or the desktop proper.
</div>
<div>&nbsp;</div>
<div>Down the road this is better for third party plasmoid developers as engines are refined and rolled up into kde releases proper. It helps to encourage better coding practices among developers with more reuse of engine code, as well as unifying the launcher plasmoids and plasmoids proper, and a unified way to script the kde desktop components interactively.
</div>
<div>&nbsp;</div>
<div>I haven&#39;t played with Beta 3 yet, but it would be great to be able to use Kioslaves to set the default directory of the containers, enabling sharing of contents across networks.</div>
<div>&nbsp;</div>
<div>BTW, looking forward to Kross. =)</div>
<div>(Agent) Smith</div>

------=_Part_3235_2646477.1193166462990--

--===============0040281356==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel

--===============0040281356==--