On Friday, 8 December 2023 07:22:30 PST Dominik Holland via Development wrote:
> Although not part of qt5.git the interface framework is part of Qt DCE
> for quite some time already and also used by customers. From a
> qt-project standpoint that module doesn't exist and is not part of
>
hursday, 7 December 2023 18:37
*To:*Tuukka Turunen
*Cc:*Macieira, Thiago ;
development@qt-project.org
*Subject:*Re: [Development] Requesting a repository for Qt Interface
Framework Reference APIs
If it’s an option to rename this module we should take the
opportunity to do so I think.
The problem of t
rg
Subject: Re: [Development] Requesting a repository for Qt Interface Framework
Reference APIs
If it’s an option to rename this module we should take the opportunity to do so
I think.
The problem of the generic naming came up in the past, but the understanding
was that it was too late
ra, Thiago ; development@qt-project.org
Subject: Re: [Development] Requesting a repository for Qt Interface Framework
Reference APIs
If it’s an option to rename this module we should take the opportunity to do so
I think.
The problem of the generic naming came up in the past, but the und
ø ; Tuukka Turunen
Cc: Macieira, Thiago ; development@qt-project.org
Subject: Re: [Development] Requesting a repository for Qt Interface Framework
Reference APIs
⚠ This email originates from outside the organization or the sender could not
be verified.
You are absolutely correct that t
: Thursday, 7 December 2023 18:37
> To: Tuukka Turunen
> Cc: Macieira, Thiago ; development@qt-project.org
> Subject: Re: [Development] Requesting a repository for Qt Interface Framework
> Reference APIs
>
>
>
> If it’s an option to rename this module we should t
; development@qt-project.org
Subject: Re: [Development] Requesting a repository for Qt Interface Framework
Reference APIs
If it’s an option to rename this module we should take the opportunity to do so
I think.
The problem of the generic naming came up in the past, but the understanding
pment@qt-project.org>
mailto:development@qt-project.org>>
Subject: Re: [Development] Requesting a repository for Qt Interface Framework
Reference APIs
On Tuesday, 5 December 2023 08:54:29 PST Thiago Macieira wrote:
> Then why are you asking for a repository if it's already there? When was
On Thursday, 7 December 2023 08:02:15 PST Tuukka Turunen via Development
wrote:
> So the question is what should this module be called, if it would be
> renamed?
I would indeed want to know what these are interfaces of or for. Like I said,
they are not network interfaces, which is the first
From: Development on behalf of Thiago
Macieira
Date: Tuesday, December 5, 2023 at 19:06
To: development@qt-project.org
Subject: Re: [Development] Requesting a repository for Qt Interface Framework
Reference APIs
On Tuesday, 5 December 2023 08:54:29 PST Thiago Macieira wrote:
> Then
On Tuesday, 5 December 2023 08:54:29 PST Thiago Macieira wrote:
> Then why are you asking for a repository if it's already there? When was
> that module approved by the Qt Project? I can't find anything in the email
> archives.
>
> The first commit in this repository is "First version of the
On Tuesday, 5 December 2023 07:54:51 PST Dominik Holland via Development
wrote:
> It's not a question to import something, the module literally already
> exist here: https://code.qt.io/cgit/qt/qtinterfaceframework.git for
> quite some time and for that there is a source and binary compatibility.
Am 12/5/23 um 16:34 schrieb Thiago Macieira:
On Tuesday, 5 December 2023 04:17:08 PST Dominik Holland via Development
wrote:
Right, but at the same time we cannot change of the module and all it's
classes afterwards.
Yes, you can. Any code imported into the Qt Project is subject to API
On Tuesday, 5 December 2023 04:17:08 PST Dominik Holland via Development
wrote:
> Right, but at the same time we cannot change of the module and all it's
> classes afterwards.
Yes, you can. Any code imported into the Qt Project is subject to API reviews
and may therefore be different than when
Dominik Holland (5 December 2023 10:03) replied:
The Qt Interface Framework is a module which already exists
(https://doc.qt.io/QtInterfaceFramework) that's what the Reference
APIs are based on.
That doesn't change the fact that the name is rather generic (and leads
to the prefix qtif, which
Yes, this is also in line with a request I had made about the same – and the
documentation has already had some attention in regard to migrating away the
“reference” APIs to differentiate the “core” APIs to affect wider adoption.
+1 from me.
Mike
Confidentiality Notice: This message
On Monday, 4 December 2023 02:10:43 PST Dominik Holland via Development wrote:
>>> the qtinterfaceframework module currently also hosts two reference
>>> APIs (qtifmedia and qtifvehiclefunctions). Both are very much
>>> automotive specific. In order to make the module also available for
>>> other
Am 12/4/23 um 20:34 schrieb Thiago Macieira:
On Monday, 4 December 2023 02:10:43 PST Dominik Holland via Development wrote:
the qtinterfaceframework module currently also hosts two reference APIs
(qtifmedia and qtifvehiclefunctions). Both are very much automotive
specific. In order to make
On Monday, 4 December 2023 02:10:43 PST Dominik Holland via Development wrote:
> the qtinterfaceframework module currently also hosts two reference APIs
> (qtifmedia and qtifvehiclefunctions). Both are very much automotive
> specific. In order to make the module also available for other industries
Hi,
the qtinterfaceframework module currently also hosts two reference APIs
(qtifmedia and qtifvehiclefunctions). Both are very much automotive specific.
In order to make the module also available for other industries we would like
to move those two modules to a new qt-labs repository.
Name
20 matches
Mail list logo
