From kde-panel-devel Tue Mar 31 17:24:34 2009 From: Yuen Hoe Lim Date: Tue, 31 Mar 2009 17:24:34 +0000 To: kde-panel-devel Subject: Re: [GSoC] (One more) Proposal for Plasmate Message-Id: <26362f480903311024q5ee451a9ic8d82377a8920325 () mail ! gmail ! com> X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=123852035305096 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1948693389==" --===============1948693389== Content-Type: multipart/alternative; boundary=000e0cd30af609906a04666d79c6 --000e0cd30af609906a04666d79c6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit > > we already have a previewer started in playground; showing a plasmoid in a > little window by itself is a tiny amount of code, really. :) > > don't need to; we know where the code is on disk, and you can just pass > that > path directly to the Package which would then be used by the Applet object > to > run the widget. Evidently I have yet much to learn about the platform and available code :) * if the user needs an embedded terminal to make plasmate useful, > something's > horribly wrong :) it's all based on managing the contents of a Package and > that's all automated / automatable So happened that when I was telling a friend about Plasmate he exclaimed 'What, no terminal!?' :P I agree completely that Plasmate should not need to rely on the terminal emulator at all, but I was just thinking that it might be handy (I use Kate's terminal for all kinds of things). Hmmm, then again Plasmate will probably be maintaining the 'project files' somewhere out of sight so maybe its not such a good idea to let the user have terminal access to that location after all. > * for the diff viewer, we could probably use the kdiff kpart that comes > with > kde if it's available on the system (otherwise just show it in a plain text > editor, i suppose) Yeah, was thinking the same thing. Wonder how much work will it be though to manually produce one from a text diff file. Since it doesn't need to be editable, the hardest part would probably be parsing the diff file Thanks a lot for the comments by the way :) Will have them addressed before the deadline this friday >.< *fingers crossed* ---- Lim Yuen Hoe http://yuenhoe.co.cc/ --000e0cd30af609906a04666d79c6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
we already have a previewer started in playground; showing a plas= moid in a
little window by itself is a tiny amount of code, really. :)

don't need to; we know where the code is on disk, and you can just pass= that
path directly to the Package which would then be used by the Applet object = to
run the widget.

Evidently I have yet much to learn abo= ut the platform and available code :)

* if the user needs an embedded terminal to make plasmate useful, something= 's
horribly wrong :) it's all based on managing the contents of a Package = and
that's all automated / automatable

So happened tha= t when I was telling a friend about Plasmate he exclaimed 'What, no ter= minal!?' :P I agree completely that Plasmate should not need to rely on= the terminal emulator at all, but I was just thinking that it might be han= dy (I use Kate's terminal for all kinds of things).

Hmmm, then again Plasmate will probably be maintaining the 'project= files' somewhere out of sight so maybe its not such a good idea to let= the user have terminal access to that location after all.=A0
=A0
* for the diff viewer, we could probably use the kdiff kpart that comes wit= h
kde if it's available on the system (otherwise just show it in a plain = text
editor, i suppose)

Yeah, was thinking the same thing. = Wonder how much work will it be though to manually produce one from a text = diff file. Since it doesn't need to be editable, the hardest part would= probably be parsing the diff file

Thanks a lot for the comments by the way :) Will have them addressed be= fore the deadline this friday >.<

*fingers crossed*

----
Lim Yuen Hoe
http:/= /yuenhoe.co.cc/

--000e0cd30af609906a04666d79c6-- --===============1948693389== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel --===============1948693389==--