<br><br><div class="gmail_quote">On Fri, Aug 17, 2012 at 8:50 PM, Giorgos Tsiapaliokas <span dir="ltr"><<a href="mailto:terietor@gmail.com" target="_blank">terietor@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br><br><div class="gmail_quote"><div class="im">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><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></div></div></blockquote><div><br>+1 For The Plasma SDK, this makes sense.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote">
<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></div></div></blockquote><div><br>Well you cannot, if you want both plasmoidviewer and plasmate to be able to use it, you'll have to move the stuff to some qwidget (or maybe a KPart?) so that they can share it.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><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?<br>
</div></div></div></div></blockquote><div><br>Not sure about how to solve this<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote">
<div><div> </div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div>
<div><br></div><div>3. duplication of code, plasmoidviewer vs plasma-previewer</div></div></div></div></blockquote><div><br>where's plasma-previewer? Looks like I missed some news :P<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_quote"><div><div><br></div><div>etc...</div></div><div class="im"><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><div>I believe that this is an overkill and also we don't solve the above technical issues.</div><div class="im"><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><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 class="im">
<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></div>
<br>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
<br></blockquote></div><br>Overall I +1 this proposal, and thanks for all the awesome work :)<br clear="all"><br>-- <br>Shantanu Tushar (UTC +0530)<br><a href="http://www.shantanutushar.com" target="_blank">http://www.shantanutushar.com</a><br>