Porting a Large Scale Non-Qt Legacy CAD Application to Qt/QML: The Good, The Bad, and The Ugly
Abstract: Over the last 3 years, we have been working on porting our large legacy CAD software (Alias) to using Qt/QML for UI. We had been using an in-house developed UI framework for the last 30+ years and it was time to upgrade to something more modern to empower our designers and take pressure off of our developers to make them more productive with easier and more intuitive tools. Because of the state of our application, we have taken an all-in approach where we disabled the UI for our CAD software and began building everything bit by bit. During this project, we not only refactored and changed the technology we use for our UI but also the way we work within our team across disciplines.
About the Speaker: Furkan Uzumcu is a senior software engineer at Autodesk. He has worked with many languages and backend, and end frontend systems to solve problems. He's passionate about good UX, software architecture, and design. He's worked with Qt/QML for over 8 years, and developed software for desktop and mobile devices. He's been working at Autodesk for the past 4 years, on the architecture and the user interface of a large 3D CAD software. When he's not working, he enjoys reading, rock climbing, running, and building mechanical keyboards.
Oh, here is more
Maximize ROI and Streamline Development with Qt
Modern development demands agility, performance, and a seamless user experience across platforms and...
Watch videoWebinar: Accelerating Industrial AI Applications
Artificial intelligence is redefining industrial automation—driving the evolution toward modular, so...
Watch videoData Modul - Qt World Summit 2025
Learn how Qt helps Data Modul save time and costs for the creation of Industry-grade displays and HM...
Watch videoHarman - Qt World Summit 2025
Learn how Harman uses Qt Framework for Automotive HMI development and as an accelerator to unlock co...
Watch video