[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-20 8:37:16
Message-ID: CAODYyLavCte5_Zf3PDHhFhK3ah_2v_PmnihVCko-hNWBv1_3jw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 20 August 2012 02:15, Aleix Pol <aleixpol@kde.org> wrote:
>
> That's a packaging decision. The Plasmate should depend on the plasma
> tools.
The Plasmate IDE will depend on the plasma tools, either if they are in the
kde-workspace or in
the plasmate repo.
> > 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??
> I'm unsure what you mean. You can embed a plasma view. You won't ever
> embed the plasmoidviewer, maybe you can compile the same code twice,
> but it's not the same!
>
> >
> > 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?
> Well, you can add arguments to the binary, for example.
>
> >
> > 3. duplication of code, plasmoidviewer vs plasma-previewer
> You can expose a library.
I believe that the idea of moving the tools is much more better than
those workarounds.
> >> 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 IDE.
Those tools will still be accessible as standalone applications, so we still
leave this use case alive.
> It's not really what I was saying.
>
> What I said is that people will keep using Kate, KDevelop, QtCreator,
> emacs, vim or whatever they want to create their plasmoids. You're
> imposing a dependency by neglecting the current users of those tool. I
> think that's generally not good.
Can you explain to me how I will manage that?
If I move those tools to the plasmate repo, why the life of those people
will
get worst? Is it because they will have to build one more repo which needs
1 minute?
--
Giorgos Tsiapaliokas (terietor)
KDE Developer
terietor.gr
[Attachment #5 (text/html)]
<div dir="ltr"><br><br><div class="gmail_quote">On 20 August 2012 02:15, 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"> That's a \
packaging decision. The Plasmate should depend on the plasma \
tools.</blockquote><div><br></div><div>The Plasmate IDE will depend on the plasma \
tools, either if they are in the kde-workspace or in</div><div>the plasmate repo. \
</div> <div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"> > From a \
technical point of view,<br> > those are a few issues for which we have to move \
the plasma tools inside<br> > plasmate,<br>
> 1. How can someone embed a binary inside a qwidget?<br>
> Example: How can I embed the binary named plasmoidviewer inside \
plasmate's<br> > MainWindow::CentralContainer::CentralContainer??<br>
</div>I'm unsure what you mean. You can embed a plasma view. You won't \
ever<br> embed the plasmoidviewer, maybe you can compile the same code twice,<br>
but it's not the same!<br>
<div class="im"><br>
><br>
> 2. Some tools when they are used as standalone applications require a few<br>
> extra ui stuff.<br>
> Example: when I execute plasmaremoteinstaller from plasmate I have a known<br>
> source directory for my plasmoid(thanks to plasmate), but when<br>
> I execute it as a standalone application I don't., so I need an extra<br>
> kurlrequester. How can I hide a kurlrequester from a binary?<br>
</div>Well, you can add arguments to the binary, for example.<br>
<div class="im"><br>
><br>
> 3. duplication of code, plasmoidviewer vs plasma-previewer<br>
</div>You can expose a library.</blockquote><div><br></div><div>I believe that the \
idea of moving the tools is much more better than</div><div>those \
workarounds.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">
>> 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>
><br>
><br>
> When you say "plasmate" do you refer to the ide named plasmate or \
the<br> > repository?<br>
</div>The IDE.</blockquote><div><br></div><div>Those tools will still be accessible \
as standalone applications, so we still</div><div>leave this use case \
alive.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> It's not really what I was \
saying.<br> <br>
What I said is that people will keep using Kate, KDevelop, QtCreator,<br>
emacs, vim or whatever they want to create their plasmoids. You're<br>
imposing a dependency by neglecting the current users of those tool. I<br>
think that's generally not good.</blockquote></div><br>Can you explain to me how \
I will manage that?<br>If I move those tools to the plasmate repo, why the life of \
those people will<div>get worst? Is it because they will have to build one more repo \
which needs 1 minute?<br clear="all"> <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>
_______________________________________________
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