Re: [Interest] Interest Digest, Vol 114, Issue 23

2021-03-22 Thread Nyall Dawson
On Tue, 23 Mar 2021 at 15:24, Tuukka Turunen wrote: > > > Hi, > > Feedback on the Qt 6 API is valuable and we are very interested in it. > Portability was one of the key design principles and we have avoided making > changes when not needed. That said, there can surely be some items that are >

Re: [Interest] Interest Digest, Vol 114, Issue 23

2021-03-22 Thread Tuukka Turunen
Hi, Feedback on the Qt 6 API is valuable and we are very interested in it. Portability was one of the key design principles and we have avoided making changes when not needed. That said, there can surely be some items that are unnecessarily changed. Knowing what is the problem and the intende

Re: [Interest] The willy-nilly deletion of convenience methods

2021-03-22 Thread Jason H
Surprisingly, I had a good experience with Wt, (webtoolkit.eu) the "web version of Qt" (uses boost). Maybe chromium plus Wt is the way to go? It's commercial, but not as bad as Qt licensing. (GPL2 or commercial) If you don't constantly fracture the code base of humanity every couple years with

Re: [Interest] The willy-nilly deletion of convenience methods

2021-03-22 Thread Max Paperno
On 3/22/2021 7:32 PM, Turtle Creek Software wrote: Re: willy-nilly I can relate to anyone who is unhappy about deprecated functions.  It is never fun when existing code breaks.  We want to be inventing new stuff, not going back and fixing old code just to stay in the same place.  The C+

Re: [Interest] Interest Digest, Vol 114, Issue 23

2021-03-22 Thread Turtle Creek Software
Re: willy-nilly I find this discussion interesting, because we ranted on the Cocoa-dev list for a while and probably sounded a lot like Roland. That was after we spent 3 years porting our C++ desktop app from Mac Carbon to Cocoa, and barely got half done. With huge effort we might have finished

Re: [Interest] The willy-nilly deletion of convenience, , methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Roland Hughes
On 3/22/21 4:03 PM, interest-requ...@qt-project.org wrote: has any framework crossed your way that implements CoW? Honestly, I haven't dug that deep. Been using CopperSpice on RedDiamond editor. Veered off to try porting Gede to CopperSpice so I could finally look at the new strings. Back on

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Roland Hughes
On 3/22/21 4:03 PM, Thiago Macieira wrote: No removals have happened without warning. Please stop the FUD. (who am I kidding? you're not going to stop) All removals were announced by way of deprecation messages, A deprecation message at compile time is __not__ a warning to the installed base

Re: [Interest] The willy-nilly deletion of convenience methods

2021-03-22 Thread Thorsten Glaser
On Mon, 22 Mar 2021, Thiago Macieira wrote: > accomplish the same goal. As shown by the example of the KWallet CLI, there > may be a much better and much simpler solution once the need is understood. I wouldn’t call shouting “API abuse!” at me a “much better” solution. I’m a user here, neither a

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Jérôme Godbout
+1 over her on Qml being my favorite UI framework, did crazy think with it we did render 3D into Qml scene before Qt 3D was there, rendering an engine into texture into our own declarative engine rendering exposed nodes. Multiple QQmlEngine for pipeline flow rendering pass (fast renderin

[Interest] [SPAM] Re: FW: The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Vad Rulezz
Spam detection software, running on the system "mx.qt-project.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. C

Re: [Interest] FW: The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Marcell Varga
Hello Eric, I might be interested in using a solution like that. Also ImGui from my point of view is a little bit too lightweight compared to Qt UI. What is your opinion about: https://github.com/mitsuba-renderer/nanogui? Anyway if you start a project like that I will be interested. Best Regards,

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Bernhard Lindner
Hi Roland, has any framework crossed your way that implements CoW? -- Best Regards, Bernhard Lindner ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest

[Interest] FW: FW: The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread eric.fedosejevs
Neat, thanks for the tip. Have you heard of anyone using LVGL for desktop development? It looks like it should be pretty easy to throw something together using the SDL2-based device simulator as a starting point. Might give it a whirl and see how it compares to ImGUI. From: Jason H > I'm not

Re: [Interest] FW: The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Jason H
> Sent: Monday, March 22, 2021 at 6:54 PM > From: eric.fedosej...@gmail.com > To: interest@qt-project.org > Subject: [Interest] FW: The willy-nilly deletion of convenience, methods > (was: Mixing Commercial and Open...) > > Thank you for your informative reply Roland. I am curious whether any >

[Interest] FW: The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread eric.fedosejevs
Thank you for your informative reply Roland. I am curious whether any companies that you know of have considered switching to a cross-platform windowing library like SDL plus a lean immediate mode GUI (e.g. Dear ImGUI, Nuklear, Nanogui, or whatever else is current)? I really like the idea of doi

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Jason H
> Sent: Monday, March 22, 2021 at 5:18 PM > From: "Roland Hughes" > To: "Jean-Michaël Celerier" , "Jason H" > > Cc: "interest" > Subject: Re: [Interest] The willy-nilly deletion of convenience, methods > (was: Mixing Commercial and Open...) > > > On 3/22/21 10:39 AM, Jean-Michaël Celerier wro

Re: [Interest] The willy-nilly deletion of convenience methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Thiago Macieira
On Monday, 22 March 2021 02:37:08 PDT Benjamin TERRIER wrote: > but the removal of toList(), toSet() & co. is already a pain, and we > basically needed to add helper functions to keep our code readable. I thought we'd fixed that and reverted them. Or didn't we add toContainer? Peppe, what was ou

Re: [Interest] The willy-nilly deletion of convenience methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Thiago Macieira
On Monday, 22 March 2021 02:23:01 PDT Roland Hughes wrote: > Everybody else simply quit Qt when what they needed was nuked without > warning. No removals have happened without warning. Please stop the FUD. (who am I kidding? you're not going to stop) All removals were announced by way of depreca

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Roland Hughes
On 3/22/21 10:39 AM, Jean-Michaël Celerier wrote: > A debian package would go along way to introduce people to Qt there in the hobbyist sector, but it's a compile-it-for-yourself situation ?? http://archive.raspbian.org/raspbian/pool/main/q/qtbase-opensource-src/

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Roland Hughes
There are plenty of C++ developers. They don't work for the slave wages JavaScript hackers do, but there are plenty of C++ developers. More graduate college every year. I've never seen a paid C++ Internship that didn't see dozens of candidates. On 3/22/21 9:39 AM, Vlad Stelmahovsky wrote: The

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Roland Hughes
On 3/22/21 9:22 AM, Jason H wrote: Roland, what did those companies move to? That's what myself and Konrad have been comparing notes on. "The market" hasn't settled on "one thing." The set-top boxes all went to RDK along with Opera browser. The "Explore this computer"/Kiosk market seems to

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread ekke
+1 Qt for me still is the best cross-platform solution for mobile app development enabling me to build great (and performant) apps from one source. from time to time looking at Flutter but still feel better using QML for UI and C++ for the rest. cannot say much about Qt6 yet because I'm wa

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Jean-Michaël Celerier
> A debian package would go along way to introduce people to Qt there in the hobbyist sector, but it's a compile-it-for-yourself situation ?? http://archive.raspbian.org/raspbian/pool/main/q/qtbase-opensource-src/ kind regards, jm On Mon, Mar 22, 2021 at 3:23 PM Jason H wrote: > > > > Even Ja

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Nelson, Michael
+1 for idea that mobile support has not been the priority in QtCo's mind that I need it to be. +1 for idea that filing bug reports and voting for them did not result in my concerns being addressed. UX with QML across mobile and desktop platforms could be better but many issues simply sit unaddre

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Vlad Stelmahovsky
The problem with companies, moving away from Qt, laying only partially with weird licensing rules, which constantly changes (and this is annoying, agreed) The problem mostly with lack of C++ developers. On Mon, Mar 22, 2021 at 1:47 PM Roland Hughes wrote: > On 3/22/21 7:25 AM, Vlad Stelmahovsky

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Frank Hemer
On Montag, 22. März 2021 15:22:37 CET Jason H wrote: > > Even Jason's company, you remember Jason right? QML's biggest, and > > possibly __only__, fan. Even his company dumped Qt. The medical device > > clients I've worked for have also dumped Qt. > > > > It isn't the FUD that is obsolete, just th

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Jason H
> > Even Jason's company, you remember Jason right? QML's biggest, and > possibly __only__, fan. Even his company dumped Qt. The medical device > clients I've worked for have also dumped Qt. > > It isn't the FUD that is obsolete, just the management of Qt. I'm apparently Qt's biggest fan boy? Yes,

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Roland Hughes
On 3/22/21 7:25 AM, Vlad Stelmahovsky wrote: oops. suddenly all the FUD becomes obsoleted On Mon, Mar 22, 2021 at 11:49 AM Allan Sandfeld Jensen mailto:k...@carewolf.com>> wrote: On Montag, 22. März 2021 10:38:09 CET Roland Hughes wrote: > On 3/22/21 4:07 AM, Bernhard Lindner wrote:

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Vlad Stelmahovsky
oops. suddenly all the FUD becomes obsoleted On Mon, Mar 22, 2021 at 11:49 AM Allan Sandfeld Jensen wrote: > On Montag, 22. März 2021 10:38:09 CET Roland Hughes wrote: > > On 3/22/21 4:07 AM, Bernhard Lindner wrote: > > >> Licensing FUD + death-of-perpetual-license + death-of-OpenSource-LTS + >

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Roland Hughes
On 3/22/21 5:19 AM, Vad Rulezz wrote: Hello Roland, Qt devs! On 3/22/21 12:38 PM, Roland Hughes wrote: Even if TQC took back their critical decisions, I can't imagine that people would ever trust them again. This could cause fatal damage to Qt in the long run if they don't sell it to someone

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Henry Skoglund
On 2021-03-22 11:48, Allan Sandfeld Jensen wrote: On Montag, 22. März 2021 10:38:09 CET Roland Hughes wrote: On 3/22/21 4:07 AM, Bernhard Lindner wrote: Licensing FUD + death-of-perpetual-license + death-of-OpenSource-LTS + Qt-6-rolling-out-incomplete + deleted-convenience-methods = customers-l

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Allan Sandfeld Jensen
On Montag, 22. März 2021 10:38:09 CET Roland Hughes wrote: > On 3/22/21 4:07 AM, Bernhard Lindner wrote: > >> Licensing FUD + death-of-perpetual-license + death-of-OpenSource-LTS + > >> Qt-6-rolling-out-incomplete + deleted-convenience-methods = > >> customers-leaving > > > > I wonder if the loss

[Interest] [SPAM] Re: The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Vad Rulezz
Spam detection software, running on the system "mx.qt-project.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. C

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Roland Hughes
On 3/22/21 4:07 AM, Jason H wrote: Is there anything we can do to maybe block the release of new Qt versions, so that the BSD poison pill clause is triggered? Then we can start over from a BSD license, and maybe get other custodians of the code base? Qt is currently catering to automotive com

Re: [Interest] The willy-nilly deletion of convenience methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Philippe
but the removal of toList(), toSet() & co. is already a pain, and we basically needed to add helper functions to keep our code readable. Yes. These are good examples of "small convenient methods" that make (made) Qt containers stand apart (in the positive way) Philippe On Mon, 22 Mar 2021 10:

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Roland Hughes
On 3/22/21 4:07 AM, Bernhard Lindner wrote: Licensing FUD + death-of-perpetual-license + death-of-OpenSource-LTS + Qt-6-rolling-out-incomplete + deleted-convenience-methods = customers-leaving I wonder if the loss of confidence in the current Qt owners can ever be compensated. Even if TQC too

Re: [Interest] The willy-nilly deletion of convenience methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Benjamin TERRIER
On Mon, 22 Mar 2021 at 10:07, Volker Hilsheimer wrote: > > Roland, if you have specific 1st hand porting experience to share and > constructive contributions to make about which APIs we should bring back > because, then please do so. > > > Just to add my experience. A big part of the Qt projects

Re: [Interest] The willy-nilly deletion of convenience methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Roland Hughes
On 3/22/21 4:07 AM, Volker Hilsheimer wrote: On 20 Mar 2021, at 14:22, Roland Hughes wrote: I grepped the archive this morning. Hopefully Andre's email still works. I had hoped he was still watching on here and would pipe up. Maybe he and his company abandoned Qt as well after the June 2020

Re: [Interest] The willy-nilly deletion of convenience methods (was: Mixing Commercial and Open...)

2021-03-22 Thread Volker Hilsheimer
> On 20 Mar 2021, at 14:22, Roland Hughes wrote: > > I grepped the archive this morning. Hopefully Andre's email still works. I > had hoped he was still watching on here and would pipe up. Maybe he and his > company abandoned Qt as well after the June 2020 exchange? > > Here is a scrape of one