So every single program is going to install its own PHP, and GTK? 11MB for every PHP-GTK 
application, when the code itself weights probably 3KB. Granted there are advantages to self
 
contained systems (like updates not breaking a program) but there are just as many disadvant
ages 
(like updating every single program one by one, and 11MB download per 'script'). I know hard
 drives 
are measured in gigabytes and sometimes terrabytes... but meh. Australians will cry about th
eir use 
of bandwidth, and dialup users will cry about spending an hour, all for a simple app.

 From a Linux users perspective not being shared is an annoying thing, though Elizabeth I kn
ow 
prefers this relocatabopityboo trickery. Does this also do anything about registering file 
extensions with Windows so that phpw/phpg can be double clicked? Probably not that would be 
more the 
job for a shared library installer I guess.

I am not a all negative person, I could see this being useful for selling apps to real clien
ts for 
installation. Do all the licenses involved (including any code you wrote for this) allow for
 that?

I would probably suggest fixing spelling errors and general English structure (punctuation, 
capitalization) on the page, too.

- bob.

Mr. Dreadsoft wrote:
>  First of all, I would like to give thanks to Elizabeth Smith  
>  (http://www.perisama.net) and kksou 
>  (http://www.kksou.com/php-gtk2/index.php). Without their work, my small 
>  contribution would not be possible.
>  
>  I've just realized a small "environment" to create standalone 
>  self-installing php apps. You'll be able to create an installer for your 
>  application, and, once installed, your app won't need any extra 
>  file/programs (e.g. gnope).
>  
>  For more information, see
>  
>  http://www.dreadsoft.org/php-gtk/readme.html
>  
>  please let me know if you notice some problems.
>  
>  Marco
>  

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