Confidential
>
> From: Ville Voutilainen
> Sent: Tuesday, May 27, 2025 11:28 PM
> To: Volker Hilsheimer
> Cc: Jaroslaw Kobus; development@qt-project.org
> Subject: Re: [Development] Making TaskTree a public API
[...]
> An observat
>
> From: Volker Hilsheimer
> Sent: Tuesday, May 27, 2025 5:35 PM
> To: Jaroslaw Kobus
> Cc: development@qt-project.org
> Subject: Re: [Development] Making TaskTree a public API
>
> Hi Jarek,
>
>
> Thanks for pu
On Tue, 27 May 2025 at 18:37, Volker Hilsheimer via Development
wrote:
> Two thoughts:
>
> - how does TaskTree fit into a C++26 future with sender/receiver
A quick look based on documentation:
1) it's easy to fit a TaskTree into a sender pipeline, it has signals,
so the generic adaptation will j
Hi,
as an addendum to what Volker said, (parts of) the official process are
outlined in https://contribute.qt-project.org/quips/14. Given the history,
there's obviously
no need to add it to playground first, and the aim should be to move it into
the Qt framework (whether as TP or as a full-fl
Volker Hilsheimer (27 May 2025 17:35) wrote:
> The asset-downloader using it might be one reason, but [...] the only
> example that uses that (short of the example showing how to use the
> downloader, which is in qtdeclarative…) is the car-configurator, which
> is in qtdoc. So if there is no other
> On 26 May 2025, at 15:56, Jaroslaw Kobus via Development
> wrote:
>
> Hi All,
>
> I'd like to start a broader discussion about including TaskTree in Qt and
> making it a public API.
>
> TaskTree is a solution broadly used in QtCreator in hundreds of places,
> for convenient managing of sets
