move plasma tools to plasmate

Giorgos Tsiapaliokas terietor at gmail.com
Mon Aug 20 08:37:16 UTC 2012


On 20 August 2012 02:15, Aleix Pol <aleixpol at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20120820/2f3c9688/attachment.html>


More information about the Plasma-devel mailing list