TaskTree: Difference between revisions
m (Grammar fix, I hope :)) |
No edit summary |
||
| Line 39: | Line 39: | ||
|} | |} | ||
[[File:TaskTree.jpg|thumb|The first public TaskTree presentation on Sep 28th 2023 at Felgo office, Vienna.]] | [[File:TaskTree.jpg|thumb|The first public TaskTree presentation on Sep 28th 2023 at Felgo office, Vienna.]] | ||
[[File:Spyrosoft.jpg|thumb|TaskTree presentation in Technopark Pomerania at the invitation of Spyrosoft on 18 Oct 2023.]] | |||
Revision as of 18:13, 24 May 2024
TaskTree - generic solution for automatic management of asynchronous tasks (C++)
TaskTree automatically manages a chain (or a tree) of asynchronous tasks of mixed types, including running processes, network queries, functions in separate threads, animations, timers, and so on... It's easily extensible with any other types of asynchronous tasks.
The recipe on how to run and manage the conglomerate of tasks is described in a declarative way in C++.
The recipes are enclosed in copyable value-type objects and may be run many times, or be part of more general recipes.
The TaskTree is broadly used in QtCreator, for executing Build / Deploy configurations, Locator filter, Clang tool, Autotests, driving Axivion plugin's communication and much more...
The TaskTree's implementation is separated from the QtCreator specific code and may already serve as a general purpose solution outside of QtCreator.
Notes from the presentation/discussion at Qt Contributors Summit 2023: TaskTree CS23
