Re: Should WinBinder be developed in Qt?

Yes, it does run natively, but I think Wez was talking about the look and feel - what makes the difference between win32 app and GTK app. Here are some screenshot of SIM ICQ, which is multiplatform and uses Qt for the user interface (windows screenshots, google is good friend to find linux ones too): http://www.icqinfo.ru/soft_sim.shtml Andrey Rubem Pechansky wrote:

WinBinders biggest attraction to me is that it provides a PHP interface to the native windows components.

- The reason that WinBinder is attractive is because it does native win32

I believed that Qt also did Windows natively. Their web site claims "Qt applications run natively, compiled from the same source code, on all supported platforms". Doesn't it? ------------------- 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/ ----- Original Message ----- From: "Wez Furlong" <kingwez@gmail.com> To: "Rubem Pechansky" <pechansky@hypervisual.com> Cc: <pecl-dev@lists.php.net> Sent: Tuesday, October 19, 2004 7:51 PM Subject: Re: [PECL-DEV] Should WinBinder be developed in Qt?

IMO, don't go near Qt. Two reasons: - The reason that WinBinder is attractive is because it does native win32 - Qt has crappy license implications If you're going to use a toolkit, go for wxWidgets. --Wez. On Tue, 19 Oct 2004 18:52:34 -0300, Rubem Pechansky <pechansky@hypervisual.com> wrote:

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/ -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

-- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php