[Development] Migrate QStateMachine from Qt Core

Karsten Heimrich Karsten.Heimrich at qt.io
Thu Feb 13 13:03:37 CET 2020


HI,

maybe I send out the wrong signal, but currently the suggestion is to keep the implementations, just unify them in a separate module.

-- Karsten

From: Jean-Michaël Celerier <jeanmichael.celerier at gmail.com>
Sent: Donnerstag, 13. Februar 2020 12:03 Uhr
To: Karsten Heimrich <Karsten.Heimrich at qt.io>
Cc: development at qt-project.org
Subject: Re: [Development] Migrate QStateMachine from Qt Core

What has lead to considering that they could eventually be removed ?

Couldn't they be split off in a separate library put in the marketplace or github for instance if they're a thorn ?
No reason to throw away code that works, is there ?



On Thu, Feb 13, 2020 at 10:58 AM Karsten Heimrich <Karsten.Heimrich at qt.io<mailto:Karsten.Heimrich at qt.io>> wrote:
Hi,
we would like to remove the QStatemachine API’s from Qt Core. We identified 2 options to do this:

* Move into QtScXML and keep both the implementation
* rename the module to reflect that it contains 2 different state machine implementations
* Move into Qt5Compat
                * in the long run this will lead to deprecation and removal of the QStateMachine API’s

Right now we consider option 1, merging and keeping QStateMachine and QScxmlStateMachine. Still, I would like to collect some feedback/ ideas/ objections, best would be as comments on https://bugreports.qt.io/browse/QTBUG-81848

Thanks, Karsten

_______________________________________________
Development mailing list
Development at qt-project.org<mailto:Development at qt-project.org>
https://lists.qt-project.org/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200213/74e14856/attachment-0001.html>


More information about the Development mailing list