[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: FYI: Platform content discussion in Qt
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2013-03-27 17:29:54
Message-ID: 1599872.QUZ9UI3tgt () freedom
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tuesday, March 26, 2013 13:53:29 Alan Alpert wrote:
> > import org.kde.plasma.components 1.0 as...
> > 
> > and import the "right" set, but the ideal way is (if we are importing
> > touch
> > components) to have a set of "just" the components that are rewritten for
> > touchscreen, while falling back to the common ones for everything else,
> > that now we can't do, so we have the whole set installed two times and we
> > change the import paths depending from the platform, and that's not
> > optimal.
> If the selectors were implemented at a Qt or QML level, then you could
> easily apply them in your imports the same as you would in plasma
> packages. So that problem would be solved too.

Yes, this would help. It would mean patching the QML parser itself which does 
the imports, but that's not rocket science.

The imports issue is a bit bigger than this as we also need the ability to 
deny imports or change them based on runtime permissions (allowing some QML to 
access org.foo.screwWithTheFilesystem and others not, for instance)

It would be nice to design a more complete solution for the weaknesses 
inherent in imports before we start organically adding incremental 
improvements?

-- 
Aaron J. Seigo
["signature.asc" (application/pgp-signature)]

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread]