Re: testing a plasma applet with plasmoid viewer despite PackageUrlInterceptor

2015-01-05 Thread Sebastian Kügler
On Sunday, December 28, 2014 21:21:12 Philipp A. wrote: when using a custom interceptor to circumvent it, i still get strange errors. can someone help? QML debugging is enabled. Only use this in a safe environment. Constructing a KPluginInfo object from old style JSON. Please use

Re: testing a plasma applet with plasmoid viewer despite PackageUrlInterceptor

2015-01-05 Thread Sebastian Kügler
On Monday, January 05, 2015 13:01:41 Philipp A. wrote: doesn’t change the fact that i see nothing but a blank plasma applet container. (only the border, nothing in it) No errors or warnings hidden in the slurry of output? 2015-01-05 11:13 GMT+01:00 Sebastian Kügler se...@kde.org: On Sunday,

Re: testing a plasma applet with plasmoid viewer despite PackageUrlInterceptor

2015-01-05 Thread Philipp A.
well, you saw it: https://www.mail-archive.com/plasma-devel@kde.org/msg36985.html basically: file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Plasma/FocusFrameStyle.qml: File not found file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Base/ButtonStyle.qml:153:31: QML Item: Binding loop detected for

Re: testing a plasma applet with plasmoid viewer despite PackageUrlInterceptor

2015-01-02 Thread Philipp A.
*bump* nobody got an idea? 2014-12-29 13:45 GMT+01:00 Philipp A. flying-sh...@web.de: 2014-12-29 10:23 GMT+01:00 Marco Martin notm...@gmail.com: does it load when installed? yes. i think it’s the way that plasmoidviewer loads it that breaks, see my other mail, where i changed the

Re: testing a plasma applet with plasmoid viewer despite PackageUrlInterceptor

2014-12-29 Thread Marco Martin
On Saturday 27 December 2014, Philipp A. wrote: Hi, i’m developing a plasma wiget with C++ plugin. consistent with how upstream packages do it, with my package being called `org.kde.plasma.steam`, the plugin is called `org.kde.plasma.private.steam`. i try to load my plasmoid from its

Re: testing a plasma applet with plasmoid viewer despite PackageUrlInterceptor

2014-12-29 Thread Philipp A.
2014-12-29 10:23 GMT+01:00 Marco Martin notm...@gmail.com: does it load when installed? yes. i think it’s the way that plasmoidviewer loads it that breaks, see my other mail, where i changed the interceptor to allow these requests and still get errors: 2014-12-28 21:21 GMT+01:00 Philipp A.

Re: testing a plasma applet with plasmoid viewer despite PackageUrlInterceptor

2014-12-28 Thread Philipp A.
but then i have to compile the whole plasma framework. that’s far out of scope of a plasma applet :/ 2014-12-28 0:57 GMT+01:00 David Edmundson da...@davidedmundson.co.uk: On Sat, Dec 27, 2014 at 10:11 PM, Philipp A. flying-sh...@web.de wrote: Hi, i’m developing a plasma wiget with C++

Re: testing a plasma applet with plasmoid viewer despite PackageUrlInterceptor

2014-12-28 Thread Philipp A.
code is here btw: https://github.com/flying-sheep/steam-plasmoid 2014-12-28 17:41 GMT+01:00 Philipp A. flying-sh...@web.de: but then i have to compile the whole plasma framework. that’s far out of scope of a plasma applet :/ 2014-12-28 0:57 GMT+01:00 David Edmundson

Re: testing a plasma applet with plasmoid viewer despite PackageUrlInterceptor

2014-12-28 Thread Philipp A.
aha, so the problem seems to be that when loaded via plasmoidviewer m_package.metadata().pluginName() == org.kde.desktopcontainment when using a custom interceptor to circumvent it, i still get strange errors. can someone help? QML debugging is enabled. Only use this in a safe environment.

Re: testing a plasma applet with plasmoid viewer despite PackageUrlInterceptor

2014-12-27 Thread David Edmundson
On Sat, Dec 27, 2014 at 10:11 PM, Philipp A. flying-sh...@web.de wrote: Hi, i’m developing a plasma wiget with C++ plugin. consistent with how upstream packages do it, with my package being called `org.kde.plasma.steam`, the plugin is called `org.kde.plasma.private.steam`. i try to load