Re: private import names

2013-09-25 Thread David Edmundson
On Wed, Sep 25, 2013 at 10:41 AM, Sebastian Kügler wrote: > Hey, > > Import names. As we can't use our setContextProperty tricks in subclassed > Applets anymore, we'll have to resort more often to installing imports that > are very specific (i.e. not libraries per se, but more like C++ portions >

Re: private import names

2013-09-25 Thread Marco Martin
On Wednesday 25 September 2013 12:17:52 Sebastian Kügler wrote: > > so something like private.org.kde.plasma.widgetname or > > .org.kde.private.plasma.widgetname > > The leading . is purposeful? ah, no ;) > > the first would take a "private" at the first level, that maybe is not too > > nice, bu

Re: private import names

2013-09-25 Thread Sebastian Kügler
On Wednesday, September 25, 2013 12:07:55 Marco Martin wrote: > On Wednesday 25 September 2013 11:41:36 Sebastian Kügler wrote: > > Import names. As we can't use our setContextProperty tricks in subclassed > > Applets anymore, we'll have to resort more often to installing imports > > that > > are v

Re: private import names

2013-09-25 Thread Marco Martin
On Wednesday 25 September 2013 11:41:36 Sebastian Kügler wrote: > Hey, > > Import names. As we can't use our setContextProperty tricks in subclassed > Applets anymore, we'll have to resort more often to installing imports that > are very specific (i.e. not libraries per se, but more like C++ porti

Re: private import names

2013-09-25 Thread Bhushan Shah
Hello! On Wed, Sep 25, 2013 at 3:11 PM, Sebastian Kügler wrote: > I suggest to use "org.kde.plasma.private.$widgetname" If I remember notmart suggested me to use, private.$pluginname Log : * notmart would like private.org.kde.icon, and in general private."plasmoid plugin name" Thanks! ___