[Development] Controlling QML Imports

Alan Alpert 416365416c at gmail.com
Wed Dec 12 19:30:03 CET 2012

On Mon, Dec 10, 2012 at 7:23 PM, Alan Alpert <416365416c at gmail.com> wrote:
> For finer-grained control over QML it would make sense to have an API
> allowing import restrictions. Two usecases come to mind, platform
> security contexts and scriptable applications. Platform security
> contexts is about when a platform using QML for the applications wants
> to have restricted capabilities, like android does, so that packaged
> applications can be restricted to just the capabilities the package
> says it needs. The scriptable applications usecase is for if you want
> to make your application scriptable with QML - you probably only want
> the scripts to use your application provided functionality and not
> create popup windows (this is why Window gets it own QtQuick.Window
> import).

Okay, forget about the platform security context usecase. That's much
more complicated than we seem to need right now, and I'm fine with
leaving that to the platforms. Let's just consider the other usecase
for now.

For the scriptable application usecase, like Jan has and like Plasma
has, is the suggested API helpful? Does the proposed restriction model
work, or is there an easier way?

Alan Alpert

More information about the Development mailing list