Details
-
Epic
-
Resolution: Done
-
P2: Important
-
6.0
-
None
-
QtStateMachine6
-
-
20
Description
Usual steps involved in the migration process:
- Port to CMake and verify
- Synchronize MOC code with qtbase
- Verify qtdeclarative dependency, necessary to split module in two libraries?
- Apply API changes / ,modernization of dependent modules (qtbase, qtdeclarative)
- Apply binding support where beneficial (see QTBUG-85271)
- Example improvements and verification
- Unit test improvements and cleanup of blacklisted tests (if applicable unblacklist or remove)
- Improve documentation
- Investigate option to rename the module to qtstatemachine
- Verify proper support of state machine QML plugins
Attachments
Issue Links
- depends on
-
QTBUG-89847 Qt SCXML: Unite component XML: SCXML and Core: State Machine
- In Progress
-
QTBUG-89828 Qt SCXML: Port module to cmake build system
- Closed
-
QTBUG-89830 Qt SCXML: Synchronize MOC code with qtbase and create patch file
- Closed
-
QTBUG-89831 Qt SCXML: Verify qtdeclarative dependency, is it necessary to split module in two libraries?
- Closed
-
QTBUG-89832 Qt SCXML: Apply API changes/ modernization of dependent modules
- Closed
-
QTBUG-89833 Qt SCXML: Improve and verify documentation
- Closed
-
QTBUG-89834 Qt SCXML: Improve and verifiy examples
- Closed
-
QTBUG-89836 Qt SCXML: Improve, verify and/or fix tests
- Closed
-
QTBUG-89845 Qt SCXML: Bug triaging/ fixing
- Closed
-
QTBUG-89895 Qt SCXML: add QProperty binding support where beneficial
- Closed
-
QTBUG-91151 Verify Qt 6 SCXML module's interoperability with Qt Creator's SCXML editor
- Closed
-
QTBUG-91375 Qt StateMachine: add QProperty binding support where beneficial
- Closed
-
QTBUG-89837 Qt SCXML: Rename the module to a more general name, e.g. qtstatemachine
- Withdrawn
- is required for
-
QTBUG-89504 Module Migration for Qt 6.1
- Closed
-
QTBUG-89509 Module Migration for Qt 6.2
- Closed
- resulted from
-
QTBUG-85271 Use new QProperty throughout Qt
- Open
- mentioned in
-
Page Loading...