Should an application using the VCL be migrated?
Is the VCL dead or does it have a future as a GUI library? How did CLX end up, is there a chance for cross-platform support in future releases?
I had to work with a legacy application that uses Borland VCL (BCB6). Now that new features are to be implemented, the alternatives need to be re-evaluated. Whether sticking to VCL or migrating to another library / framework.
I have never read what's going on in the Embarcadero area (Borland). At least there are only a few VCL related questions here in SO and not too much luck with Google.
a source to share
Whether you should continue to use VCL in your project or switch to an alternative depends on your requirements. The VCL framework is powerful and mature, with many third party components making it a good idea. The alternatives were rapidly improving and indicated that the final choice really requires you to carefully consider your requirements and check the strengths and weaknesses of the various frameworks.
Given that cross platform is on the roadmap, I remind you that 64 bit support has been quite a long time. We may see cross platform support, perhaps on schedule, perhaps protracted, as we've seen with many previous features. I want to believe that it will come because I really like the VCL framework, but I always have a natural doubt about the official roadmap of the RAD studio series - sorry David.;)
If you have explored various alternatives and found that VCL is the best choice based on its relevance to your project, then I would consider using the VCL framework, especially if it is an environment that you are familiar with. Learning a new structure can, although it is often a good idea, is time consuming work. Therefore, even if there is a risk that the structure will not be preserved (as with any alternatives), you can save a lot of work by staying in the familiar structure if it is more appropriate for your project.
If you decide to go with C ++ Builder and VCL, you may find that the C ++ Builder log is a valuable source of information, they have a relatively decent forum but with some interesting posts in it, as well as some free tips their website : www.bcbjournal.com .
Of course, there are also embarcadero forums, and it might be a good idea to search the Delphi forums and categories on this site as they seem to have more active users and a lot more posts. One good thing, however, is that converting from Delphi to C ++ in VCL-related questions is pretty straightforward.
a source to share
The VCL continues to evolve. The cross platform is on the current roadmap . the embarcadero forums are still a valuable resource.
a source to share
As a VCL user, I must say that your observations are indeed correct. You may like the VCL, but the resources available compared to QT and other tools are bad, at least esp. in SO. Our team also found several bugs in their components and fixed the components more than once to make our application stable. However, for me, the main reason for the migration is that the VCL locks you with one set of development tools. I have to admit that I'm having a hard time finding any really compelling reasons to keep using it if you have the resources to migrate.
Considering that bcc32 and its libraries are also very cumbersome, lockin gets even more serious. In recent months, my team and I have spent more time troubleshooting compiler-induced problems than actually developing functions. For me, this is such a major obstacle that its excess cost of its benefits is tenfold. Unfortunately, the costs of migration are so great for us that we, at least for now, have to endure our pains.
a source to share