private import names

[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++ portions
> needed for a certain applet). Examples are Kickoff, Icon, and the dreaded
> systray. I suggest to use "org.kde.plasma.private.$widgetname" for this, so
> we can filter for these imports later on, when our import security has been
> implemented. Objections? (No objections means that I'll change it.)

first,
get out of my mind :p

I was thinking to something even more radical, that we can try to have 
consistent in whole kde (since i suspect a lot of other modules will have qml 
imports such as kdepim, or many other apps, such as games, kdeedu...)

so something like private.org.kde.plasma.widgetname or 
.org.kde.private.plasma.widgetname

the first would take a "private" at the first level, that maybe is not too 
nice, but the nice part is that it would always be private.$widgetpluginname 
that has some beauty (and easy filtering) in it

-- 
Marco Martin