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 fo
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 lic
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 li
For the "Installer" we just package up everything into a standalone package
and zip it up. No installer necessary. Not sure of the downsides but seems
easier for our users to just right-click and expand the archive and run.
—
Mike Jackson
On Wed, Mar 20, 2024 at 8:44 PM Thiago Macieira
wrote:
>
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 swi
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 l
