Re: [Development] Qt and IoT infographic

On Tuesday, 29 August 2017 12:41:25 PDT Jean-Michaël Celerier wrote: > > Research shows NO ONE deploys Arduino for real products. It's a maker toy, > > stuff hobbyists use to make one-off things and some professional makers > > use > > for initial prototyping. When they get serious, Arduino goes

Re: [Development] Qt and IoT infographic

> Research shows NO ONE deploys Arduino for real products. It's a maker toy, stuff hobbyists use to make one-off things and some professional makers use for initial prototyping. When they get serious, Arduino goes out the window and they get real boards. Sure, but if you can't start prototyping

Re: [Development] Qt and IoT infographic

On Tuesday, 29 August 2017 10:35:05 PDT Jason H wrote: > I think the ideal tech solution here is not to do one or the other, rather > both, in a layered approach. Use the HTTP/REST and provide a translation > layer to CoAP. They make a statement about it being really close, so it > shouldn't be

Re: [Development] Qt and IoT infographic

29.08.2017, 19:00, "Thiago Macieira" : > On Tuesday, 29 August 2017 02:43:44 PDT Shawn Rutledge wrote: >>  And yet it has a web server for serving up either a human-readable page or >>  JSON on demand, and it also pushes data to a central server periodically. > > Is

Re: [Development] Qt and IoT infographic

> Sent: Tuesday, August 29, 2017 at 12:00 PM > From: "Thiago Macieira" > To: development@qt-project.org > Subject: Re: [Development] Qt and IoT infographic > > On Tuesday, 29 August 2017 02:43:44 PDT Shawn Rutledge wrote: > > And yet it has a web server for serving up

Re: [Development] Qt and IoT infographic

  This. +1*100 Sent: Tuesday, August 29, 2017 at 4:20 AM From: "Jean-Michaël Celerier" To: "Thiago Macieira" Cc: development@qt-project.org Subject: Re: [Development] Qt and IoT infographic > If you're going to communicate with a

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

On Tuesday, 29 August 2017 01:10:53 PDT René J.V. Bertin wrote: > Which we just rediscovered :) Funny though, apparently 1 misdirected > startTimer() call can turn any application in a CPU hog that burns cycles > without ever doing anything. Wouldn't it be safer for QObject::timerEvent() > to kill

Re: [Development] Qt and IoT infographic

On Tuesday, 29 August 2017 02:43:44 PDT Shawn Rutledge wrote: > And yet it has a web server for serving up either a human-readable page or > JSON on demand, and it also pushes data to a central server periodically. Is that a static JSON? Because if you need to compose the data on the fly, you

Re: [Development] Qt and IoT infographic

On Tuesday, 29 August 2017 01:44:34 PDT Edward Welbourne wrote: > Thiago: > >> If you're going to communicate with a tiny MCU connected over a mesh > >> network like 6LoWPAN/Thread, you won't be using TCP. Much less HTTP. > > and you'll want that MCU running something light-weight in C++, not a >

Re: [Development] QLowEnergyController and obsolete ctor

On Tue, 29 Aug 2017 11:18:02 + Alex Blasche wrote: > Hi Martin, > > > -Original Message- > > From: Development [mailto:development- > > bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Martin Koller > > > In Qt 5.9 I find that the following

Re: [Development] QLowEnergyController and obsolete ctor

Hi Martin, > -Original Message- > From: Development [mailto:development- > bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Martin Koller > In Qt 5.9 I find that the following ctor is marked as obsolete: > > explicit QLowEnergyController(const QBluetoothAddress , >

Re: [Development] Maintainers, your actions needed: Change files for Qt 5.6.3

> -Original Message- > From: André Hartmann [mailto:andre.hartm...@iseg-hv.de] > Sent: tiistai 29. elokuuta 2017 9.25 > To: Jani Heikkinen ; development@qt-project.org > Subject: Re: [Development] Maintainers, your actions needed: Change files > for Qt 5.6.3 > > Hi

Re: [Development] Qt and IoT infographic

> On 29 Aug 2017, at 10:44, Edward Welbourne wrote: > > Thiago: >>> If you're going to communicate with a tiny MCU connected over a mesh >>> network like 6LoWPAN/Thread, you won't be using TCP. Much less HTTP. > > and you'll want that MCU running something light-weight

Re: [Development] Qt and IoT infographic

Thiago: >> If you're going to communicate with a tiny MCU connected over a mesh >> network like 6LoWPAN/Thread, you won't be using TCP. Much less HTTP. and you'll want that MCU running something light-weight in C++, not a web-bloat thing. So Qt is just the thing for the job. (... and I had to

Re: [Development] Qt and IoT infographic

> If you're going to communicate with a tiny MCU connected over a mesh network like 6LoWPAN/Thread, you won't be using TCP. Much less HTTP. What makes me a bit sad is that if Qt's not doing it, then we end up having to put up with bloated stuff like Node.JS on beagleboard or raspberries :

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

On Tuesday August 29 2017 02:02:59 Gabriel de Dietrich wrote: >FYI: QCocoaMenu: Stop update timer >(Merged) Thanks for the heads-up. > >On Aug 29, 2017, at 9:00 AM, Thiago Macieira >> wrote: >

Re: [Development] Maintainers, your actions needed: Change files for Qt 5.6.3

Hi Jani, I have some comments to the change file process: 1. The commit message is "Add change file for Qt 5.6.3" but it should be "Add changes file for Qt 5.6.3" (plural) 2. In the last releases, this initial version was WIP, so the maintainer needed to adjust the message so it could be

Re: [Development] Qt and IoT infographic

On Mon, 28 Aug 2017 21:41:15 +0200, Jean-Michaël Celerier wrote: > * apparently QQuickWindow has some ties to the QML engine but in my > experience you can just create new QQuickItem from c++ and add them as > child of the rootItem and it works. F.e. https://github.com/uwerat/qskinny does