Bring legacy toolkits to Qt. Use KDAB's proven porting experience
KDAB has unique experience in porting the code base for toolkits like Qt 3, Qt 4, Motif, Java, Tcl, GTK, .NET, MFC, and Photon to Qt 5. Porting a legacy GUI toolkits to Qt5 is often a job where proven experience saves a lot of time.
Benefits of porting Qt3, Qt4 and/or other legacy GUI Toolkits to Qt5 include :
- easier to maintain
- runs faster
- more flexible where style is concerned
- works on multiple platforms
- looks more professional
- is modern, making it easier to find developers to work for you
KDAB: Multiple migration projects with millions of Lines of Code (LOC)
We help you modernize your legacy code in a fast and reliable manner by using specialized tools and in-depth know-how from migration projects in different industries with millions of Lines of Code (LOC).
-
KDAB’s code migration of GUI-toolkits includes:
- reviews by our own senior engineers
- analysis using our own proprietary analysis tools
- back-ported, refactored and ready to ship version of the complete source code you provided to us
A code migration project usually includes a one week handover training at the end of the project. These sessions will include teaching Qt programming techniques as well as a familiarization with the specific patterns our engineers have applied to your code.
To explore your possibilities
Overview: KDAB code migration of GUI-toolkits:
- free in-depth analysis report*
- changing old classes to current Qt classes
- reworking outdated architectural/design patterns to Model-view based lists
- converting code for painting, multi-threading and data access
- replacing unsupported third party tools with new or custom-made components
*free in-depth analysis report, if you decide to use us for the project
The in-depth analysis report covers areas such as:
- initial code analysis by our migration experts, often as part of a one-day workshop, followed by –
- an additional analysis with KDAB proprietary analysis tools
- the application context
- the advantages of porting
- the setup of the source code, scripts etc.
- modules used in the source code
- potential migration steps
- how to compile, usage of KDAB’s porting scripts etc.
- considerations regarding fixing runtimes differences, avoiding regressions…
- porting away deprecated layout, widget methods, containers…
- cost and time estimates for migrating the identified modules
- how the work would be organized
6 Steps for Legacy Software Migrations
Also, view our Porting Applications to Qt video, a presentation about migrating to Qt.
To explore your migration possibilities