move plasma tools to plasmate

[Shantanu Tushar Jha]

On Fri, Aug 17, 2012 at 8:50 PM, Giorgos Tsiapaliokas <terietor at gmail.com>wrote:

>
>
> On 17 August 2012 16:24, Aleix Pol <aleixpol at 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?
>

+1 For The Plasma SDK, this makes sense.


>
>
> 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??
>

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.

>
> 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?
>

Not sure about how to solve this


>
>

> 3. duplication of code, plasmoidviewer vs plasma-previewer
>

where's plasma-previewer? Looks like I missed some news :P


>
> 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
>
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>
Overall I +1 this proposal, and thanks for all the awesome work :)

-- 
Shantanu Tushar    (UTC +0530)
http://www.shantanutushar.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20120819/b82ef948/attachment.html>