Re: [Interest] I love QML

2020-07-03 Thread joao morgado via Interest
 When I started using Qt I never touched WIndows MFC again.
Qt is indeed a geat tool, and fun to use. QML is even cooler that the Qt 
widgets.
A bit off topic I just want to point out that I was using the Indie developer 
license and was happy to pay for it, even if I was not making any money with 
Qt, because I was not developing any comercial apps. To me it was more like a 
donation for supporting Qt company. Qt company never reveal how much clients 
they had, I guess not much because they pulled the plug, but I wich they would 
consider bring a afordable license for indies again. That startup license is 
just to much for indies. 
CheersJoão
Em sexta-feira, 3 de julho de 2020 03:25:24 GMT+1, Quang Phú Bùi 
 escreveu:  
 
 Agree with that.
Qt is an awesome tool to create an app with backend by C++ and UI by QML.
I'm waiting to touch Qt6 with new generation of QML

phubq

On Fri, 3 Jul 2020 at 00:44, ekke  wrote:

+1 from me

tomorrow it's exactly 42 years ago I started developing software 
(Assembler, COBOL, ...) and over all the years most fun is using Qt + 
QML to write mobile apps :)
to be precise: fun started with Qt 4.8 + BlackBerry 10 Cascades, but in 
the meantime I'm very happy with QQC2

I'm looking forward to Qt 6 / strict QML and my goal is to port 
(refactor) all my mobile apps (and blog about and probably write a book)

thx to Qt I'm able to write performant complex mobile business apps in a 
short timeframe and all my users love their apps.

from my POV Qt 6 + strict QML + new SmallBusiness - License should 
motivate mobile app devs to switch to Qt.

ekke
Am 02.07.20 um 17:50 schrieb Jérôme Godbout:
> +1 totaly agree, we often forget to praise Qt for the great work. I have been 
> through many framework (MFC, Xaml, wxWidgets, Xamarin...) but my favorite is 
> still Qt with Qml. The binding often leverage the need for those view model 
> or model convert to adapt to the view. The fact that I can have most of my 
> lib (algo, GUI, controler...) into reusable code between desktop, mobile, 
> embedded Yocto is such a huge win. I cannot wait for Qt 6 and C++ binding, 
> seriously it's probably the feature I'm most looking forward to, remove those 
> conditional connect or complex (mostly hard to maintain) flow around connect.
>
> Long live Qt 
>
> -Original Message-
> From: Interest  On Behalf Of Jason H
> Sent: July 2, 2020 11:24 AM
> To: interestqt-project.org ; ulf.herm...@qt.io
> Subject: [Interest] I love QML
>
> I know I spend a lot of time talking about inadequacies of Qt, but it's out 
> of love. Since discovering Qt back in oh, 2001 when I was writing MFC apps, I 
> have come to love the toolkit despite its rough edges. I have been assigned 
> to port our Qt/QML app to Swift. And let me say what a joy it is working with 
> Qt/QML.
> - The ability to use JSON inline, and as a proper JavaScript Object is a huge 
> feature that I did not appreciate previously.
> - The property bindings system eliminates so much code and the automatic 
> evaluation of bindings is phenomenal.
> - The lack of a separated view and view controller makes reusable components 
> even easier.
> - The fact that I don't need to use UI machinations in a UI builder to build 
> an app (I'm looking at you, @IBOutlet) is another joy
> - The fact that Qt types don't seemingly duplicate each other in quirky ways 
> (UIColor, CGColor)
> - I could go on...
>
> I know Qt is going to offer an alternative to JS, but unless it has all those 
> features (mainly the in-line JSON in actual JSON) I am likely to stay with 
> the JavaScript version.
>
> A big big Thank You to the Qt team!
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest

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

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


Re: [Interest] Qt6 CMake Windows VS Debug Build Issues

2020-07-03 Thread Oliver Niebuhr
Am 30/06/2020 um 11:52 schrieb Oliver Niebuhr:
> Am 30/06/2020 um 09:31 schrieb Alexandru Croitor:
>> Hi,
>>
>> Thanks for the feedback.
>>
>> I would appreciate if you could file 2 bug reports for the issues you 
>> encountered with the "Build System: CMake component".
>>
>> I am not surprised about the long path issues, but the the clang one is 
>> strange.
>> Please provide your CMake configuration line and which clang libraries you 
>> used, in the bug reports.
>>
>>> On 30. Jun 2020, at 05:18, Oliver Niebuhr  
>>> wrote:
>>>
>>> Hello List.
>>>
>>> I keep running into some Issues when trying to build a Debug Build with
>>> * Clang 10.0.1, build from Git, with VS 2019, Release build
>>> * CMake 3.17.3
>>> * Ninja 1.10
>>> * VS 2019 16.6.2
>>> * Qt 6 Dev Branch: latest Git
>>>
>>> Issue Number 1 is a too long Input Line. No problem with Release builds
>>> though.
>>> "[1/1547] Automatic QML type registration for target
>>> qmlfolderlistmodelplugin
>>> FAILED:
>>> qtdeclarative/src/imports/folderlistmodel/qmlfolderlistmodelplugin_qmltyperegistrations.cpp
>>>
>>> cmd.exe /C "cd /D
>>> C:\Dev\QtSrcx86DevMSVC\qtdeclarative\src\imports\folderlistmodel && set
>>> "PATH=C:\Dev\QtSrcx86DevMSVC\qtdeclarative\bin;C:\Dev\Qtx86DevDebugMSVC\bin;%PATH%"
>>> && C:\Dev\QtSrcx86DevMSVC\qtbase\bin\qmltyperegistrar.exe
>>> --generate-qmltypes=C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/plugins.qmltypes
>>> --import-name=Qt.labs.folderlistmodel --major-version=6
>>> --minor-version=0
>>> @C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/qmltypes/foreign_types.txt
>>> -o
>>> C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/qmlfolderlistmodelplugin_qmltyperegistrations.cpp
>>> C:/Dev/QtSrcx86DevMSVC/qtdeclarative/src/imports/folderlistmodel/meta_types/qt6qmlfolderlistmodelplugin_debug_metatypes.json"
>>> The input line is too long."
>>>
>>> Issue Number 2 is a "mismatch detected for '_ITERATOR_DEBUG_LEVEL'" with
>>> "[4/1547] Linking CXX executable qtbase\bin\lupdate.exe
>>> FAILED: qtbase/bin/lupdate.exe
>>> cmd.exe /C "cd . && C:\Dev\CMake\bin\cmake.exe -E vs_link_exe
>>> --intdir=qttools\src\linguist\lupdate\CMakeFiles\lupdate.dir
>>> --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\rc.exe
>>> --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\mt.exe --manifests  --
>>> C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1426~1.288\bin\Hostx64\x86\link.exe
>>> /nologo @CMakeFiles\lupdate.rsp  /out:qtbase\bin\lupdate.exe
>>> /implib:qttools\src\linguist\lupdate\lupdate.lib
>>> /pdb:qtbase\bin\lupdate.pdb /version:0.0  /machine:X86 /DYNAMICBASE
>>> /SUBSYSTEM:CONSOLE,10.0 /DEBUG:FASTLINK /GUARD:CF /INCREMENTAL /NXCOMPAT
>>> /subsystem:console   -DYNAMICBASE -NXCOMPAT  && cd ."
>>> LINK Pass 1: command
>>> "C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1426~1.288\bin\Hostx64\x86\link.exe
>>> /nologo @CMakeFiles\lupdate.rsp /out:qtbase\bin\lupdate.exe
>>> /implib:qttools\src\linguist\lupdate\lupdate.lib
>>> /pdb:qtbase\bin\lupdate.pdb /version:0.0 /machine:X86 /DYNAMICBASE
>>> /SUBSYSTEM:CONSOLE,10.0 /DEBUG:FASTLINK /GUARD:CF /INCREMENTAL /NXCOMPAT
>>> /subsystem:console -DYNAMICBASE -NXCOMPAT /MANIFEST
>>> /MANIFESTFILE:qttools\src\linguist\lupdate\CMakeFiles\lupdate.dir/intermediate.manifest
>>> qttools\src\linguist\lupdate\CMakeFiles\lupdate.dir/manifest.res" failed
>>> (exit code 1319) with the following output:
>>> clangTooling.lib(Tooling.cpp.obj) : error LNK2038: mismatch detected for
>>> '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in
>>> numerus.cpp.obj
>>> clangTooling.lib(Tooling.cpp.obj) : error LNK2038: mismatch detected for
>>> 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value
>>> 'MDd_DynamicDebug' in numerus.cpp.obj
>>> clangTooling.lib(CommonOptionsParser.cpp.obj) : error LNK2038: mismatch
>>> detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2'
>>> in numerus.cpp.obj
>>> clangTooling.lib(CommonOptionsParser.cpp.obj) : error LNK2038: mismatch
>>> detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match
>>> value 'MDd_DynamicDebug' in numerus.cpp.obj
>>> clangTooling.lib(ArgumentsAdjusters.cpp.obj) : error LNK2038: mismatch
>>> detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2'
>>> in numerus.cpp.obj
>>> clangTooling.lib(ArgumentsAdjusters.cpp.obj) : error LNK2038: mismatch
>>> detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match
>>> value 'MDd_DynamicDebug' in numerus.cpp.obj
>>> [etc. etc. etc.]"
>>>
>>> Yes, I have tested removing the additional Compiler Flags like /Qspectre
>>> etc. - those are not the Problem. And please ignore the Numbers which
>>> counting the build order: I had to restart Ninja to get the Error
>>> Messages - Windows CMD Shell Output is very limited. No matter how high
>>> you set the Buffer Number.
>>>
>>> I am fully aware that the CMake Port is not finished and has a lot of
>>> Issues (having the Qt6 Bugreports Site pinned in the