Everything You Need To Know About Modernizing Delphi Apps
Delphi is a software product that uses the Delphi dialect of the Object Pascal programming language and provides an integrated development environment (IDE) for rapid application development of desktop, mobile, web, and console software, currently developed and maintained by Embarcadero Technologies. Delphi is known for its fast compilation speed, native code, and developer productivity. Borland originally developed Delphi as a rapid application development tool for Windows as the successor of Turbo Pascal. In this article, we will go over everything you need to know about modernizing Delphi apps and look at some of the most important points mentioned by senior Embarcadero members that you should keep in mind when modernizing UI Delphi apps with the Windows UI toolkit. How to upgrade Third-Party components? First of all, you should ask yourself which third-party libraries and components are you using with your legacy Delphi or C++ builder project? Having the source code for these components makes it easier because you can just take that existing source code, drop it into the current version of Delphi builder and rebuild it. Now you have a library that will work with the current Delphi/C++ builder that you want. Any third-party libraries or components that do not have this source code still need the upgraded version for the current Delphi / C++ build you are using. There is a good chance that some, if not all of your third-party libraries and components can be found on the GetIt Package Manager. You can search and install directly into the Delphi or C builder. This saves you a lot of time and effort trying to find a version of these third-party libraries of components compatible with the current version of Delphi. Should you update your app to use Unicode? A lot of people believe that updating their apps to Unicode is a lot harder than it is. You need to ask yourself if your application needs Unicode, or can it live as an English-only application? If your existing code only uses ‘single-byte’ (English standard alphanumeric characters and punctuation) and you do not need to support Unicode characters in your code, then you might be able to get away with avoiding Unicode altogether. It is a perfectly valid technique to use instead of string or Unicode string. There is a wonderful utility called the Unicode Statistics Tool, also known as The Parser Executable. It returns some objective measures on the likely complexity of your Unicode migration. The good news is that the compiler is smart enough to tell you where and if any Unicode changes need to occur. The Unicode migration has always been a lot easier than folks think it will be. The good thing is that after you go through the process of Unicode migration, your code will now allow you to now distribute that application to larger markets for supporting Unicode character and Unicode strings. It also makes upgrading between future versions of Delphi a lot easier. Do you have the latest database technology? You should seriously consider moving away from the BDE (Borland Database Engine). Yes, it was extremely popular for many years but it has also been LONG deprecated by Embarcadero and has not been actively upgraded for the last 15 years. The BDE cannot support Unicode and will never have 64-bit support. So […]
