* move the console in another process, but there may be too much that would have to be exposed trough dbus for that
+1 2014-03-31 12:09 GMT+02:00 Michael Palimaka <kensing...@gentoo.org>: > On 02/27/2014 01:00 AM, Martin Gräßlin wrote: >> On Wednesday 26 February 2014 12:56:41 Marco Martin wrote: >>> On Wednesday 26 February 2014 11:36:16 Martin Gräßlin wrote: >>>> On Wednesday 26 February 2014 11:27:04 Marco Martin wrote: >>>>> Hi all, >>>>> yesterday i was toying with porting the javascript interactive console >>>>> for >>>>> plasma-shell. >>>>> one thing that i stumbled upon is how much dependencies the thing has. >>>>> >>>>> apart the usual removal of kde4support, it depends from new things like >>>>> ktexteditor,ktextbrowser etc. >>>>> >>>>> so, it would bump up the dependencies of the plasma-framework repo even >>>>> more and i don't really like it. >>>>> so, there could be alternatives: >>>>> >>>>> * rewrite it with less dependencies (tough it need kate as the editor to >>>>> not suck..) >>>>> * split the shell out of the repo >>>> >>>> What's the reason of having the shell in the plasma-framework? Shouldn't >>>> it >>>> be in kde-workspace in the first place? >>> >>> so, opinion poll: >>> move plasma-shell to kde-workspace? (btw, is kde-workspace the final >>> nameit's going to have? what is the status of the splitting it?) >> >> Right it could be put together with the other plasma parts when splitting and >> maybe it doesn't make much sense to change anything prior to splitting. > > Now that kde-workspace is split, does it make more sense for > plasma-shell to be moved to one of the new plasma-desktop/workspace repos? > > > _______________________________________________ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel