>  I'm not a Windows person, but I think we (as in the PHP-GTK  developers) 
>  ought to agree upon *one standard location* for PHP-GTK  to reside in.

Hallelujah. Both on the internet and on the client :)

That may not be practically possible, as users may want
>  to install PHP-GTK in customized locations, but the problem can be  solved 
>  by creating a registry key upon installation which stores the  location of 
>  the installed PHP-GTK binaries. After this, we could  release a tiny 
>  helper-app that developers using PHP-GTK could use to  build their 
>  installers. All that installer would really contain is  the source code of 
>  the program itself and some code to retrieve the  registry entry and set 
>  the PATHs correctly.
> 
>  Any developers using PHP-GTK who choose not to use our helper-app to 
>  release (windows versions) of their software lose out on the  convenience.
> 
>  How feasible is this?

It'll need looking into. Unless Elizabeth knows off-hand of course.

Cygwin installations work on dependencies and download whatever's necessary 
(including upgrades) to complete a lib install. Maybe we could work towards 
something similar, but we'd need a registry entry to do it because of the 
potential path issue - and we obviously can't use the existing PHP registry 
entry.

- Steph

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

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