Borland C++BuilderX and wxWidgets

letter | references | FAQ

Letter to the wxWidgets community


References


Borland and wxWidgets FAQ

How is wxWidgets supported in the September release of Borland C++BuilderX?
Only a technology preview of the designer tool is supported currently, to show how it will work in a future release. However, you may still use wxWidgets with the tools; we will be releasing a wxWidgets 2.5.1 development snapshot shortly which should work with most of the supported compilers on Windows, Linux and Solaris.

How is Borland helping the wxWidgets project?
Borland is providing funding for several aspects, including extended RTTI, the new build system, documentation and some reengineering tasks. They will support the QA process and their engineers will help solve specific bugs. Later, they may contribute significant new classes. Borland is also in a good position to encourage other companies to support wxWidgets and there will be many knock-on benefits of the association.

Is Borland 'taking over' wxWidgets?
Absolutely not. It couldn't, and it wouldn't wish to -- wxWidgets will remain open source forever. Borland is committed to the principle of an open source framework that has a long, long life, which cannot always be said of proprietary frameworks.

Why does Borland refer to the framework as 'wx'?
This is to avoid any naming controversy while the issue is being investigated. Meanwhile, our name is still wxWidgets!

Does Borland support Mac?
Of the desktop platforms, Borland is initially most interested in Windows, Linux and Solaris, but Mac support is likely to follow.

What about mobile platforms?
wxWidgets for Windows CE is quite far advanced (do join us in finishing it) and other mobile platforms are under consideration. However at present C++BuilderX is likely to focus on the use of wxWidgets for desktop application development.