Legacy Code Migration: First Steps with the Designer
Ivanil Marcelino
Good morning! ☀️
📝 Note:
This video is intended for users who have never worked with the Designer before.
If you prefer, you can skip directly to the section that demonstrates the MyProject.init feature.
It’s a rather detailed video — maybe a bit long — but it thoroughly covers each step for better understanding.
🎬 About the video:
In this video, I demonstrate how to migrate the SuperChef project into the Designer, starting from installation, splitting the PRG form from one of the files, and finally compiling the project.
It’s a step-by-step tutorial that may help colleagues who have reached out with questions about how to handle this type of migration.
⚙️ Recommendations:
Before applying the process to your official project, I recommend following the exact model shown in the video.
Once you master this example, you’ll be fully capable of migrating any project safely and confidently.
📦 About the Designer:
The Designer does not create dependencies, unless you enable the Addons option.
When activated, Addons use internal mechanisms for:
-
Database handling
-
Automatic search system
-
Automatic export to Excel/HTML
These files can be provided free of charge upon request.
If you use the Wizard and select CRUD options, you’ll need to enable this dependency.
🔧 Compilation details:
The entire compilation kit remains available — nothing is deleted.
You can even run it manually, since all the necessary links are defined in the hbmk2 configuration files.
✨ New feature – MyProject.init:
The video also introduces the new MyProject.init feature,
where you can define your project’s public variables.
This allows the Designer to rebuild windows even when using external variables or functions,
though this requires a slightly more advanced understanding of the environment.
Wishing you a great weekend and happy coding! 👋
