> Sent: Monday, June 05, 2017 at 3:26 PM
> From: "Lorn Potter" <lorn.pot...@gmail.com>
> To: "Jason H" <jh...@gmx.com>
> Cc: development@qt-project.org
> Subject: Re: [Development] Future of Qt on Web?
>
>
>
> On 06/06/2017 12:20 AM
On 06/06/2017 12:20 AM, Jason H wrote:
>
>
>> Sent: Monday, June 05, 2017 at 12:34 AM
>> From: "Lorn Potter" <lorn.pot...@gmail.com>
>> To: development@qt-project.org
>> Subject: Re: [Development] Future of Qt on Web?
>>
>>
>>
>
05.06.2017, 17:20, "Jason H" <jh...@gmx.com>:
>> Sent: Monday, June 05, 2017 at 12:34 AM
>> From: "Lorn Potter" <lorn.pot...@gmail.com>
>> To: development@qt-project.org
>> Subject: Re: [Development] Future of Qt on Web?
>
> Sent: Monday, June 05, 2017 at 12:34 AM
> From: "Lorn Potter" <lorn.pot...@gmail.com>
> To: development@qt-project.org
> Subject: Re: [Development] Future of Qt on Web?
>
>
>
> On 06/05/2017 07:00 AM, Jason H wrote:
> > While Qt is not a we
Op ma 5 jun. 2017 06:35 schreef Lorn Potter :
>
>
> On 06/05/2017 07:00 AM, Jason H wrote:
> > While Qt is not a web framework, over time there have been efforts to
> use it on the web (outlined below).
> >
> > Given that Chrome is dropping NaCL (
>
On 06/05/2017 07:00 AM, Jason H wrote:
> While Qt is not a web framework, over time there have been efforts to use it
> on the web (outlined below).
>
> Given that Chrome is dropping NaCL
> (http://www.tomshardware.com/news/chrome-deprecates-pnacl-embraces-webassembly,34583.html)
> and the