I chose .phpw since it does not matter at all if a (w)indowed php app
uses tk, gtk or win32 api
to create a gui - .exe files also don't have .exec, .exed (delphi),
.exev (visual basic) and such.
Windows is not *nix. A php-gtk script is not an executable. Although
in linux you can simply toggle an executable file attribute and give it
a hashbang, windows has ONE WAY to show what to do with a file, the
extension. Comparing a scripting file extension to windows executable
extension is apples to oranges. You do have .js scripting files and
.wsh scripting files and .vb scripting files (unless you compile that
visual basic script to an .exe you better have a .vb extension on it).
The extension tells windows how to execute it. The problem is the way
windows registers file types - to get the "double click" magical
functionality windows needs to be told the proper action to take. If
you register .phpw with php-gtk and overwrite the windbinder
registration your computer will have problems if you use a script meant
for winbinder to run on the executable meant for gtk. - ask leon ;) It
would be like registering .zip or .tar - suddenly other programs don't
work because you took an extension another program uses. A file
extension on windows functions much the way a hashbang functions on
linux - windows just isn't as cool ;)
As of 2.8 wimp is enabled by default in Gtk+ on windows - I've added a
bunch of additional optional themes and theme engines and a theme
switcher as well, but I'm not sure how useful that will be to the
average user.
I can add an option to install PEAR (since I'm basically duplicating the
php installer functionality - why microsoft didn't make dependencies
easier is beyond me - and merge modules suck) and the demos - but
probably not in the typical clickthrough install. Multiple pear
installs can really do weird stuff on a computer. Any other opinions?