Port Flash4Linux to Qt 5.12

@MuhammadUzair16

Hi I am a software engineer with over 16 years of experience. I have extensive experience with C++, Qt Widgets, Linux desktop applications, and modernizing legacy code without changing established behaviour. I can migrate Flash4Linux from its deprecated Qt3 APIs to Qt 5.12, replacing obsolete widgets, signals/slots, dialogs, and build configuration while preserving the original screens, menus, command-line options, and workflow. I will use the current release as the visual and functional baseline, compare the interface during the port, and provide a clean project that builds from scratch without warnings. Any internal refactoring will remain focused on compatibility rather than redesign. Which Linux distribution and compiler will you use for final acceptance, and do you have a working original build or reference screenshots available for regression comparison? Please contact me to discuss details.

@anandinfraveo

**I can start your Flash4Linux Qt3 to Qt5.12 port today and keep it looking exactly like the original** I am Anand, full-stack dev focused on Linux desktop ports and legacy Qt migrations for small teams. I read your repo and your priorities are clear. I will migrate the full codebase to Qt 5.12, replicate all screens menus and dialogs pixel-for-pixel with no layout or style changes, refactor deprecated Qt3 classes behind the scenes, and preserve all external functionality and command-line options. Deliverables: A clean warning-free Qt 5.12 project that compiles from scratch and passes your regression check against the current feature set. Recent work: Migrated Qt3 file manager to Qt5 with identical UI, Ported Qt4 serial tool to Qt 5.12 warning-free. Can you confirm which distro and compiler you will use for the final build test so I match it exactly

@bohdan38

Hi, Porting Flash4Linux from deprecated Qt3 APIs to Qt 5.12 requires preserving the original screens, menus, dialogs, command-line behavior, and visual presentation while replacing obsolete framework code. The priority is a clean build without changing the user-facing experience. The implementation will modernize project configuration and Qt classes, resolve compilation and compatibility issues, and retain existing application behavior. I will compare the migrated interface against the original release, focusing on practical pixel-level fidelity and avoiding unnecessary layout or styling changes. Similar work includes maintaining legacy application behavior while upgrading frontend and backend foundations, with careful API replacement and regression-focused testing. The supplied repository can be reviewed first to align the migration with its current structure. The first working milestone will provide a clean, warning-free Qt 5.12 project that builds from scratch, with documented changes and regression checks completed within seven days. Best regards, Bohdan

@emilesd617

Hi, I am a C++ and Qt developer with 8 years of rich experience in software development, with a background in porting legacy codebases across Qt versions. For Flash4Linux, I would replace the deprecated Qt3 classes and headers with their Qt 5.12 equivalents, rebuild the widgets, menus and dialogs to match the original layout pixel for pixel, and keep every command-line option and external behavior unchanged so the build compiles clean and warning-free from a fresh clone. I am familiar with C++, Qt, Qt3 to Qt5 Migration, Qt Widgets, Linux Build Systems, etc. I'm an individual freelancer and can work on any time zone you want. Please contact me with the best time for you to have a quick chat. Looking forward to discussing more details. Thanks. Emile.

@shadabkhan92

As an experienced software engineer with a strong proficiency in C++ programming, I am confident that I can handle your project efficiently. Over the years, I've specialized in seamless migrations of large codebases from deprecated platforms and libraries to newer ones - a skill that would be immensely valuable in porting Flash4Linux to Qt 5.12. While undertaking such migrations, I understand the importance of maintaining consistency and not disrupting the existing functionality. Therefore, my approach will be focused on replicating all user-facing screens, menus, and dialogs perfectly to ensure that the application's look and behavior stays identical. To expand on my relevant experience, beyond C++ development, I have substantial expertise across different technological domains such as Odoo ERP, IoT hardware design & firmware development, as well as web and mobile stack using React, Flutter, Django, Node. These diversified skills uniquely equip me in dealing with complex and cross-functional projects like yours where AI is embedded into ERP workflows and interacts with live sensor data – thereby giving your project the necessary edge.

@naminghn

Hi there, I see you need to migrate the Flash4Linux codebase from the deprecated Qt3 API to Qt 5.12 while maintaining the original look and behavior. I can assure you that I’ll replicate the user-facing screens, menus, and dialogs pixel-for-pixel, adhering closely to your specifications. While refactoring the back-end components for compatibility, I will ensure that all external functionalities and command-line options remain intact as per your requirements. I’ll maintain a clean, warning-free project ready for your regression checks, and I'm open to suggesting improvements for future phases if needed. Regards, Ali

@carlosd178

Hello, I’ve reviewed the Flash4Linux migration requirements and understand the priority: move the existing Qt3/C++ codebase to Qt 5.12 while preserving the original UI, behaviour, command-line options, and overall user experience. I’m comfortable with C++, Qt, legacy-code migration, build debugging, and refactoring deprecated APIs. My approach would be to first establish the current application structure and build dependencies, then migrate Qt3-specific classes, signals/slots, widgets, containers, file/process handling, and build configuration incrementally. I’ll keep UI changes to the absolute minimum and compare screens, menus, dialogs, sizing, and behaviour against the original application throughout the port. The final project will build cleanly from scratch under Qt 5.12 without relying on obsolete Qt3 compatibility APIs. Any optional modernization I identify will be kept separate so it doesn’t affect this migration phase. A couple of quick questions: • Which Linux distribution should be the primary build/test target? • Do you want the existing build system preserved, or is converting it to CMake/qmake acceptable? I’m available to start immediately. Best regards, Carlos.

@richardb063

Hi, starting with the Qt3 dependencies and build errors so the migration path is clear before anything is ported. Getting you a warning-free Qt 5.12 build where the screens, menus, and dialogs look exactly as they did in the original is the goal. Previously I have ported Qt3 code where the biggest work was replacing deprecated classes like Q3ListView and Q3TextEdit, since those have no direct Qt5 equivalent and needed custom widgets to keep the same appearance. I would work through the classes, refactor behind the scenes where it helps, and keep every command-line option and user-facing behaviour intact. You will get a clean project that compiles from scratch, ready for your regression check. I am determined to win this project and confident I can deliver high quality results within your deadline if awarded. Talk soon.

@OptimumGrpCorp

Hi, I can migrate Flash4Linux to Qt 5.12, ensuring the application retains its original look and behavior. I will prioritize replicating user-facing screens, menus, and dialogs exactly as they are, while modernizing the codebase behind the scenes. The deliverable will be a clean, warning-free Qt 5.12 project that compiles successfully. I will conduct thorough testing, including building from scratch and running regression checks to ensure all current features work seamlessly. I am available to work in your timezone and am ready to begin working on this project to deliver the required solution. Looking forward to moving forward with this project.

@manh2906

Hello, I’m Manh. I can take the Flash4Linux codebase through a careful Qt3-to-Qt 5.12 migration while keeping the original interface, behavior and command-line functionality intact. I’ll first review the existing project structure and identify deprecated Qt3 APIs, classes, build configuration and compatibility issues. I’ll then replace outdated APIs with their Qt 5.12 equivalents, update the project/build files, resolve compiler errors and warnings, and refactor only where necessary to maintain compatibility. The UI will remain a priority throughout the migration. I’ll preserve the existing menus, dialogs, layouts, controls, styling and application flow as closely as practical rather than redesigning the interface. I’ll also verify command-line options and existing functionality after the port. Before delivery, I’ll build the project from a clean environment, run regression checks against the existing feature set, address warnings and document any compatibility considerations. The final result will be a clean Qt 5.12 project ready for your from-scratch build and testing. Looking forward to working with you. Thanks.

@sufyanasmat38

Hello, I have experience with C++, Qt, and migrating legacy applications to newer Qt versions while preserving existing functionality and UI behaviour. We can migrate the Qt3 codebase to Qt 5.12, replace deprecated APIs and classes, resolve build issues, and carefully preserve the original screens, menus, dialogs, command-line behaviour, and overall application flow. We’ll also validate the project with a clean build and regression testing on a current Linux distribution. Are there any custom Qt3 widgets or UI components in the application that rely on behaviour not directly available in Qt 5.12?

@karolz44

⭐ Similar Experience: Migrating legacy Qt3 C++ codebases to Qt 5.12 while keeping the UI pixel-for-pixel identical Hi there, ✋ I've finished the reading your job description and I really get who you're looking for. I'm writing this proposal by hand, as a developer who has pretty rich experience in C++ Programming and cross-platform desktop UI work Flash4Linux is a classic legacy-rescue job: the whole codebase is glued to the retired Qt3 API, so the real work is mapping every QWidget, menu and dialog onto Qt 5.12 without a single pixel drifting. I'd start by inventorying the old classes, swapping Q3MainWindow/Q3ListView-style constructs for their modern equivalents, then rebuilding the .pro/qmake files so a from-scratch build comes out clean and warning-free on current distributions. The command-line options and external behaviour stay frozen , no new layouts, no restyling, exactly the original look. Breating old desktop apps back to life is my bread and butter, and replicating a GUI pixel-for-pixel uses the same discipline I apply when I port a React Native screen, where a one-pixel offset is instantly obvious. I keep build tooling lean too , even when a stack is more Typescript and web scaffolding than native, the same tidy pipelines apply. No Artificial Intelligence guesswork here, just careful refactors plus a regression pass against the current feature set so your from-scratch build runs identically. ⏱️ => ⏱️ I'm available for 40+ work hours per week for this proje

@shaynegg

Hi, I like this kind of migration work because the challenge is modernising the code without changing what users already know. I’d start by building Flash4Linux and identifying the Qt3 dependencies, then replace deprecated APIs with Qt 5.12 equivalents while preserving the existing screens, menus, dialogs, and command-line behaviour. I’d pay particular attention to layout metrics, widget styling, and signal/slot changes to keep the interface as close to pixel-identical as practical. Finally, I’d build from a clean checkout, resolve compiler warnings, and run regression tests. Are there specific Linux distributions or compiler versions you’ll use for acceptance testing?

@hakan1022

Hi, there I successfully migrated a complex Qt3 application to Qt 5.12, similar to Flash4Linux, for a client in the finance industry. The project involved refactoring outdated classes and replacing deprecated APIs while maintaining the original application's look and feel. I implemented a custom widget set to replicate the original screens, menus, and dialogs pixel-perfectly, without introducing any new styles. I also refactored the application's core logic to utilize Qt 5.12's features, such as improved signal-slot connectivity and enhanced performance. To achieve the desired outcome, I plan to create a custom widget set using Qt 5.12's Graphics View framework, which will enable precise replication of the original application's user interface. I will also utilize Qt's built-in migration tools and my expertise in Qt 5.12 to refactor the application's core logic and replace deprecated APIs. If I use my previous experience, your project will likely be completed successfully. Hope to discuss this in detail. Through detailed discussion, I think I can find the better solution to finish your project successfully. Thank you.

@copulas

Hello, I've checked your codebase basically from shared repository. You are alright, it was using QT3 API and need to upgrade for QT5.x I can upgrade with exact same ui and pass full unit test within 3 days. Looking forward we can discuss more detail in direct chat. Best Regards.

@jtolbert0175

Hi 12 requires updating the code from Qt3 while maintaining the original user interface and behavior. 12 equivalents, ensuring a clean and warning-free build. I've handled similar tasks before, like transitioning a complex Qt4 app to Qt5 for a tech company, where I realigned the UI without compromising functionality. I understand how critical it is to replicate the interface exactly, preserving the pixel-perfect layout you demand. Your focus on UI consistency shows attention to detail, which I respect greatly. I’m well-prepared to manage this port and ensure a seamless migration. Let's discuss your project requirements further, and I'll walk you through my approach. Thanks, Jonathan

@amadorjay

Hi there, The hard part is not just migrating the code, but ensuring the application’s interface remains identical to the original. Prioritizing the user-facing elements while refactoring the backend for Qt 5.12 presents a unique challenge. I plan to focus on replicating screens and menus pixel-for-pixel, while addressing deprecated classes behind the scenes without altering external functionality. Could you clarify if there are specific areas in the codebase that have been particularly problematic or require extra attention during the migration? Looking forward to discussing the details in chat.

@pristinedev

Hi, how are you! I can port the existing Flash4Linux Qt3/C++ codebase to Qt 5.12 while preserving the original UI, behavior, and command-line functionality. I’ll systematically replace deprecated Qt3 classes/APIs with Qt5 equivalents, resolve build issues and warnings, and carefully verify screens, menus, dialogs, sizing, and interactions against the original application. Any internal refactoring will be limited to what is necessary for compatibility, without changing the user-facing design or workflow. You’ll receive a clean Qt 5.12 project that builds from scratch on Linux and is ready for your regression testing. I’m experienced with C++, Qt, Linux, legacy codebases, debugging, and low-level software analysis, and I can start immediately. Best regards, Victor.

@shammij2

Hi 12 while preserving its original UI and behavior is an interesting challenge, and I'm eager to tackle it. 12, ensuring compatibility without altering user-facing features. I'll leverage Qt's extensive documentation and tools to refactor and replace outdated classes, focusing on maintaining the current pixel-perfect UI and vast functionality. With my background in C++ and Qt development, I've handled similar migrations and modernizations, such as a legacy application transition from Qt4 to Qt5, which resulted in a successful and clean upgrade. Appreciating your priority on keeping the interface unchanged, I’ll ensure a seamless port focusing on these requirements. 12 build, while respecting your original vision. I'm here to walk you through the proposed approach or dive into specific areas of interest. Thanks, Shammi