Should WinBinder be developed in Qt?

Hello all, Manuel Lemos, of phpclasses.org fame, points out some important issues about the future of WinBinder that I'd like to share with you. He thinks that if WinBinder is meant to succeed it has to be a viable replacement for PHP-Gtk, and this includes of course being multiplatform. He points Qt as the best native multiplatform solution. Maybe he is right. IMO this approach has the following advantages: - Inherently multiplatform - Qt's API is much easier to work with than Windows' - API is fully tested and debugged, avoids tedious trial and error / testing - Much more stable And the disadvantages: - Object-oriented model may compromise non-OO PHP/WinBinder - Long learning curve for WinBinder core developers (i.e. me :) - Need C++, not C (I'm not the best C++ programmer around) - Can't compile with anything other than MS Visual Studio - Possible license restrictions for future shareware/commercial products (not sure) - Extra footprint of about 3.5 MB Of course the sooner the decision is made, the better. What do you think? Should I halt the development of WinBinder as it is now and delve deep into Qt? ------------------- Rubem Pechansky WinBinder - The native Windows binding for PHP http://winbinder.sourceforge.net/ winbinder-discussion@lists.sourceforge.net Hypervisual - Advanced Design for IT http://hypervisual.com/