[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: move plasma tools to plasmate
From: Giorgos Tsiapaliokas <terietor () gmail ! com>
Date: 2012-08-17 15:20:08
Message-ID: CAODYyLbkgKZ10gkWKKkh+nqG7qjfEiXVzQC6yWZrygP=AxWNeg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 17 August 2012 16:24, Aleix Pol <aleixpol@kde.org> wrote:
>
> Hi,
> I don't really see the point of doing that. I don't see why it's
> better not to have them in kde-workspace is it troublesome for anyone?
>
From an aesthetic point of view,
Q: Hello, where are the plasma tools? I want to create a new plasmoid.
A: Inside kde-workspace you will find some tools which will make you life
easier
and in the plasmate repository you will find the plasma ide.
That's why we want to move those tools in plasmate, we want our sdk to be
neat. No?
From a technical point of view,
those are a few issues for which we have to move the plasma tools inside
plasmate,
1. How can someone embed a binary inside a qwidget?
Example: How can I embed the binary named plasmoidviewer inside
plasmate's MainWindow::CentralContainer::CentralContainer??
2. Some tools when they are used as standalone applications require a few
extra ui stuff.
Example: when I execute plasmaremoteinstaller from plasmate I have a known
source directory for my plasmoid(thanks to plasmate), but when
I execute it as a standalone application I don't., so I need an extra
kurlrequester. How can I hide a kurlrequester from a binary?
3. duplication of code, plasmoidviewer vs plasma-previewer
etc...
> In any case, maybe you should put them in a separate repository?
>
I believe that this is an overkill and also we don't solve the above
technical issues.
> Everyone who has been using these tools so far, has done so without
> Plasmate, so there's definitely a use case outside Plasmate.
>
When you say "plasmate" do you refer to the ide named plasmate or the
repository?
The plasma tools will be accessible both as standalone applications and as
plasmate plugins.
Also those tools aren't a use case outside plasmate. When those tools had
been created plasmate didn't exist.
Also after the creation of plasmate, the project wasn't really usable,
but this has changed by now.
--
Giorgos Tsiapaliokas (terietor)
KDE Developer
terietor.gr
[Attachment #5 (text/html)]
<div dir="ltr"><br><br><div class="gmail_quote">On 17 August 2012 16:24, Aleix Pol \
<span dir="ltr"><<a href="mailto:aleixpol@kde.org" \
target="_blank">aleixpol@kde.org</a>></span> wrote:<blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi,<br>
I don't really see the point of doing that. I don't see why it's<br>
better not to have them in kde-workspace is it troublesome for \
anyone?<br></blockquote><div><br></div><div><div>From an aesthetic point of \
view,</div><div><br></div><div>Q: Hello, where are the plasma tools? I want to create \
a new plasmoid.</div> <div>A: Inside kde-workspace you will find some tools which \
will make you life easier</div><div>and in the plasmate repository you will find the \
plasma ide.</div><div><br></div><div>That's why we want to move those tools in \
plasmate, we want our sdk to be neat. No?</div> \
<div><br></div><div><br></div><div>From a technical point of view,</div><div>those \
are a few issues for which we have to move the plasma tools inside \
plasmate,</div><div>1. How can someone embed a binary inside a qwidget?</div> \
<div>Example: How can I embed the binary named plasmoidviewer inside plasmate's \
MainWindow::CentralContainer::CentralContainer??</div><div><br></div><div>2. Some \
tools when they are used as standalone applications require a few extra ui \
stuff.</div> <div>Example: when I execute plasmaremoteinstaller from plasmate I have \
a known source directory for my plasmoid(thanks to plasmate), but when</div><div>I \
execute it as a standalone application I don't., so I need an extra \
kurlrequester. How can I hide a kurlrequester from a binary?</div> \
<div><br></div><div>3. duplication of code, plasmoidviewer vs \
plasma-previewer</div><div><br></div><div>etc...</div></div><div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
In any case, maybe you should put them in a separate \
repository?<br></blockquote><div><br></div><div>I believe that this is an overkill \
and also we don't solve the above technical issues.</div><div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
Everyone who has been using these tools so far, has done so without<br>
Plasmate, so there's definitely a use case outside \
Plasmate.<br></blockquote></div><div><br></div><div>When you say "plasmate" \
do you refer to the ide named plasmate or the repository?</div><div>The plasma tools \
will be accessible both as standalone applications and as plasmate plugins.</div> \
<div><br></div><div>Also those tools aren't a use case outside plasmate. When \
those tools had been created plasmate didn't exist.</div><div>Also after the \
creation of plasmate, the project wasn't really usable, but this has changed by \
now. </div> <div><br></div>-- <br><div dir="ltr">Giorgos Tsiapaliokas \
(terietor)<br>KDE Developer<br><br><a href="http://terietor.gr" \
target="_blank">terietor.gr</a></div><br> </div>
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic