Re: [Interest] 5.8 Features?

[ekke]

thx Maurice,

Am 22.06.16 um 12:22 schrieb Maurice Kalinowski:
>
> > Highest prio from my personal perspective:
>
> > >> - Background processing API
>
> > >> - In-app Notifications: local, remote
>
> > + add Windows Store to Qt Purchasing module
>
there's more missing:
- avoid flicker for android apps out-of-the-box
- easy way to 'share' content with/from other apps (Intents, Deep
Linking) Android, iOS
such common use-cases should be abstracted and available via Qt API

coming from BlackBerry 10 Cascades/QML APP Development I'm astonished
how many common mobile tasks are missing

I want to motivate my enterprise customers to use Qt for mobile
x-platform development
they're comparing with Xamarin, Ionic, Angular ...

I still believe Qt is the best solution for mobile x platform and hope
there will be really progress on this
esp. after providing QtQuickControls2 Material style for great looking apps

ekke
>
>  
>
> https://codereview.qt-project.org/#/c/149602/
>
> https://codereview.qt-project.org/#/c/162992/
>
>  
>
> ;)
>
>  
>
> Maurice
>
>  
>
>  
>
> *From:*Interest
> [mailto:interest-bounces+maurice.kalinowski=qt...@qt-project.org] *On
> Behalf Of *Matthias Degenkolb via Interest
> *Sent:* Wednesday, June 22, 2016 11:25 AM
> *To:* ekke 
> *Cc:* interest@qt-project.org
> *Subject:* Re: [Interest] 5.8 Features?
>
>  
>
> I fully agree to ekke's and Jason's wishes. The features mentioned are
> all topics I also miss urgently since our first app development tests
> with Qt ..
>
> Not having cross-platform access to those "standard" mechanisms for
> mobile OS really makes me wonder whether my next projects will be
> based on Qt ...
>
>  
>
> Highest prio from my personal perspective:
>
> >> - Background processing API
> >> - In-app Notifications: local, remote
>
> + add Windows Store to Qt Purchasing module
>
>  
>
>  
>
> 2016-06-22 10:45 GMT+02:00 ekke  >:
>
> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
>
> > Den 21-06-2016 kl. 22:55 skrev Jason H:
> >> I feel like the last few releases have been run by the trolls, and
> >> not the users of Qt. I was hoping open governance would enable the
> >> community to direct Qt development, but I seem to have
> misinterpreted
> >> what it means. I'm looking for what's going into 5.8.. not much
> >> listed on the releases page.
> >>
> >> I'd like to suggest that mobile get some much needed love.
> >> - Application state transitions; Foreground, background
> >> - Background processing API
> >> - Screen wake lock API
> >> - In-app Notifications: local, remote
> >>
> >> While I have those characterized as "mobile" there are things like
> >> notifications occurring on desktop platforms.
> >>
> >> Any thoughts?
> >
> > There's only one reason why you don't see more features for the
> mobile
> > parts: There are not enough developers on it. And that's not because
> > QtCompany is doing anything wrong, they just have their priorities
> > different from what you have.
> >
> > Personally I don't care about mobile at all. I haven't had a mobile
> > customer since 2011 and I don't see that changing. My focus is
> almost
> > entirely on Linux embedded and Windows desktop. Those are the areas
> > where a lot of applications are written.
> >
> > I'd love to see the mobile platforms thrive. But unless you Qt users
> > start becoming Qt developers and contribute to it, I don't see that
> > happening.
>
> hmmm
> the only reason for me to use Qt is mobile
> using new Qt Quick Controls 2 Qt is a great platform for mobile app
> development and I hope many new developers will start with Qt on
> mobile
> to make this easier I'm writing example apps and a blog series
> http://j.mp/qt-x
>
> I really hope that there will be development on the topics Jason H
> mentioned above
>
> ekke
>
> >
> > Bo Thorsen,
> > Director, Viking Software.
> >
>
> ___
> Interest mailing list
> Interest@qt-project.org 
> http://lists.qt-project.org/mailman/listinfo/interest
>
>  
>


-- 

ekke (ekkehard gentz)

independent software architect
international development native mobile business apps
BlackBerry 10 | Qt Mobile (Android, iOS)
workshops - trainings - bootcamps

*BlackBerry Elite Developer
BlackBerry Platinum Enterprise Partner*

max-josefs-platz 30, D-83022 rosenheim, germany
mailto:e...@ekkes-corner.org
blog: http://ekkes-corner.org
apps and more: http://appbus.org

twitter: @ekkescorner
skype: ekkes-corner
LinkedIn: http://linkedin.com/in/ekkehard/
Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490

___
Interest mailing list
Interest@qt-project.org

Re: [Interest] [Windows][opengl] How graphic card is choosen on a portable computer with many?

[Xavier Bigand]

I think I finally found the solution on stackoverflow

For Nvidia :

// enable optimus!extern "C" {
_declspec(dllexport) DWORD NvOptimusEnablement = 0x0001;}

And for AMD :

extern "C"
  {
__declspec(dllexport) int AmdPowerXpressRequestHighPerformance = 1;
  }


Now I just need to found the corresponding configuration to test.

If it works it would be just perfect.

2016-06-22 23:44 GMT+02:00 Jérôme Godbout :

> I'm guessing ActiveX may have more options to select the proper card but I
> may be wrong on this. I'm also curious about this, we are supporting Intel
> GPU but since we have an heavy CAD application, we always switch the card
> to the AMD/NVidia one. I would love an option or way to select this before
> the first OpenGL context is created too, that would be a lovely features.
> Not sure if other platforms allow this??? I known macOS can switch video
> card, but I think it's transparent to the user or application (maybe that's
> explain the old OpenGL version they are using!).
>
> I'm pretty sure it must be possible under Linux, but I never try it or did
> it.
>
> On Wed, Jun 22, 2016 at 3:49 PM, Xavier Bigand 
> wrote:
>
>> Wow, it seems complicated. I prefer a transparent solution for users, I
>> think that it will be relatively easy to find an OpenGL feature to filter
>> the cards (but I need to get a such configuration before :-().
>>
>> I thought that it could be similar than scanning screen or something like
>> that. I am expecting that we could select the right card during the window
>> or the opengl context creation.
>> I am curious on how video games are doing to be always launched on the
>> right card.
>>
>>
>> 2016-06-22 21:25 GMT+02:00 Jérôme Godbout :
>>
>>> I don't think you can select this before the aplication is launch, it's
>>> Windows and the video driver that choose that for you. You could however,
>>> have a small launcher or a checker on application launch with the OpenGL
>>> card used (maybe inspect the QSurface format or anything that could point
>>> to if the wanted OpenGL features is available).
>>>
>>> you can execute the following batch script to get the video card
>>> / VideoCardIdentifier.bat
>>> *@echo off*
>>> *for /F "tokens=* skip=1" %%n in ('WMIC path Win32_VideoController get
>>> Name ^| findstr "."') do set GPU_NAME=%%n*
>>> *echo %GPU_NAME%*
>>> / END VideoCardIdentifier.bat
>>>
>>> should output something like that:
>>> *AMD Radeon R9 200 Series*
>>>
>>> use a regex to parse the output to detect the available card type.
>>>
>>> You could show an error dialog and stop at this point and tell the
>>> requirement to your user. I would point. depending on the nvidia or AMD
>>> card detected, you could try to launch the proper panel and display the
>>> instruction to change it or give a link to do it.
>>>
>>>
>>> On Wed, Jun 22, 2016 at 12:35 PM, Xavier Bigand <
>>> flamaros.xav...@gmail.com> wrote:
>>>
 Hi,

 Some of users can't launch our application because there computer have
 2 graphic cards. To fix the issue they have to force the card made for
 gaming to be used with our software.
 Our application is made with Qt and QML, but we have our custom 3D
 engine that do not work on intel integrated GPU. One particularity of our
 engine is that it doesn't request a draw every time dislike games.


 Is there a way for us to make the application able to discover the best
 graphic card and force his usage?


 --
 Xavier

 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


>>>
>>
>>
>> --
>> Xavier
>>
>
>


-- 
Xavier
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interest Digest, Vol 57, Issue 26

[Jakub Michałowski]

Szanowni Państwo,

Dziękuję za przesłanie wiadomości.

W dniach od 19 do 24 czerwca 2016 roku jestem poza biurem w związku z 
międzynarodowymi targami Firex w Londynie.

W sprawach szkoleń proszę o kontakt z panem Krzysztofem Nowakowskim pod numerem 
52 36 39 265 lub z działem wsparcia technicznego pod numerem 52 36 39 261.

Realizacją zapytań ofertowych zajmuje się nasz dystrybutor AAT Holding S.A. 
Listę oddziałów dystrybutora można uzyskać na stronie www.aat.pl.

W sprawach nieprawidłowości i usterek proszę o kontakt z działem serwisu pod 
numerem 52 36 39 375.

W sprawach pomocy technicznej na temat obecnych w ofercie urządzeń proszę o 
kontakt z naszym działem wsparcia technicznego pod numerem telefonu: 52 36 39 
261 lub adresem e-mail: polona...@polon-alfa.pl

Serdecznie pozdrawiam

Jakub Michałowski
Młodszy Konstruktor

Polon-Alfa Spółka z ograniczoną odpowiedzialnością Sp. k.
85-861 Bydgoszcz, ul. Glinki 155
Tel.  +48 52 36 39 265
Fax  +48 52 36 39 264
Kom.  +48 601 380 401
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] [Windows][opengl] How graphic card is choosen on a portable computer with many?

[Jérôme Godbout]

I'm guessing ActiveX may have more options to select the proper card but I
may be wrong on this. I'm also curious about this, we are supporting Intel
GPU but since we have an heavy CAD application, we always switch the card
to the AMD/NVidia one. I would love an option or way to select this before
the first OpenGL context is created too, that would be a lovely features.
Not sure if other platforms allow this??? I known macOS can switch video
card, but I think it's transparent to the user or application (maybe that's
explain the old OpenGL version they are using!).

I'm pretty sure it must be possible under Linux, but I never try it or did
it.

On Wed, Jun 22, 2016 at 3:49 PM, Xavier Bigand 
wrote:

> Wow, it seems complicated. I prefer a transparent solution for users, I
> think that it will be relatively easy to find an OpenGL feature to filter
> the cards (but I need to get a such configuration before :-().
>
> I thought that it could be similar than scanning screen or something like
> that. I am expecting that we could select the right card during the window
> or the opengl context creation.
> I am curious on how video games are doing to be always launched on the
> right card.
>
>
> 2016-06-22 21:25 GMT+02:00 Jérôme Godbout :
>
>> I don't think you can select this before the aplication is launch, it's
>> Windows and the video driver that choose that for you. You could however,
>> have a small launcher or a checker on application launch with the OpenGL
>> card used (maybe inspect the QSurface format or anything that could point
>> to if the wanted OpenGL features is available).
>>
>> you can execute the following batch script to get the video card
>> / VideoCardIdentifier.bat
>> *@echo off*
>> *for /F "tokens=* skip=1" %%n in ('WMIC path Win32_VideoController get
>> Name ^| findstr "."') do set GPU_NAME=%%n*
>> *echo %GPU_NAME%*
>> / END VideoCardIdentifier.bat
>>
>> should output something like that:
>> *AMD Radeon R9 200 Series*
>>
>> use a regex to parse the output to detect the available card type.
>>
>> You could show an error dialog and stop at this point and tell the
>> requirement to your user. I would point. depending on the nvidia or AMD
>> card detected, you could try to launch the proper panel and display the
>> instruction to change it or give a link to do it.
>>
>>
>> On Wed, Jun 22, 2016 at 12:35 PM, Xavier Bigand <
>> flamaros.xav...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Some of users can't launch our application because there computer have 2
>>> graphic cards. To fix the issue they have to force the card made for gaming
>>> to be used with our software.
>>> Our application is made with Qt and QML, but we have our custom 3D
>>> engine that do not work on intel integrated GPU. One particularity of our
>>> engine is that it doesn't request a draw every time dislike games.
>>>
>>>
>>> Is there a way for us to make the application able to discover the best
>>> graphic card and force his usage?
>>>
>>>
>>> --
>>> Xavier
>>>
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/interest
>>>
>>>
>>
>
>
> --
> Xavier
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] universal builds on OS X

[Thiago Macieira]

On quarta-feira, 22 de junho de 2016 09:45:17 PDT Kevin Mcintyre wrote:
> Is it possible to build for IPhone from Ubuntu?  Any tutorials of starter
> docs would be greatly appreciated.

The tricky part is installing the toolchain. As far as I know, Apple only 
provides it for OS X/macOS.

So if you don't own a Mac, you can't develop for iPhone.

I seriously don't get how people put up with that... but Apple gets away with 
it.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Tuukka Turunen]

> -Original Message-
> From: Interest [mailto:interest-bounces+tuukka.turunen=qt.io@qt-
> project.org] On Behalf Of Michael R Nelson
> Sent: keskiviikkona 22. kesäkuuta 2016 19.11
> To: interest@qt-project.org
> Subject: Re: [Interest] 5.8 Features?
> 
> I have to say I completely agree with Jason's sentiment here. I'm a
> commercial customer since early Qt 5.0. I bought with the belief mobile
> support would continue to grow, and not require me to step into native
> platform coding, nor require me to build custom versions of Qt to get around
> shortcomings that never get fixed.
> 

Hi,

Perhaps the pace has been slower than you wanted, or maybe the developed items 
different, but the mobile support of Qt has developed steadily with each 
release. Not only are we keeping pace with the mobile developments supporting 
new platform versions as they are available, but there has also been steady 
increase of the API parity and maturity. One of the big investments benefiting 
mobile has been to support WinRT / Windows 10, which of course does not benefit 
those who are only interested in iOS or Android. Qt is well committed in 
keeping and improving the position as the leading cross-platform toolkit across 
desktop-mobile-embedded. 

Yours,

Tuukka


> Mike
> 
> -Original Message-
> From: Interest [mailto:interest-bounces+mnelson=sutron.com@qt-
> project.org] On Behalf Of Jason H
> Sent: Wednesday, June 22, 2016 9:40 AM
> To: Sze Howe Koh 
> Cc: interest@qt-project.org
> Subject: Re: [Interest] 5.8 Features?
> 
> 
> > Subject: Re: [Interest] 5.8 Features?
> >
> > On 22 June 2016 at 09:34, Thiago Macieira 
> wrote:
> > >
> > > On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > > > I feel like the last few releases have been run by the trolls, and
> > > > not the users of Qt. I was hoping open governance would enable the
> > > > community to direct Qt development, but I seem to have
> misinterpreted what it means.
> >
> > See https://wiki.qt.io/The_Qt_Governance_Model
> >
> > "Open governance" means that all members of the community can raise
> > proposals and vote on them. It is also a meritocratic system (as
> > opposed to democratic), which means more weight is given to members of
> > higher rank. Put simply, rank is gained through contributions and
> > commitment to the Qt Project.
> 
> Where and when does this voting occur? I've been vocal about improving Qt
> on mobile since mobile was an option. I've been hardcore on the
> shortcomings for about 20 months. During that time, I saw 5.6 get released,
> 5.7 get released at the same time as 5.6.1, and a lot of meaningless (to me)
> modules added. And now 5.8 is only 1.5 months from 5.7? What_the_hell?
> I'd like to see Qt complete it's mobile initiative.
> 
> As for contributing, the past 20 months I've been under _multiple_
> commercial licenses, one that was paying for a Desktop just to use Qt Charts.
> I think that's pretty material.
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
> 
> Please be advised that this email may contain confidential information. If you
> are not the intended recipient, please notify us by email by replying to the
> sender and delete this message. The sender disclaims that the content of
> this email constitutes an offer to enter into, or the acceptance of, any
> agreement; provided that the foregoing does not invalidate the binding
> effect of any digital or other electronic reproduction of a manual signature
> that is included in any attachment.
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QTimer Freeze in 4.8

[Thiago Macieira]

On quarta-feira, 22 de junho de 2016 14:49:39 PDT Cjb_SW Freescale wrote:
> yes and no, I mean that every other process is executed proper by Linux,
> and also a second QThread running in the GUI application is running fine.
> Seems that only the graphic Thread is "freezed". It will resume by touching
> the Touchscreen (which is USB, managed via Tslib).
> 
> Unfortunately I cannot build backtraces, I have problems with GDB. I can
> launch the program under gdbserver, and I can set breakpoints, but if I
> press the Interrupt button, then I can see a disassembly window, and I
> can't see where it is the programcounter in my sources. So I tried to
> Interrupt the application while is in the freeze state, but I can't see
> something useful.

Please, always reply to the mailing list. If you reply to me personally, it 
may get lost in inbox and I may never reply. And no one else would have the 
opportunity to, either.

Anyway, since you said that other processes are running just fine and even 
other threads in the same process, my conclusion is that something is blocking 
the GUI thread in your application. We've seen this happen in Qt 5 with XCB, 
whenever the screensaver is on or when you swap to another virtual terminal: 
there's a function call we make that blocks on waiting for a reply from the X 
server, which won't come until the display is unlocked.

Clearly that's not your case, but you get the idea of what it might be.

Unfortunately, I can't help you without a backtrace (and one with debug 
symbols, at that). I have NEVER built a QWS build of Qt and I don't even have 
a Qt 4.8 source handy to look things up. Sorry.

My recommendations are:
 * fix GDB. It's unacceptable for it not to work.
 * consider upgrading to Qt 5.6 or 5.7 (which means dropping QWS for something 
else)

Note that you can work around a non-working gdbserver by causing your process 
to dump core while in the frozen state (kill -ABRT, for example), then loading 
that core file on your host machine's target gdb.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] [qt3d] is qt3d working on the Raspberry PI yet?

[Pierre Chicoine]

Never mind. I cloned Qt repository with GIT and it compiled all the way
through.

Cheers

Pierre Chicoine

On Tue, Jun 21, 2016 at 9:50 AM, Pierre Chicoine <
pierrechicoine...@gmail.com> wrote:

> Does anyone have an idea why compile stops here. Should I put out a Jira
> bug instead? Does qt3d compile on the Raspberry PI?
>
> I cant seem to get qt3d to compile on 5.7. The compiler gives me an error
> 2.  I'm on Kubuntu 14.04. The compile makes it through most of Qt but quits
> here.
>
> Here's the output.
>
> /home/pierre/opt/gcc-4.7-linaro-rpi-gnueabihf/bin/arm-linux-gnueabihf-g++
> -c -include .pch/Qt53DRender -pipe -marm -mfpu=vfp -mtune=arm1176jzf-s
> -march=armv6zk -mabi=aapcs-linux -mfloat-abi=hard
> --sysroot=/mnt/rasp-pi-rootfs -O2 -std=c++11 -fvisibility=hidden
> -fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wvla -D_REENTRANT
> -fPIC -DQT_NO_MTDEV -DQT_NO_LIBUDEV -DQT_NO_TSLIB -DQT_NO_LIBINPUT
> -DQT_NO_FOREACH -DQT_BUILD_3DRENDER_LIB -DQT_BUILDING_QT
> -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT
> -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS
> -DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_NO_EXCEPTIONS
> -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_3DCORE_LIB
> -DQT_GUI_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_OPENGLEXTENSIONS_LIB
> -DQT_GUI_LIB -DQT_CORE_LIB -I. -Ibackend -Igeometry -Igraphicshelpers
> -Iframegraph -Ifrontend -Ijobs -Ilights -Imaterialsystem -Irenderstates
> -Iio -Ipicking -Iraycasting -Iservices -Itexture -I../../include
> -I../../include/Qt3DRender -I../../include/Qt3DRender/5.7.0
> -I../../include/Qt3DRender/5.7.0/Qt3DRender -I../../include/Qt3DCore/5.7.0
> -I../../include/Qt3DCore/5.7.0/Qt3DCore
> -I/home/pierre/opt/qt-everywhere-opensource-src-5.7.0/qtbase/include/QtGui/5.7.0
> -I/home/pierre/opt/qt-everywhere-opensource-src-5.7.0/qtbase/include/QtGui/5.7.0/QtGui
> -I/home/pierre/opt/qt-everywhere-opensource-src-5.7.0/qtbase/include/QtCore/5.7.0
> -I/home/pierre/opt/qt-everywhere-opensource-src-5.7.0/qtbase/include/QtCore/5.7.0/QtCore
> -I../../include/Qt3DCore
> -I/home/pierre/opt/qt-everywhere-opensource-src-5.7.0/qtbase/include
> -I/home/pierre/opt/qt-everywhere-opensource-src-5.7.0/qtbase/include/QtGui
> -I/home/pierre/opt/qt-everywhere-opensource-src-5.7.0/qtbase/include/QtConcurrent
> -I/home/pierre/opt/qt-everywhere-opensource-src-5.7.0/qtbase/include/QtCore
> -I/home/pierre/opt/qt-everywhere-opensource-src-5.7.0/qtbase/include/QtOpenGLExtensions
> -I.moc -I/mnt/rasp-pi-rootfs/opt/vc/include
> -I/mnt/rasp-pi-rootfs/opt/vc/include/interface/vcos/pthreads
> -I/mnt/rasp-pi-rootfs/opt/vc/include/interface/vmcs_host/linux
> -I/home/pierre/opt/qt-everywhere-opensource-src-5.7.0/qtbase/mkspecs/devices/linux-rasp-pi-g++
> -o .obj/clearbuffers.o framegraph/clearbuffers.cpp
> geometry/qattribute.cpp: In static member function ‘static typename
> QtPrivate::QEnableIf<(QtPrivate::FunctionPointer::ArgumentCount ==
> (-1)), QMetaObject::Connection>::Type QObject::connect(const typename
> QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2,
> Qt::ConnectionType) [with Func1 = void (Qt3DCore::QNode::*)(); Func2 =
> std::_Bind(Qt3DRender::QAttribute*,
> std::nullptr_t)>; typename
> QtPrivate::QEnableIf<(QtPrivate::FunctionPointer::ArgumentCount ==
> (-1)), QMetaObject::Connection>::Type = QMetaObject::Connection; typename
> QtPrivate::FunctionPointer::Object = Qt3DCore::QNode; QObject =
> QObject]’:
> geometry/qattribute.cpp:418:1: internal compiler error: in
> type_contains_placeholder_1, at tree.c:2957
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See  for instructions.
> make[2]: *** [.obj/qattribute.o] Error 1
>
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] universal builds on OS X

[Kevin Mcintyre]

Is it possible to build for IPhone from Ubuntu?  Any tutorials of starter
docs would be greatly appreciated.

On Wed, Jun 22, 2016 at 3:51 AM, René J. V.  wrote:

> Hamish Moffatt wrote:
>
>
> > Out of interest, for what purpose? There hasn't been a 32-bit Mac built
> > since before 2008. Does current Qt and Xcode even support an OS X
> > version old enough to run on a 32-bit Mac?
>
> It's a question I've been asking myself, but AFAIK 10.9 still runs on 32bit
> hardware. I haven't seen any indication that Qt 5.6 or 5.7 require 10.8 or
> newer, and 10.7 *definitely* still runs on 32bit hardware. With its own
> Xcode of
> course. So yes, there's still a purpose.
>
> FWIW, there are drivers for things like (older though by no means ancient)
> scanners that exist only in 32bit. Having the possibility to build
> applications
> supporting that type of hardware as universal binaries and then starting
> them in
> 32bit mode is a big advantage. That's an actual example I "have to live
> with"
> (not with a Qt app but it could well have been).
>
> R.
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] [Windows][opengl] How graphic card is choosen on a portable computer with many?

[Xavier Bigand]

Hi,

Some of users can't launch our application because there computer have 2
graphic cards. To fix the issue they have to force the card made for gaming
to be used with our software.
Our application is made with Qt and QML, but we have our custom 3D engine
that do not work on intel integrated GPU. One particularity of our engine
is that it doesn't request a draw every time dislike games.


Is there a way for us to make the application able to discover the best
graphic card and force his usage?


-- 
Xavier
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Thiago Macieira]

On quarta-feira, 22 de junho de 2016 15:39:35 PDT Jason H wrote:
> > "Open governance" means that all members of the community can raise
> > proposals and vote on them. It is also a meritocratic system (as
> > opposed to democratic), which means more weight is given to members of
> > higher rank. Put simply, rank is gained through contributions and
> > commitment to the Qt Project.
> 
> Where and when does this voting occur? I've been vocal about improving Qt on
> mobile since mobile was an option. I've been hardcore on the shortcomings
> for about 20 months. During that time, I saw 5.6 get released, 5.7 get
> released at the same time as 5.6.1, and a lot of meaningless (to me)
> modules added. And now 5.8 is only 1.5 months from 5.7? What_the_hell? I'd
> like to see Qt complete it's mobile initiative.

See the other email on the voting.

Your contribution in terms of being vocal about an issue is not new with the 
Qt Open Governance: you could have done before that. Developers are supposed 
to listen to users to figure out what to do next, especially listen to 
complaints about pain points. That doesn't mean we always do what users ask, 
though -- sometimes we take our own opinion, like was the case of 
QNetworkDatagram.

> As for contributing, the past 20 months I've been under _multiple_
> commercial licenses, one that was paying for a Desktop just to use Qt
> Charts. I think that's pretty material.

Indeed, that's another way to influence: to pay for a commercial licence and 
use your premium support as well as relationship with the commercial sales to 
request features and provide feedback.

But those are outside the governance. Those have been in place since Trolltech 
was founded in 1993.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Thiago Macieira]

On quarta-feira, 22 de junho de 2016 16:57:57 PDT Sze Howe Koh wrote:
> "Open governance" means that all members of the community can raise
> proposals and vote on them. It is also a meritocratic system (as
> opposed to democratic), which means more weight is given to members of
> higher rank. Put simply, rank is gained through contributions and
> commitment to the Qt Project.

Just to be clear: there's no actual *voting*. The Qt governance is not a 
democracy.

Issues are discussed, opinions are raised, those with the most merit (best 
logical arguments, best technical reasoning, coming from those with most 
experience, etc.) win.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Michael R Nelson]

I have to say I completely agree with Jason's sentiment here. I'm a commercial 
customer since early Qt 5.0. I bought with the belief mobile support would 
continue to grow, and not require me to step into native platform coding, nor 
require me to build custom versions of Qt to get around shortcomings that never 
get fixed.

Mike

-Original Message-
From: Interest [mailto:interest-bounces+mnelson=sutron@qt-project.org] On 
Behalf Of Jason H
Sent: Wednesday, June 22, 2016 9:40 AM
To: Sze Howe Koh 
Cc: interest@qt-project.org
Subject: Re: [Interest] 5.8 Features?


> Subject: Re: [Interest] 5.8 Features?
>
> On 22 June 2016 at 09:34, Thiago Macieira  wrote:
> >
> > On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > > I feel like the last few releases have been run by the trolls, and
> > > not the users of Qt. I was hoping open governance would enable the
> > > community to direct Qt development, but I seem to have misinterpreted 
> > > what it means.
>
> See https://wiki.qt.io/The_Qt_Governance_Model
>
> "Open governance" means that all members of the community can raise
> proposals and vote on them. It is also a meritocratic system (as
> opposed to democratic), which means more weight is given to members of
> higher rank. Put simply, rank is gained through contributions and
> commitment to the Qt Project.

Where and when does this voting occur? I've been vocal about improving Qt on 
mobile since mobile was an option. I've been hardcore on the shortcomings for 
about 20 months. During that time, I saw 5.6 get released, 5.7 get released at 
the same time as 5.6.1, and a lot of meaningless (to me) modules added. And now 
5.8 is only 1.5 months from 5.7? What_the_hell? I'd like to see Qt complete 
it's mobile initiative.

As for contributing, the past 20 months I've been under _multiple_ commercial 
licenses, one that was paying for a Desktop just to use Qt Charts. I think 
that's pretty material.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Please be advised that this email may contain confidential information. If you 
are not the intended recipient, please notify us by email by replying to the 
sender and delete this message. The sender disclaims that the content of this 
email constitutes an offer to enter into, or the acceptance of, any agreement; 
provided that the foregoing does not invalidate the binding effect of any 
digital or other electronic reproduction of a manual signature that is included 
in any attachment.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Problems with QWebSocketServer

[Adrian Jäkel]

Oh,

wow what a stupid mistake. Thanks for the hint, it seems i need more 
sleep :)


Adrian

Am 22.06.2016 um 16:42 schrieb André Hartmann:

Hi,

> void MainWindow::buttonClicked()
> {
> // uncomment this for not working websocketserver in mainwindow
> //  QWebSocketServer server(QStringLiteral("QWebSocketServer"),
> QWebSocketServer::NonSecureMode);
> //  if (!server.listen(QHostAddress::LocalHost, 12345)) {
> //qFatal("Failed to open web socket server.");
> //  }
> }


Your'e creating the server in the stackframe of 
MainWindow::buttonClicked(). As soon as the function is leaved, the 
stackframe is cleared and the destructor of QWebSocketServer is called.


Solution: add a member variable QWebSocketServer *m_server and 
allocate memory for it in the buttonClicked():


m_server = new QWebSocketServer(QStringLiteral("QWebSocketServer"),
> QWebSocketServer::NonSecureMode);

Best regards,
André

PS: I know this problem because I had it same way with QTcpServer :)

Am 22.06.2016 um 16:28 schrieb Adrian Jäkel:

Hi,

i'm having problems starting a QWebSocketServer from within a
QMainWindow. Perhaps i'm missing something obvious?

When starting it from the main.cpp it works correctly and i can connect
to it from my sample html page. But inside a QMainWindow e.g. after
clicking a button my html page refuses to connect with "Error in
connection establishment: net::ERR_CONNECTION_REFUSED"

Below is a small sample app. Just un/comment accordingly when testing
both cases.

Regards,
A. Jäkel

main.cpp

#include 
#include 
#include 

#include "mainwindow.h"

int main(int argc, char** argv)
{
 QApplication app(argc, argv);

 // comment the following lines when trying websocketserver from
mainwindow
 QWebSocketServer server(QStringLiteral("QWebSocketServer"),
QWebSocketServer::NonSecureMode);
 if (!server.listen(QHostAddress::LocalHost, 12345)) {
 qFatal("Failed to open web socket server.");
 }

 MainWindow w;
 w.show();

 return app.exec();
}

mainwindow.cpp

#include "mainwindow.h"

#include 
#include 

MainWindow::MainWindow(QWidget *parent) :
   QMainWindow(parent)
{
// uncomment this for not working websocketserver in mainwindow
//  QPushButton *button = new QPushButton("start server");
//  setCentralWidget(button);
//  connect(button, ::clicked, this,
::buttonClicked);
}

void MainWindow::buttonClicked()
{
// uncomment this for not working websocketserver in mainwindow
//  QWebSocketServer server(QStringLiteral("QWebSocketServer"),
QWebSocketServer::NonSecureMode);
//  if (!server.listen(QHostAddress::LocalHost, 12345)) {
//qFatal("Failed to open web socket server.");
//  }
}

mainwindow.h

#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include 

class MainWindow : public QMainWindow
{
   Q_OBJECT

public:
   explicit MainWindow(QWidget *parent = 0);
   ~MainWindow() {}

   void buttonClicked();
};

#endif // MAINWINDOW_H


index.html


 
 
 window.onload = function() {
 var baseUrl = "ws://localhost:12345";

 console.info("Connecting to WebSocket server at " +
baseUrl + ".");
 var socket = new WebSocket(baseUrl);

 socket.onclose = function()
 {
 console.error("web channel closed");
 };
 socket.onerror = function(error)
 {
 console.error("web channel error: " + error);
 };
 socket.onmessage = function(e)
 {
 console.info("message: " + e.data);
 };
 socket.onopen = function()
 {
 console.warn("WebSocket connected.");
 }
 }
 
 
 
 


.pro file
QT += gui widgets websockets

SOURCES += \
 main.cpp \
 mainwindow.cpp

HEADERS += \
 mainwindow.h

DISTFILES += \
 index.html

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest




___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] qtwebengine and libintl on Linux (and using more "system" dependencies on OS X)

[René J . V . Bertin]

René J.V. Bertin wrote:

PS: the same applies to ninja: why build it if already available on the host?!

R.

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] QDockWidgets behaving differently after 5.6.0

[Chris Gripeos]

Hello,


I'm not sure if this is the right place for this, but here it goes!


I'm working in a pretty complex application that was originally build on Qt4.8.


I migrated it to Qt5.6.0 and everything seemed to work fine.


A fewof days ago, I migrated that to Qt5.6.1 and now we're noticing that our 
QDockWidgets are not behaving the way they used to.


They no longer get added to QTabBars. Also, they sometimes get stacked top to 
bottom and sometimes left to right (when we drag and drop them in the 
MainWindow), even though we always specify them to dock to the "Left Area".


Qt5.7 is also behaving the same.


I'm going through docs and our code to see what it is that we might be doing 
wrong.


But I wanted to ask if there are any known changes or issues with Qt5.6.1 and 
Qt5.7 that might be causing this.


Thanks in advance for any help!


- Chris


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interesting blog post on QtQuick UI for games

[guillaume . belz]

I'm not a game dev, but maybe see V-Play engin: http://v-play.net/ 

- Mail original -

> De: "Jason H" 
> À: "Jean-Michaël Celerier" 
> Cc: "interest" 
> Envoyé: Mercredi 22 Juin 2016 14:40:42
> Objet: Re: [Interest] Interesting blog post on QtQuick UI for games

> Also see Voltair
> http://blog.qt.io/blog/2014/07/21/google-labs-voltair-game-built-with-qt/

> Sent: Wednesday, June 22, 2016 at 4:00 AM
> From: "Jean-Michaël Celerier" 
> To: interest 
> Subject: [Interest] Interesting blog post on QtQuick UI for games

> Here :

> http://zxstudio.org/blog/2016/06/22/using-qtquickqml-games/

> Reactions ?

> Best,
> Jean-Michaël Celerier ___
> Interest mailing list Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interest Digest, Vol 57, Issue 25

[Jakub Michałowski]

Szanowni Państwo,

Dziękuję za przesłanie wiadomości.

W dniach od 19 do 24 czerwca 2016 roku jestem poza biurem w związku z 
międzynarodowymi targami Firex w Londynie.

W sprawach szkoleń proszę o kontakt z panem Krzysztofem Nowakowskim pod numerem 
52 36 39 265 lub z działem wsparcia technicznego pod numerem 52 36 39 261.

Realizacją zapytań ofertowych zajmuje się nasz dystrybutor AAT Holding S.A. 
Listę oddziałów dystrybutora można uzyskać na stronie www.aat.pl.

W sprawach nieprawidłowości i usterek proszę o kontakt z działem serwisu pod 
numerem 52 36 39 375.

W sprawach pomocy technicznej na temat obecnych w ofercie urządzeń proszę o 
kontakt z naszym działem wsparcia technicznego pod numerem telefonu: 52 36 39 
261 lub adresem e-mail: polona...@polon-alfa.pl

Serdecznie pozdrawiam

Jakub Michałowski
Młodszy Konstruktor

Polon-Alfa Spółka z ograniczoną odpowiedzialnością Sp. k.
85-861 Bydgoszcz, ul. Glinki 155
Tel.  +48 52 36 39 265
Fax  +48 52 36 39 264
Kom.  +48 601 380 401
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Problems with QWebSocketServer

[Adrian Jäkel]

Hi,

i'm having problems starting a QWebSocketServer from within a 
QMainWindow. Perhaps i'm missing something obvious?


When starting it from the main.cpp it works correctly and i can connect 
to it from my sample html page. But inside a QMainWindow e.g. after 
clicking a button my html page refuses to connect with "Error in 
connection establishment: net::ERR_CONNECTION_REFUSED"


Below is a small sample app. Just un/comment accordingly when testing 
both cases.


Regards,
A. Jäkel

main.cpp

#include 
#include 
#include 

#include "mainwindow.h"

int main(int argc, char** argv)
{
QApplication app(argc, argv);

// comment the following lines when trying websocketserver from 
mainwindow
QWebSocketServer server(QStringLiteral("QWebSocketServer"), 
QWebSocketServer::NonSecureMode);

if (!server.listen(QHostAddress::LocalHost, 12345)) {
qFatal("Failed to open web socket server.");
}

MainWindow w;
w.show();

return app.exec();
}

mainwindow.cpp

#include "mainwindow.h"

#include 
#include 

MainWindow::MainWindow(QWidget *parent) :
  QMainWindow(parent)
{
// uncomment this for not working websocketserver in mainwindow
//  QPushButton *button = new QPushButton("start server");
//  setCentralWidget(button);
//  connect(button, ::clicked, this, 
::buttonClicked);

}

void MainWindow::buttonClicked()
{
// uncomment this for not working websocketserver in mainwindow
//  QWebSocketServer server(QStringLiteral("QWebSocketServer"), 
QWebSocketServer::NonSecureMode);

//  if (!server.listen(QHostAddress::LocalHost, 12345)) {
//qFatal("Failed to open web socket server.");
//  }
}

mainwindow.h

#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include 

class MainWindow : public QMainWindow
{
  Q_OBJECT

public:
  explicit MainWindow(QWidget *parent = 0);
  ~MainWindow() {}

  void buttonClicked();
};

#endif // MAINWINDOW_H


index.html




window.onload = function() {
var baseUrl = "ws://localhost:12345";

[Interest] qtwebengine and libintl on Linux (and using more "system" dependencies on OS X)

[René J . V . Bertin]

Hi,

I'm trying to build QtWebengine (5.6.1) for installing into /opt/local which 
also contains a gettext build that includes libintl (which provides symbols 
like libintl_gettext). This is a context that is comparable to what we have in 
MacPorts on OS X.

I'm getting QtWebengine build errors related to that symbol when linking 
patched-yasm which do not occur on OS X. Is there anything to do about this 
other than moving libintl.so or possibly the whole gettext install in 
/opt/local aside while building QtWebengine? Isn't it possible to use the 
system yasm, simply?

Along a similar vein, has anyone looked into using more dependencies from 
(elsewhere on) the system on OS X, e.g. ffmpeg from MacPorts when building 
QtWebengine for MacPorts? Anything that reduces the build time and/or 
installation footprint of this huge component would be welcome!

Thanks,
R.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interesting blog post on QtQuick UI for games

[Jason H]

Also see Voltair http://blog.qt.io/blog/2014/07/21/google-labs-voltair-game-built-with-qt/
 

Sent: Wednesday, June 22, 2016 at 4:00 AM
From: "Jean-Michaël Celerier" 
To: interest 
Subject: [Interest] Interesting blog post on QtQuick UI for games


Here :




http://zxstudio.org/blog/2016/06/22/using-qtquickqml-games/

 

Reactions ?
 

Best,

Jean-Michaël Celerier




___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest



___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Jason H]

> Subject: Re: [Interest] 5.8 Features?
>
> On 22 June 2016 at 09:34, Thiago Macieira  wrote:
> >
> > On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > > I feel like the last few releases have been run by the trolls, and not the
> > > users of Qt. I was hoping open governance would enable the community to
> > > direct Qt development, but I seem to have misinterpreted what it means.
> 
> See https://wiki.qt.io/The_Qt_Governance_Model
> 
> "Open governance" means that all members of the community can raise
> proposals and vote on them. It is also a meritocratic system (as
> opposed to democratic), which means more weight is given to members of
> higher rank. Put simply, rank is gained through contributions and
> commitment to the Qt Project.

Where and when does this voting occur? I've been vocal about improving Qt on 
mobile since mobile was an option. I've been hardcore on the shortcomings for 
about 20 months. During that time, I saw 5.6 get released, 5.7 get released at 
the same time as 5.6.1, and a lot of meaningless (to me) modules added. And now 
5.8 is only 1.5 months from 5.7? What_the_hell? I'd like to see Qt complete 
it's mobile initiative.

As for contributing, the past 20 months I've been under _multiple_ commercial 
licenses, one that was paying for a Desktop just to use Qt Charts. I think 
that's pretty material. 
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] universal builds on OS X

[René J . V . Bertin]

Hamish Moffatt wrote:


> Out of interest, for what purpose? There hasn't been a 32-bit Mac built
> since before 2008. Does current Qt and Xcode even support an OS X
> version old enough to run on a 32-bit Mac?

It's a question I've been asking myself, but AFAIK 10.9 still runs on 32bit 
hardware. I haven't seen any indication that Qt 5.6 or 5.7 require 10.8 or 
newer, and 10.7 *definitely* still runs on 32bit hardware. With its own Xcode 
of 
course. So yes, there's still a purpose.

FWIW, there are drivers for things like (older though by no means ancient) 
scanners that exist only in 32bit. Having the possibility to build applications 
supporting that type of hardware as universal binaries and then starting them 
in 
32bit mode is a big advantage. That's an actual example I "have to live with" 
(not with a Qt app but it could well have been).

R.

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Maurice Kalinowski]

> Highest prio from my personal perspective:
> >> - Background processing API
> >> - In-app Notifications: local, remote
> + add Windows Store to Qt Purchasing module

https://codereview.qt-project.org/#/c/149602/
https://codereview.qt-project.org/#/c/162992/

;)

Maurice


From: Interest 
[mailto:interest-bounces+maurice.kalinowski=qt...@qt-project.org] On Behalf Of 
Matthias Degenkolb via Interest
Sent: Wednesday, June 22, 2016 11:25 AM
To: ekke 
Cc: interest@qt-project.org
Subject: Re: [Interest] 5.8 Features?

I fully agree to ekke's and Jason's wishes. The features mentioned are all 
topics I also miss urgently since our first app development tests with Qt ..
Not having cross-platform access to those "standard" mechanisms for mobile OS 
really makes me wonder whether my next projects will be based on Qt ...

Highest prio from my personal perspective:
>> - Background processing API
>> - In-app Notifications: local, remote
+ add Windows Store to Qt Purchasing module


2016-06-22 10:45 GMT+02:00 ekke 
>:
Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> Den 21-06-2016 kl. 22:55 skrev Jason H:
>> I feel like the last few releases have been run by the trolls, and
>> not the users of Qt. I was hoping open governance would enable the
>> community to direct Qt development, but I seem to have misinterpreted
>> what it means. I'm looking for what's going into 5.8.. not much
>> listed on the releases page.
>>
>> I'd like to suggest that mobile get some much needed love.
>> - Application state transitions; Foreground, background
>> - Background processing API
>> - Screen wake lock API
>> - In-app Notifications: local, remote
>>
>> While I have those characterized as "mobile" there are things like
>> notifications occurring on desktop platforms.
>>
>> Any thoughts?
>
> There's only one reason why you don't see more features for the mobile
> parts: There are not enough developers on it. And that's not because
> QtCompany is doing anything wrong, they just have their priorities
> different from what you have.
>
> Personally I don't care about mobile at all. I haven't had a mobile
> customer since 2011 and I don't see that changing. My focus is almost
> entirely on Linux embedded and Windows desktop. Those are the areas
> where a lot of applications are written.
>
> I'd love to see the mobile platforms thrive. But unless you Qt users
> start becoming Qt developers and contribute to it, I don't see that
> happening.
hmmm
the only reason for me to use Qt is mobile
using new Qt Quick Controls 2 Qt is a great platform for mobile app
development and I hope many new developers will start with Qt on mobile
to make this easier I'm writing example apps and a blog series
http://j.mp/qt-x

I really hope that there will be development on the topics Jason H
mentioned above

ekke

>
> Bo Thorsen,
> Director, Viking Software.
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[ekke]

Am 22.06.16 um 12:12 schrieb Xavier Bigand:
> It is good to know, I made my test with Qt5.6 and Qt Quick Controls
> labs. It seems that there is some improvement since.
> It seems that one of the hardest thing to simulate is the shadow with
> elevation, but on your captures it seems perfect.
Material.elevation property can be set in Qt 5.7
>
> If I can make my personal application with Qt, it would be great,
> because I dislike Android Studio.
I'll do more example apps and provide recipes for Controls not available
out-of-the-box
ekke
>
> 2016-06-22 11:43 GMT+02:00 ekke  >:
>
> Am 22.06.16 um 11:31 schrieb Xavier Bigand:
>> I made few tests for a personal project with Qt Quick Controls 2
>> on Android and was not convinced. Because for a full GUI
>> application it still too far from the same GUI made with the
>> Android SDK.
> take a look at this example app: blog http://bit.ly/qt-drawer-nav-x
> and at github: https://github.com/ekke/drawer_nav_x
> Drawer, Bottom Navigation, FAB, Popup, Toast, StackView,
> SwipeView, Pages, ...
> some fine-tuning is already in-development (have written
> bugreports for this)
> From my POV you can write good looking Android Material Apps
> the only controls I'm missing are Date- and Time Pickers
>
>
> I'm still evaluating, but have a good feeling that Qt 5.7 will be
> great for mobile business apps I'm writing
>
> ekke
>
>> I still think that for small applications that is preferable to
>> develop them with the platform SDK as they contains all features.
>> But for middle and biggest applications it can be different
>> especially if desktop platforms are also target.
>> There is an other reason why I think that it is preferable to use
>> platform SDK, it is for commercial application that want to try
>> to be featured by mobile stores, it would be easier to integrate
>> latest SDK features,...
>>
>>
>> I am working on big application with a 3D engine that runs on
>> mobile and desktop, we are using Qt Quick for the GUI, everything
>> else is in standard C++. For feature specific to the platform
>> (in-app, social,...) we use platform SDK and it's not that long
>> to do the job 2 or 3 times for those features.
>>
>> Qt represent a big time saver for the GUI for us mainly because
>> of the property binding that allow us to adapt the GUI easily and
>> efficiently to the screen size, and tweak it per platform,
>> product version,...
>>
>> And now I am trying to replace our 3D engine by qt3d to improve
>> the user experience, the compatibility on desktop, the
>> performances and be able to use different rendering techniques on
>> desktop.
>>
>>
>>
>>
>> 2016-06-22 10:45 GMT+02:00 ekke > >:
>>
>> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
>> > Den 21-06-2016 kl. 22:55 skrev Jason H:
>> >> I feel like the last few releases have been run by the
>> trolls, and
>> >> not the users of Qt. I was hoping open governance would
>> enable the
>> >> community to direct Qt development, but I seem to have
>> misinterpreted
>> >> what it means. I'm looking for what's going into 5.8.. not
>> much
>> >> listed on the releases page.
>> >>
>> >> I'd like to suggest that mobile get some much needed love.
>> >> - Application state transitions; Foreground, background
>> >> - Background processing API
>> >> - Screen wake lock API
>> >> - In-app Notifications: local, remote
>> >>
>> >> While I have those characterized as "mobile" there are
>> things like
>> >> notifications occurring on desktop platforms.
>> >>
>> >> Any thoughts?
>> >
>> > There's only one reason why you don't see more features for
>> the mobile
>> > parts: There are not enough developers on it. And that's
>> not because
>> > QtCompany is doing anything wrong, they just have their
>> priorities
>> > different from what you have.
>> >
>> > Personally I don't care about mobile at all. I haven't had
>> a mobile
>> > customer since 2011 and I don't see that changing. My focus
>> is almost
>> > entirely on Linux embedded and Windows desktop. Those are
>> the areas
>> > where a lot of applications are written.
>> >
>> > I'd love to see the mobile platforms thrive. But unless you
>> Qt users
>> > start becoming Qt developers and contribute to it, I don't
>> see that
>> > happening.
>> hmmm
>> the only reason for me to use Qt is mobile
>> using new Qt Quick Controls 2 Qt is a great platform for
>> 

Re: [Interest] 5.8 Features?

[Xavier Bigand]

It is good to know, I made my test with Qt5.6 and Qt Quick Controls labs.
It seems that there is some improvement since.
It seems that one of the hardest thing to simulate is the shadow with
elevation, but on your captures it seems perfect.

If I can make my personal application with Qt, it would be great, because I
dislike Android Studio.

2016-06-22 11:43 GMT+02:00 ekke :

> Am 22.06.16 um 11:31 schrieb Xavier Bigand:
>
> I made few tests for a personal project with Qt Quick Controls 2 on
> Android and was not convinced. Because for a full GUI application it still
> too far from the same GUI made with the Android SDK.
>
> take a look at this example app: blog http://bit.ly/qt-drawer-nav-x
> and at github: https://github.com/ekke/drawer_nav_x
> Drawer, Bottom Navigation, FAB, Popup, Toast, StackView, SwipeView, Pages,
> ...
> some fine-tuning is already in-development (have written bugreports for
> this)
> From my POV you can write good looking Android Material Apps
> the only controls I'm missing are Date- and Time Pickers
>
>
> I'm still evaluating, but have a good feeling that Qt 5.7 will be great
> for mobile business apps I'm writing
>
> ekke
>
> I still think that for small applications that is preferable to develop
> them with the platform SDK as they contains all features. But for middle
> and biggest applications it can be different especially if desktop
> platforms are also target.
> There is an other reason why I think that it is preferable to use platform
> SDK, it is for commercial application that want to try to be featured by
> mobile stores, it would be easier to integrate latest SDK features,...
>
>
> I am working on big application with a 3D engine that runs on mobile and
> desktop, we are using Qt Quick for the GUI, everything else is in standard
> C++. For feature specific to the platform (in-app, social,...) we use
> platform SDK and it's not that long to do the job 2 or 3 times for those
> features.
>
> Qt represent a big time saver for the GUI for us mainly because of the
> property binding that allow us to adapt the GUI easily and efficiently to
> the screen size, and tweak it per platform, product version,...
>
> And now I am trying to replace our 3D engine by qt3d to improve the user
> experience, the compatibility on desktop, the performances and be able to
> use different rendering techniques on desktop.
>
>
>
>
> 2016-06-22 10:45 GMT+02:00 ekke :
>
>> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
>> > Den 21-06-2016 kl. 22:55 skrev Jason H:
>> >> I feel like the last few releases have been run by the trolls, and
>> >> not the users of Qt. I was hoping open governance would enable the
>> >> community to direct Qt development, but I seem to have misinterpreted
>> >> what it means. I'm looking for what's going into 5.8.. not much
>> >> listed on the releases page.
>> >>
>> >> I'd like to suggest that mobile get some much needed love.
>> >> - Application state transitions; Foreground, background
>> >> - Background processing API
>> >> - Screen wake lock API
>> >> - In-app Notifications: local, remote
>> >>
>> >> While I have those characterized as "mobile" there are things like
>> >> notifications occurring on desktop platforms.
>> >>
>> >> Any thoughts?
>> >
>> > There's only one reason why you don't see more features for the mobile
>> > parts: There are not enough developers on it. And that's not because
>> > QtCompany is doing anything wrong, they just have their priorities
>> > different from what you have.
>> >
>> > Personally I don't care about mobile at all. I haven't had a mobile
>> > customer since 2011 and I don't see that changing. My focus is almost
>> > entirely on Linux embedded and Windows desktop. Those are the areas
>> > where a lot of applications are written.
>> >
>> > I'd love to see the mobile platforms thrive. But unless you Qt users
>> > start becoming Qt developers and contribute to it, I don't see that
>> > happening.
>> hmmm
>> the only reason for me to use Qt is mobile
>> using new Qt Quick Controls 2 Qt is a great platform for mobile app
>> development and I hope many new developers will start with Qt on mobile
>> to make this easier I'm writing example apps and a blog series
>> http://j.mp/qt-x
>>
>> I really hope that there will be development on the topics Jason H
>> mentioned above
>>
>> ekke
>>
>> >
>> > Bo Thorsen,
>> > Director, Viking Software.
>> >
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>
>
>
> --
> Xavier
>
>
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>


-- 
Xavier
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[ekke]

Am 22.06.16 um 11:31 schrieb Xavier Bigand:
> I made few tests for a personal project with Qt Quick Controls 2 on
> Android and was not convinced. Because for a full GUI application it
> still too far from the same GUI made with the Android SDK.
take a look at this example app: blog http://bit.ly/qt-drawer-nav-x
and at github: https://github.com/ekke/drawer_nav_x
Drawer, Bottom Navigation, FAB, Popup, Toast, StackView, SwipeView,
Pages, ...
some fine-tuning is already in-development (have written bugreports for
this)
>From my POV you can write good looking Android Material Apps
the only controls I'm missing are Date- and Time Pickers


I'm still evaluating, but have a good feeling that Qt 5.7 will be great
for mobile business apps I'm writing

ekke
> I still think that for small applications that is preferable to
> develop them with the platform SDK as they contains all features. But
> for middle and biggest applications it can be different especially if
> desktop platforms are also target.
> There is an other reason why I think that it is preferable to use
> platform SDK, it is for commercial application that want to try to be
> featured by mobile stores, it would be easier to integrate latest SDK
> features,...
>
>
> I am working on big application with a 3D engine that runs on mobile
> and desktop, we are using Qt Quick for the GUI, everything else is in
> standard C++. For feature specific to the platform (in-app,
> social,...) we use platform SDK and it's not that long to do the job 2
> or 3 times for those features.
>
> Qt represent a big time saver for the GUI for us mainly because of the
> property binding that allow us to adapt the GUI easily and efficiently
> to the screen size, and tweak it per platform, product version,...
>
> And now I am trying to replace our 3D engine by qt3d to improve the
> user experience, the compatibility on desktop, the performances and be
> able to use different rendering techniques on desktop.
>
>
>
>
> 2016-06-22 10:45 GMT+02:00 ekke  >:
>
> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> > Den 21-06-2016 kl. 22:55 skrev Jason H:
> >> I feel like the last few releases have been run by the trolls, and
> >> not the users of Qt. I was hoping open governance would enable the
> >> community to direct Qt development, but I seem to have
> misinterpreted
> >> what it means. I'm looking for what's going into 5.8.. not much
> >> listed on the releases page.
> >>
> >> I'd like to suggest that mobile get some much needed love.
> >> - Application state transitions; Foreground, background
> >> - Background processing API
> >> - Screen wake lock API
> >> - In-app Notifications: local, remote
> >>
> >> While I have those characterized as "mobile" there are things like
> >> notifications occurring on desktop platforms.
> >>
> >> Any thoughts?
> >
> > There's only one reason why you don't see more features for the
> mobile
> > parts: There are not enough developers on it. And that's not because
> > QtCompany is doing anything wrong, they just have their priorities
> > different from what you have.
> >
> > Personally I don't care about mobile at all. I haven't had a mobile
> > customer since 2011 and I don't see that changing. My focus is
> almost
> > entirely on Linux embedded and Windows desktop. Those are the areas
> > where a lot of applications are written.
> >
> > I'd love to see the mobile platforms thrive. But unless you Qt users
> > start becoming Qt developers and contribute to it, I don't see that
> > happening.
> hmmm
> the only reason for me to use Qt is mobile
> using new Qt Quick Controls 2 Qt is a great platform for mobile app
> development and I hope many new developers will start with Qt on
> mobile
> to make this easier I'm writing example apps and a blog series
> http://j.mp/qt-x
>
> I really hope that there will be development on the topics Jason H
> mentioned above
>
> ekke
>
> >
> > Bo Thorsen,
> > Director, Viking Software.
> >
>
> ___
> Interest mailing list
> Interest@qt-project.org 
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
>
>
> -- 
> Xavier


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Xavier Bigand]

I made few tests for a personal project with Qt Quick Controls 2 on Android
and was not convinced. Because for a full GUI application it still too far
from the same GUI made with the Android SDK.
I still think that for small applications that is preferable to develop
them with the platform SDK as they contains all features. But for middle
and biggest applications it can be different especially if desktop
platforms are also target.
There is an other reason why I think that it is preferable to use platform
SDK, it is for commercial application that want to try to be featured by
mobile stores, it would be easier to integrate latest SDK features,...


I am working on big application with a 3D engine that runs on mobile and
desktop, we are using Qt Quick for the GUI, everything else is in standard
C++. For feature specific to the platform (in-app, social,...) we use
platform SDK and it's not that long to do the job 2 or 3 times for those
features.

Qt represent a big time saver for the GUI for us mainly because of the
property binding that allow us to adapt the GUI easily and efficiently to
the screen size, and tweak it per platform, product version,...

And now I am trying to replace our 3D engine by qt3d to improve the user
experience, the compatibility on desktop, the performances and be able to
use different rendering techniques on desktop.




2016-06-22 10:45 GMT+02:00 ekke :

> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> > Den 21-06-2016 kl. 22:55 skrev Jason H:
> >> I feel like the last few releases have been run by the trolls, and
> >> not the users of Qt. I was hoping open governance would enable the
> >> community to direct Qt development, but I seem to have misinterpreted
> >> what it means. I'm looking for what's going into 5.8.. not much
> >> listed on the releases page.
> >>
> >> I'd like to suggest that mobile get some much needed love.
> >> - Application state transitions; Foreground, background
> >> - Background processing API
> >> - Screen wake lock API
> >> - In-app Notifications: local, remote
> >>
> >> While I have those characterized as "mobile" there are things like
> >> notifications occurring on desktop platforms.
> >>
> >> Any thoughts?
> >
> > There's only one reason why you don't see more features for the mobile
> > parts: There are not enough developers on it. And that's not because
> > QtCompany is doing anything wrong, they just have their priorities
> > different from what you have.
> >
> > Personally I don't care about mobile at all. I haven't had a mobile
> > customer since 2011 and I don't see that changing. My focus is almost
> > entirely on Linux embedded and Windows desktop. Those are the areas
> > where a lot of applications are written.
> >
> > I'd love to see the mobile platforms thrive. But unless you Qt users
> > start becoming Qt developers and contribute to it, I don't see that
> > happening.
> hmmm
> the only reason for me to use Qt is mobile
> using new Qt Quick Controls 2 Qt is a great platform for mobile app
> development and I hope many new developers will start with Qt on mobile
> to make this easier I'm writing example apps and a blog series
> http://j.mp/qt-x
>
> I really hope that there will be development on the topics Jason H
> mentioned above
>
> ekke
>
> >
> > Bo Thorsen,
> > Director, Viking Software.
> >
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>



-- 
Xavier
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interest Digest, Vol 57, Issue 24

[Jakub Michałowski]

Szanowni Państwo,

Dziękuję za przesłanie wiadomości.

W dniach od 19 do 24 czerwca 2016 roku jestem poza biurem w związku z 
międzynarodowymi targami Firex w Londynie.

W sprawach szkoleń proszę o kontakt z panem Krzysztofem Nowakowskim pod numerem 
52 36 39 265 lub z działem wsparcia technicznego pod numerem 52 36 39 261.

Realizacją zapytań ofertowych zajmuje się nasz dystrybutor AAT Holding S.A. 
Listę oddziałów dystrybutora można uzyskać na stronie www.aat.pl.

W sprawach nieprawidłowości i usterek proszę o kontakt z działem serwisu pod 
numerem 52 36 39 375.

W sprawach pomocy technicznej na temat obecnych w ofercie urządzeń proszę o 
kontakt z naszym działem wsparcia technicznego pod numerem telefonu: 52 36 39 
261 lub adresem e-mail: polona...@polon-alfa.pl

Serdecznie pozdrawiam

Jakub Michałowski
Młodszy Konstruktor

Polon-Alfa Spółka z ograniczoną odpowiedzialnością Sp. k.
85-861 Bydgoszcz, ul. Glinki 155
Tel.  +48 52 36 39 265
Fax  +48 52 36 39 264
Kom.  +48 601 380 401
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Konstantin Tokarev]

21.06.2016, 23:55, "Jason H" :
> I feel like the last few releases have been run by the trolls, and not the 
> users of Qt. I was hoping open governance would enable the community to 
> direct Qt development, but I seem to have misinterpreted what it means. I'm 
> looking for what's going into 5.8.. not much listed on the releases page.
>
> I'd like to suggest that mobile get some much needed love.
> - Application state transitions; Foreground, background
> - Background processing API
> - Screen wake lock API
> - In-app Notifications: local, remote
>
> While I have those characterized as "mobile" there are things like 
> notifications occurring on desktop platforms.
>
> Any thoughts?

You still have ~1.5 months before 5.8 feature freeze to implement some of these 
items :)

-- 
Regards,
Konstantin
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Matthias Degenkolb via Interest]

I fully agree to ekke's and Jason's wishes. The features mentioned are all
topics I also miss urgently since our first app development tests with Qt ..
Not having cross-platform access to those "standard" mechanisms for mobile
OS really makes me wonder whether my next projects will be based on Qt ...

Highest prio from my personal perspective:
>> - Background processing API
>> - In-app Notifications: local, remote
+ add Windows Store to Qt Purchasing module


2016-06-22 10:45 GMT+02:00 ekke :

> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> > Den 21-06-2016 kl. 22:55 skrev Jason H:
> >> I feel like the last few releases have been run by the trolls, and
> >> not the users of Qt. I was hoping open governance would enable the
> >> community to direct Qt development, but I seem to have misinterpreted
> >> what it means. I'm looking for what's going into 5.8.. not much
> >> listed on the releases page.
> >>
> >> I'd like to suggest that mobile get some much needed love.
> >> - Application state transitions; Foreground, background
> >> - Background processing API
> >> - Screen wake lock API
> >> - In-app Notifications: local, remote
> >>
> >> While I have those characterized as "mobile" there are things like
> >> notifications occurring on desktop platforms.
> >>
> >> Any thoughts?
> >
> > There's only one reason why you don't see more features for the mobile
> > parts: There are not enough developers on it. And that's not because
> > QtCompany is doing anything wrong, they just have their priorities
> > different from what you have.
> >
> > Personally I don't care about mobile at all. I haven't had a mobile
> > customer since 2011 and I don't see that changing. My focus is almost
> > entirely on Linux embedded and Windows desktop. Those are the areas
> > where a lot of applications are written.
> >
> > I'd love to see the mobile platforms thrive. But unless you Qt users
> > start becoming Qt developers and contribute to it, I don't see that
> > happening.
> hmmm
> the only reason for me to use Qt is mobile
> using new Qt Quick Controls 2 Qt is a great platform for mobile app
> development and I hope many new developers will start with Qt on mobile
> to make this easier I'm writing example apps and a blog series
> http://j.mp/qt-x
>
> I really hope that there will be development on the topics Jason H
> mentioned above
>
> ekke
>
> >
> > Bo Thorsen,
> > Director, Viking Software.
> >
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Sze Howe Koh]

On 22 June 2016 at 09:34, Thiago Macieira  wrote:
>
> On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > I feel like the last few releases have been run by the trolls, and not the
> > users of Qt. I was hoping open governance would enable the community to
> > direct Qt development, but I seem to have misinterpreted what it means.

See https://wiki.qt.io/The_Qt_Governance_Model

"Open governance" means that all members of the community can raise
proposals and vote on them. It is also a meritocratic system (as
opposed to democratic), which means more weight is given to members of
higher rank. Put simply, rank is gained through contributions and
commitment to the Qt Project.

Regarding governance of new features, you can propose to add Feature X
to Qt. If nobody objects, that means you now have the green light to
implement and submit Feature X. (The normal review process still
applies.) You don't _have_ to make a formal proposal each time you
submit a patch, but it's strongly recommended when adding a large new
feature.


> > I'm
> > looking for what's going into 5.8.. not much listed on the releases page.
>
> Open governance allows developers of Qt, not users of Qt, to direct new
> features. I have added features to every version since 5.0 (inclusive) and
> have already submitted a few to 5.8. Open governance did not change the means
> for non-developing users to influence the progression.

To clarify Thiago's point, "Developers of Qt" refers to all
contributors, not just the Qt Company. You can become a developer of
Qt and direct new features simply by submitting, reviewing, and/or
testing code + documentation that pertain to the features you want.
For example, Qt 3D is now released mainly because KDAB poured
resources into its development [1].

Alternatively, you can achieve your goal indirectly by persuading
someone to develop the features that you want. For example, you can
persuade them by paying them [2], or by convincing them that it's
better to focus on Feature X instead of Feature Y or Bugfix Z.


Regards,
Sze-Howe

[1] https://blog.qt.io/blog/2016/06/16/introducing-qt-3d/
[2] https://woboq.com/blog/qdockwidget-changes-in-56.html
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[ekke]

Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> Den 21-06-2016 kl. 22:55 skrev Jason H:
>> I feel like the last few releases have been run by the trolls, and
>> not the users of Qt. I was hoping open governance would enable the
>> community to direct Qt development, but I seem to have misinterpreted
>> what it means. I'm looking for what's going into 5.8.. not much
>> listed on the releases page.
>>
>> I'd like to suggest that mobile get some much needed love.
>> - Application state transitions; Foreground, background
>> - Background processing API
>> - Screen wake lock API
>> - In-app Notifications: local, remote
>>
>> While I have those characterized as "mobile" there are things like
>> notifications occurring on desktop platforms.
>>
>> Any thoughts?
>
> There's only one reason why you don't see more features for the mobile
> parts: There are not enough developers on it. And that's not because
> QtCompany is doing anything wrong, they just have their priorities
> different from what you have.
>
> Personally I don't care about mobile at all. I haven't had a mobile
> customer since 2011 and I don't see that changing. My focus is almost
> entirely on Linux embedded and Windows desktop. Those are the areas
> where a lot of applications are written.
>
> I'd love to see the mobile platforms thrive. But unless you Qt users
> start becoming Qt developers and contribute to it, I don't see that
> happening.
hmmm
the only reason for me to use Qt is mobile
using new Qt Quick Controls 2 Qt is a great platform for mobile app
development and I hope many new developers will start with Qt on mobile
to make this easier I'm writing example apps and a blog series
http://j.mp/qt-x

I really hope that there will be development on the topics Jason H
mentioned above

ekke

>
> Bo Thorsen,
> Director, Viking Software.
>

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Bo Thorsen]

Den 21-06-2016 kl. 22:55 skrev Jason H:

I feel like the last few releases have been run by the trolls, and not the 
users of Qt. I was hoping open governance would enable the community to direct 
Qt development, but I seem to have misinterpreted what it means. I'm looking 
for what's going into 5.8.. not much listed on the releases page.

I'd like to suggest that mobile get some much needed love.
- Application state transitions; Foreground, background
- Background processing API
- Screen wake lock API
- In-app Notifications: local, remote

While I have those characterized as "mobile" there are things like 
notifications occurring on desktop platforms.

Any thoughts?


There's only one reason why you don't see more features for the mobile 
parts: There are not enough developers on it. And that's not because 
QtCompany is doing anything wrong, they just have their priorities 
different from what you have.


Personally I don't care about mobile at all. I haven't had a mobile 
customer since 2011 and I don't see that changing. My focus is almost 
entirely on Linux embedded and Windows desktop. Those are the areas 
where a lot of applications are written.


I'd love to see the mobile platforms thrive. But unless you Qt users 
start becoming Qt developers and contribute to it, I don't see that 
happening.


Bo Thorsen,
Director, Viking Software.

--
Viking Software
Qt and C++ developers for hire
http://www.vikingsoft.eu
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Interesting blog post on QtQuick UI for games

[Jean-Michaël Celerier]

Here :
http://zxstudio.org/blog/2016/06/22/using-qtquickqml-games/


Reactions ?

Best,
Jean-Michaël Celerier
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest