> Personally, I think the exsting QtQuick element should be scrapped and just
> focus on QML
> versions of the existing Widget functionality. I love the QML syntax, hate
> that it's not
> just a layer on top of widgets.
+100
Why this wasn't done from the start is one of the hardest puzzles! I
> Judging from the influx in the CopperSpice world, a lot of companies with
> projects large
> and small are biting the bullet.
How did you come to this result? Are there any hard numbers, links, reports,
etc. that you
can share?
--
Best Regards,
Bernhard Lindner
On Wednesday, 21 April 2021 10:39:01 PDT Giuseppe D'Angelo via Interest wrote:
> But no $X. I'm still not sure what $PROJ means.
The way the example was given, the string "$PROJ" will be written literally to
the Makefile. Make will then interpret it as $(P)ROJ, which is likely not what
you want.
Den ons 21 apr. 2021 kl 20:43 skrev Elvis Stansvik :
>
> Den ons 21 apr. 2021 kl 19:49 skrev Jason H :
> >
> >
> >
> > > Sent: Wednesday, April 21, 2021 at 1:14 PM
> > > From: "Thiago Macieira"
> > > To: interest@qt-project.org
> > > Subject: Re: [Interest] Help a unix guy on windows qmake
> > >
>
For my .pri and qmake build process (I haven’t move to cmake yet) I do some
variable definition for the path:
AMOTUS_Qt_FILESYSTEM_PATH = $$clean_path($$PWD/../FileSystem)
So you could define a variable anywhere you are (relative to the .pro or .pri
files). Might help finding your project root o
Den ons 21 apr. 2021 kl 20:43 skrev Elvis Stansvik :
>
> Den ons 21 apr. 2021 kl 19:49 skrev Jason H :
> >
> >
> >
> > > Sent: Wednesday, April 21, 2021 at 1:14 PM
> > > From: "Thiago Macieira"
> > > To: interest@qt-project.org
> > > Subject: Re: [Interest] Help a unix guy on windows qmake
> > >
>
Den ons 21 apr. 2021 kl 19:49 skrev Jason H :
>
>
>
> > Sent: Wednesday, April 21, 2021 at 1:14 PM
> > From: "Thiago Macieira"
> > To: interest@qt-project.org
> > Subject: Re: [Interest] Help a unix guy on windows qmake
> >
> > On Wednesday, 21 April 2021 09:54:09 PDT Jason H wrote:
> > > Now, whe
On 4/21/2021 11:04 AM, Giuseppe D'Angelo wrote:
On 21/04/2021 17:42, Jason H wrote:
Personally, I think the exsting QtQuick element should be scrapped and
just focus on QML versions of the existing Widget functionality. I love
the QML syntax, hate that it's not just a layer on top of widgets.
T
Boas Rui,
> On 21 Apr 2021, at 18:24, Rui Oliveira wrote:
> I did notice your product line before, when you first answered me.
>
> I like the look! Would you like to tell a bit about your experience in moving
> to Qt Quick? What were your main barriers?
>
As I just mentioned in my last emai
> Sent: Wednesday, April 21, 2021 at 1:14 PM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] Help a unix guy on windows qmake
>
> On Wednesday, 21 April 2021 09:54:09 PDT Jason H wrote:
> > Now, when compiling, regardless of shadow build or not, refer to the lib
On 21/04/2021 19:14, Thiago Macieira wrote:
qmake does not expand environment variables at all.
$ X=A qmake Y=b /dev/stdin -o /dev/null <<<'message(r = $X $$Y)'
Project MESSAGE: r = $X b
AFAIK, there's distinct syntax for everything:
$$X is a qmake variable called X
$$(X) is an environment va
On Wed, 21 Apr 2021, Giuseppe D'Angelo via Interest wrote:
> I'm not sure where to find QML on desktop stories, there's however a showroom
> https://showroom.qt.io/ where people can leave links to their applications.
You can probably add MuseScore 4 to that list. Mu͒4 is not yet finished but
it’s
Olá Nuno,
I did notice your product line before, when you first answered me.
I like the look! Would you like to tell a bit about your experience in
moving to Qt Quick? What were your main barriers? And how much work was
it to get this look?
They should give you a talk time at a Qt days!
Ru
On Wednesday, 21 April 2021 09:54:09 PDT Jason H wrote:
> Now, when compiling, regardless of shadow build or not, refer to the libs by
> adding to the project: +++ project.pro
> + mingw {
> + INCLUDEPATH += $PROJ/libraries/win/include
> + LIBS += -L$PROJ/libraries/win/$ARCH -lvendor
> + }
>
On Wednesday, 21 April 2021 09:54:09 PDT Jason H wrote:
> MinGW is not x64? It's running on a fairly recent windows 10 machine.
"mingw32" means "Minimal GNU for Win32" and Win32 is the name of the API set.
It's historical and applies to 64-bit too. That's why the mkspecs for windows
are win32-ms
On Wednesday, 21 April 2021 08:49:02 PDT Jason H wrote:
> I'm having a bugger of a time getting a project working under windows. I've
> been doit under mac and linux for the last many years. What is the proper
> scope? Allegedly these are listed in C:\Qt\$ver\$compiler\mkspecs, however
> there are
> Sent: Wednesday, April 21, 2021 at 12:04 PM
> From: "Giuseppe D'Angelo via Interest"
> To: interest@qt-project.org
> Subject: Re: [Interest] Help a unix guy on windows qmake
>
> On 21/04/2021 17:49, Jason H wrote:
> > What is the proper scope? Allegedly these are listed in
> > C:\Qt\$ver\$com
> On 21/04/2021 17:42, Jason H wrote:
> > Personally, I think the exsting QtQuick element should be scrapped and
> > just focus on QML versions of the existing Widget functionality. I love
> > the QML syntax, hate that it's not just a layer on top of widgets.
> > That said, I still really like both
For me, the major benefit of Qml is speed. Before using Qml I’ve done a couple
of years doing Qt Widgets. The glue code to make things work is a big pain. You
can declare interfaces so easily in Qml, and still have the ability to quickly
change everything without having to rewrite all the glue c
Hello Vadim,
Thanks for asking! We have provided non-commercial OSS projects with free
licenses in the past. Please contact me off-list with information about
your project. I'll see what can be done.
Harri.
On Mon, 19 Apr 2021, Vadim Peretokin wrote:
Following the news that Qt has acquired
I'm amazed. The GldSrc and the Source engines aren't famous for being
super easy to work with. And somehow Qt Quick can be integrated to make
the menus? Damn, I'd like to see that source code.
Although, this reminded me of a related example: https://sciter.com/
(notice the first example in the
At least, it would be convenient to reap the benefits of QML: HW
acceleration, for example.
I personally don't care for QML. I would prefer to write everything in
C++. But that's me. If there was a "no-QML-Quick-API" I'd be so much
happy. No more gluing code and properties and questions like t
On 21/04/2021 17:49, Jason H wrote:
What is the proper scope? Allegedly these are listed in
C:\Qt\$ver\$compiler\mkspecs, however there are no win64 ones. I'm using mingw.
mingw is the proper scope. When in doubt, look at Qt's own sources.
src/angle/src/libEGL/libEGL.pro
19:mingw:equals(
On 21/04/2021 16:10, Rui Oliveira wrote:
Black Mesa Source?! Now that's an interesting one haha!
Yep, https://steamdb.info/depot/362894/ shows some familiar names in the
installed libs. (That having been said, Qt is used only in the menus
AFAIK :-))
Thanks,
--
Giuseppe D'Angelo | giuseppe.
I'm having a bugger of a time getting a project working under windows. I've
been doit under mac and linux for the last many years.
What is the proper scope? Allegedly these are listed in
C:\Qt\$ver\$compiler\mkspecs, however there are no win64 ones. I'm using mingw.
Why is there no $PROJ variabl
On 21/04/2021 17:42, Jason H wrote:
Personally, I think the exsting QtQuick element should be scrapped and
just focus on QML versions of the existing Widget functionality. I love
the QML syntax, hate that it's not just a layer on top of widgets.
That said, I still really like both.
Do you mea
You probably won't -- it's too new. Unless you call automotive Infotainment consoles success stories.
The lack of proper QtQuick Controls (v2) held it back for a while.
Personally, I think the exsting QtQuick element should be scrapped and just focus on QML versions of the existing Widget fun
I took another look at the showcase and am still having trouble finding any
substantial desktop application built with QML.
Desktops may now be a niche corner of the market, but they are still where
most productivity occurs. Software is still being actively developed and
sold for desktops and t
Hey Giuseppe, and discussion list!
I did watch all of those. In fact, my original post cites you directly,
from a talk I believe to have happened in that event also.
Black Mesa Source?! Now that's an interesting one haha!
Anyway, some good information that I got here. Good to see someone from
> On 21 Apr 2021, at 15:48, Alex Shaw wrote:
>
> Hello,
>
> I am relatively new to mailing lists, so if I am doing something wrong here
> please forgive me.
>
> Is this the place to ask questions about the internals of Qt modules?
>
> More specifically:
> In QtDeclarative, can a QV4::Returned
Hi Alex,
On 21/04/2021 15:48, Alex Shaw wrote:
I am relatively new to mailing lists, so if I am doing something wrong
here please forgive me.
Is this the place to ask questions about the internals of Qt modules?
I'd actually recommend you to ask this question on the development@
mailing lis
Hello,
I am relatively new to mailing lists, so if I am doing something wrong here
please forgive me.
Is this the place to ask questions about the internals of Qt modules?
More specifically:
In QtDeclarative, can a QV4::ReturnedValue or a QV4::Value be converted
into an ExecutableCompilationUnit
On 21/04/2021 14:37, eric.fedosej...@gmail.com wrote:
Where are the examples of real QML desktop applications on The Qt Co. website?
I did a quick walk through the customer showcase and cannot find them.
Well the question was about embedded :)
I'm not sure where to find QML on desktop stories
You might want to give the showroom a look, some of them are Qml based:
https://showroom.qt.io/
Some use the Felgo layer:
https://felgo.com/resources/success-stories
http://en.esotericsoftware.com/forum/Facial-Animation-in-Qml-and-pushing-past-the-Spine-limits-3788
http://en.esotericsoftware.com/
Where are the examples of real QML desktop applications on The Qt Co. website?
I did a quick walk through the customer showcase and cannot find them.
From: Interest On Behalf Of Giuseppe D'Angelo
via Interest
Sent: Monday, April 19, 2021 8:36 AM
This is false, as a quick walk through the custo
On 4/21/2021 7:17 AM, Vlad Stelmahovsky wrote:
On Wed, Apr 21, 2021 at 1:50 PM Roland Hughes
mailto:rol...@logikalsolutions.com>> wrote:
On 4/21/2021 6:36 AM, Vlad Stelmahovsky wrote:
Using Electron has nothing to do with licensing issues. The issue
is common programming knowl
On Wed, Apr 21, 2021 at 1:50 PM Roland Hughes
wrote:
>
> On 4/21/2021 6:36 AM, Vlad Stelmahovsky wrote:
>
> Using Electron has nothing to do with licensing issues. The issue is
> common programming knowledge level is going down when programmers paradise
> promised for newcomers: learn HTML progra
On 4/20/2021 4:35 PM, Alexey Rusakov wrote:
Am I the only one to feel that Roland monopolises the mailing list again,
after a couple of years?
I'm sorry you feel that way. You can join the growing chorus to have
Giuseppe D'Angelo placed on 18 month forced hibernation due to
reprehensible beh
On 4/21/2021 6:36 AM, Vlad Stelmahovsky wrote:
Using Electron has nothing to do with licensing issues. The issue is
common programming knowledge level is going down when programmers
paradise promised for newcomers: learn HTML programming language
(sic!) and you are rich
btw, is Electron licen
Using Electron has nothing to do with licensing issues. The issue is common
programming knowledge level is going down when programmers paradise
promised for newcomers: learn HTML programming language (sic!) and you are
rich
btw, is Electron licensed for use in medical devices?
On Wed, Apr 21, 2021
LOL,
I never said it wasn't. I said phones and John Deere. My point was this:
>That tiny subset on the Web site doesn't scratch the surface.
Of course the total number of embedded systems using Qt of any flavor is
going down as much of the market is moving to Electron and other
libraries give
With these numbers are you trying to convince me that QML is not used in
embedded? or what?
On Wed, Apr 21, 2021 at 1:21 PM Roland Hughes
wrote:
>
> On 4/21/2021 12:14 AM, Vlad Stelmahovsky wrote:
>
>
>
> On Tue, Apr 20, 2021 at 3:13 PM Roland Hughes
> wrote:
>
>>
>> On 4/20/2021 5:00 AM, Giuse
On 4/21/2021 12:14 AM, Vlad Stelmahovsky wrote:
On Tue, Apr 20, 2021 at 3:13 PM Roland Hughes
mailto:rol...@logikalsolutions.com>> wrote:
On 4/20/2021 5:00 AM, Giuseppe D'Angelo wrote:
On 18/04/2021 14:50, Roland Hughes wrote:
It's completely true. That tiny subset on the Web
Rui,
You need to extend QQuickItem and create your scene graph.
Open QtCreator and search for scene graph examples. Take a special look to
"Scene Graph - Custom Geometry”
Best,
Nuno
> On 15 Apr 2021, at 11:25, Rui Oliveira wrote:
>
> Hey,
> As per the title implies, I would like some commen
I am ambidextrous when it comes to Quick and Widgets.
If you want it to look modern, use Quick. If you want more business-retro, use
widgets. Widgets still has better UX, but it is not as bad as it used to be.
You can do what you want in Quick, with C++ QQuickImageProvider subclass. It's
a lit
It doesn't look to have any proper maintenance since 2017 and lacks plans
for Qt6, so that doesn't look like a viable option to invest lots of effort
into.
Given the recent bad press for Qt regarding open-source, QtC opening up
Squish for open-source use would definitely be some good news.
On Tue
Hi,
I've got a project that has dependencies.
These dependencies have their own .pri file. Most of these dependencies
are just libraries that are built using another IDE-generated makefile.
I want these dependencies to be cleaned when I clean or rebuild my
project using QtCreator. I have no
47 matches
Mail list logo
