[Interest] WebGPU integration in Qt 6.x?

[Michael Jackson]

We are currently developing a desktop widgets based application that uses
VTK as our 3D rendering backend (could not use GPL so that rules out Qt
Data Visualization). VTK still relies on OpenGL but apparently is moving
towards WebGPU as their backend. I’ve done some looking on Google and
cannot quite find if WebGPU is coming to Qt anytime soon (few years in the
future kind of thing). I found New graphics integration in Qt WebEngine 6.6
and even 6.5

that
suggests new graphics backends for QML but maybe not desktop widgets. Could
anyone from Qt comment on WebGPU and its possible integration with a future
version of Qt 6?

Thank You.
--
Mike Jackson
BlueQuartz Software
www.bluequartz.net
www.dream3d.io
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] App release

[Turtle Creek Software]

Yes, that is correct: it's a closed-source app. The plan was to have an
initial free beta period using open-source Qt, then switch to a commercial
Qt license when the paid version is ready.  Getting bug reports is worth
the loss of a few possible sales.

However, if Qt Group wants to back-charge for the development period as
Thiago mentions, then we'll probably just stick with the open-source Qt
license.

Is it cool to ask about hiring subcontractors on this forum?  The
command-line app build process sure isn't beginner friendly.  Probably best
done by someone experienced with it.

Thanks,
Casey McDermott
TurtleSoft.com

*> I'll let Casey confirm, but the way understood it, the license switch
question was regarding the license under which they use Qt.*
*> I.e. they were planning on*
*> - Freeware but closed sourced/proprietary license for app + Qt under
LGPL during beta phase*
*> - Commercial/proprietary licemse for app + Qt under commercial license
when they're out of beta and ready to make money*
*> So the app would never be open source.*
*> Please confirm Casey.*
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] App release

[Elvis Stansvik]

Den tors 21 mars 2024 01:29Turtle Creek Software 
skrev:

> We are ready to release a free alpha version of our accounting app for Mac
> & Windows. The plan is to use LGPL while still in beta, then switch to a
> commercial license and static Qt when it's ready to sell.
>
> Will the switch cause licensing problems?
>
> How do people usually distribute QT for dynamic linking?  Our
> users/testers are not very tech savvy.
>

We bundle the Qt libraries inside our installer which we generate with
CPack. The installer contents is prepared with CMake install directives,
macdeployqt/windeployqt tools from Qt as well as the fixup_bundle helper in
CMake.

Elvis


> Thanks,
> Casey McDermott
> TurtleSoft.com
>
>
> ___
> 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] App release

[Elvis Stansvik]

Den tors 21 mars 2024 01:44Thiago Macieira 
skrev:

> On Wednesday, 20 March 2024 17:27:26 PDT Turtle Creek Software wrote:
> > We are ready to release a free alpha version of our accounting app for
> Mac
> > & Windows. The plan is to use LGPL while still in beta, then switch to a
> > commercial license and static Qt when it's ready to sell.
> >
> > Will the switch cause licensing problems?
>
> The LGPL will not cause you legal problems. But you must remember that the
> licence you gave to those recipients is irrevocable: they can continue
> using
> it, distributing it and even developing it after you've made your
> production
> release. You may want to think more about your business case here, because
> some potential paying customers may decide they don't want to pay you if a
> nearly as good version is open source.
>

I'll let Casey confirm, but the way understood it, the license switch
question was regarding the license under which they use Qt.

I.e. they were planning on

- Freeware but closed sourced/proprietary license for app + Qt under LGPL
during beta phase

- Commercial/proprietary licemse for app + Qt under commercial license when
they're out of beta and ready to make money

So the app would never be open source.

Please confirm Casey.

Elvis


> You should also check with Qt Company sales what terms they'll sell you a
> licence under. In the past, they usually required that you retroactively
> buy
> for the time you spent developing the application.
>
> > How do people usually distribute QT for dynamic linking?  Our
> users/testers
> > are not very tech savvy.
>
> For Mac, it's easy:  use macdeployqt and everything is inside your
> application's bundle.
>
> For Windows, you'll need to make an installer to deploy your .exe and all
> the
> Qt libraries and plugins. windeployqt can prepare the installation target,
> but
> the installer itself is up to you. You can use the Qt Installer Framework
> if
> you wish, or something else.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Principal Engineer - Intel DCAI Cloud Engineering
> ___
> 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