Re:Will there be a VCL Forms Designer In BCBX?
Rudy,
Your answer 3 is my answer 1.
I don't care whether it is part of a point release, a v2 release, an added free download, an additional optional purchase download, or what. I just want to know whether Borland has committed to and is working in a VCL forms designer for BCBX.
If the answer is Yes then I want to know approximately when this might come out.
It is possible they've decided No. It is possible they have not decided and are waiting to see how users react. I want to know the answer to this basic question. What has Borland decided at this point? Is BCB v6 the last C++/VCL forms designer we can expect from Borland? That is what I use BCB for. That is by far the main reason why I want to continue to use BCB and BCBX.
As for wxWindows or whatever it is called: hey, it might be nice. It might improve and become nice if it isn't nice now. But I don't really care at this point. I have apps written in BCB with VCL that are sold to customers and have many users that will continue to exist for many years and go thru many releases as C++/VCL apps. If BCBX gets a VCL forms designer then those apps will exist as C++/VCL apps for many more years than would be the case if Borland doesn't support a VCL designer.
To me this is a very important question. It is the only question I have about BCBX. Maybe Borland wants me to think about things about BCBX and other ways to use it. But I can't get beyond that question. I want an answer to it. If Borland supports VCL form designing in BCBX then I will definitely use it (unless it is just a terrible thing to use - but I assume they didn't{*word*222}it up). If they don't support VCL form designing then I can't say whether I will ever use BCBX. It becomes just a lot less compelling without a VCL forms designer.
If Borland doesn't want to answer this question now then why not? Why leave your customers{*word*154} about your commitment to VCL forms design support? My guess is that the vast bulk of your existing BCB users are doing VCL forms development and really don't want to have to migrate existing apps to a different UI API. That would take man-weeks or man-months or man-years of developer time and so why do it?
I find the whole discussion about BCBX tedious. I realize that BCBX might turn out to be a great thing for some kinds of C++ development. But I don't want to hear about it. I just want to know whether I'm looking at a major investment in time to move existing apps to a different API that might not even have functional equivalents for what existing VCL controls can do and that might be buggy or slower and that, generally speaking, would introduce new risks and new costs to continued development of existing apps.
So, Borland, please answer the question.
"Rudy Velthuis (TeamB)" <
XXXX@XXXXX.COM >wrote:
Quote
Randall Parker wrote:
>
>The question: Will there be a VCL Forms Designer In BCBX?
>
>The possible answers:
>
>1) Yes.
>
>2) No.
3) They are working on it for the next release?
--
Rudy Velthuis (TeamB)