On Mon, Dec 10, 2012 at 7:23 PM, Alan Alpert <4163654...@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 abo
On Tue, Dec 11, 2012 at 5:27 PM, Jan Kundrát wrote:
> On Tuesday, 11 December 2012 04:23:51 CEST, Alan Alpert 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 app
> From: Alan Alpert <4163654...@gmail.com>
>Sent: Tuesday, December 11, 2012 2:46 PM
>Subject: Re: [Development] Controlling QML Imports
>
>On Tue, Dec 11, 2012 at 7:52 AM, Thiago Macieira wrote:
>> On terça-feira, 11 de dezembro de 2012 15.44.37, Aaron J. Seigo
On Tue, Dec 11, 2012 at 7:52 AM, Thiago Macieira wrote:
> On terça-feira, 11 de dezembro de 2012 15.44.37, Aaron J. Seigo wrote:
>> > > > loading of native plugins from the application?
>>
>> Yes, but not native plugins installed by the QML applications. In such a
>> situation we need to be able t
On terça-feira, 11 de dezembro de 2012 15.44.37, Aaron J. Seigo wrote:
> > > > loading of native plugins from the application?
>
> Yes, but not native plugins installed by the QML applications. In such a
> situation we need to be able to ensure that applications which say "I will
> access this list
(sorry for interjecting a reply to multiple emails here, but i just got back
on this list specifically to discuss QML matters.)
On Tuesday, December 11, 2012 14:21:28 Laszlo Papp wrote:
> On Tue, Dec 11, 2012 at 1:11 PM, Knoll Lars wrote:
> > On Dec 11, 2012, at 5:30 AM, Thiago Macieira
> > > c
On Tue, Dec 11, 2012 at 1:11 PM, Knoll Lars wrote:
>
> On Dec 11, 2012, at 5:30 AM, Thiago Macieira
> wrote:
>
> > On terça-feira, 11 de dezembro de 2012 13.43.08, Lincoln Ramsay wrote:
> >> On 11/12/12 13:23, Alan Alpert wrote:
> >>> Any comments on adding an API like this?
> >>>
> >>> Are ther
On Dec 11, 2012, at 5:30 AM, Thiago Macieira wrote:
> On terça-feira, 11 de dezembro de 2012 13.43.08, Lincoln Ramsay wrote:
>> On 11/12/12 13:23, Alan Alpert wrote:
>>> Any comments on adding an API like this?
>>>
>>> Are there any other usecases which this might need to support?
>>
>> If we'
On terça-feira, 11 de dezembro de 2012 13.43.08, Lincoln Ramsay wrote:
> On 11/12/12 13:23, Alan Alpert wrote:
> > Any comments on adding an API like this?
> >
> > Are there any other usecases which this might need to support?
>
> If we're talking device security and restrictions policy... then ple
On Mon, Dec 10, 2012 at 7:43 PM, Lincoln Ramsay wrote:
> On 11/12/12 13:23, Alan Alpert wrote:
>> Any comments on adding an API like this?
>>
>> Are there any other usecases which this might need to support?
>
> If we're talking device security and restrictions policy... then please
> make this so
On 11/12/12 13:23, Alan Alpert wrote:
> Any comments on adding an API like this?
>
> Are there any other usecases which this might need to support?
If we're talking device security and restrictions policy... then please
make this something that can fail "softly" at runtime.
I know most mobile pl
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 capabili
12 matches
Mail list logo
