>  Whether it is the "best" is an exercise left up to the individual developer. 
>  Having a single software platform to share data with client and server has 
>  proven to me invaluable. That my servers run PHP and share data with my 
>  client software makes PHP-GTK a no-brainer. 

Err, you're missing the point here.  Windows + gtk and dependency dll 
hell + a million php installs is not a good combination.  Every php-gtk 
script installing their own version of php-gtk will add up (especially 
with many small scripts) and doesn't gain you a thing.  A single common 
way to install php-gtk (on windows or even unified locations/settings on 
  *nix) is an excellent thing.

I can tell you right now that gnope breaks any php installed using the 
"official" php msi installer.  Do we really need a dozen installers 
overwriting each other and putting conflicting ini files in bad places?

>  And the 10 or so MBs for the installer has *NEVER* shown up on the RADAR as in 
>  any way problematic. (For MacOSX, the installer effectively swallows some 400 
>  MB with X11, XCode, and the PHP-GTK binaries, and even that is deemed worth 
>  it by my clientelle) 

The issue isn't "is php-gtk worth it" it's "do we need yet another 
[windows] installer that does things its own way"

>  I guess the real question to answer is introspective - is your program 
>  actually worth $0.01 to your end users? 
>  
>  -Ben 
>  

-- 
PHP-GTK General Mailing List (http://gtk.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php