Couldn't this be done as an extension/plugin for OO? It would seem that would be more reasonable than a fork. That is exactly what it is. Don't believe the "fork" FUD.
Well, in that case it's a bug in the ms-windows theme engine, and you should open a bug report on bugzilla.gnome.org. The wimp developer is quite responsive. As far as I know, the ms-windows theme engine tries to follow the XP theme's settings as closely as possible. But then, I am no theme freak myself (heck, I have middle gret as my desktop colour;), and I don't know how well it can do that if you use some really outlandish XP theme...
Actually it's you that reinforce the prototype of Slashdot commenters;)
If you would have investigate more thoroughly what's happening, you would have noticed that the guy who released this installer and the wrapper executable (which apparently some people mistake for an X server, huh, how clueless can one be?), and posted to Slashdot, had nothing to do with the actual porting work that went on mostly during last year (by me). Announcing his installer on Slashdot was a bit premature in my opinion.
And yes, I do consider myself a pretty experienced Windows developer, although my experience is with porting software from Unix (GLib, GTK+, GIMP, Pango, GNOME platform libraries), not with writing code against Microsoft's proprietary toolkits.
There are certainly no hardcoded paths in the actual Evolution and GNOME library code. That is one of the first things to take care of in porting software from Unix to Windows, removing all uses of configure-time hardcoded paths. Like GLib, GTK, Pango etc, all the GNOME libraries and Evolution that have been ported to Windows look up their installation folder at run-time, and construct the pathnames to files they open at run-time (like plug-ins, icons, etc) based on that. They can be installed anywhere, even in folders with totally random Unicode characters. (A couple of non-ASCII -related bugs have been fixed only recently and aren't yet in the binaries available on ftp.gnome.org, only in CVS).
This wrapper the installer the parent article is about is another thing. I don't know anything about what assumptions it does.
--tml (the guy who did the Evolution port to Windows)
The ms-windows ("wimp") theme engine certainly does *not* use "native" widgets. That would be quite impossible for a GTK+ theme engine. It just draws the normal GTK widgets in a way that makes them look more like "native" widgets.
Slashdot Mirror
There are known bugs related to time formatting. See for instance http://bugzilla.gnome.org/show_bug.cgi?id=343686 and http://bugzilla.gnome.org/show_bug.cgi?id=336253.
> The open source world CAN do so much better than this...
And your contribution is...?
Well, in that case it's a bug in the ms-windows theme engine, and you should open a bug report on bugzilla.gnome.org. The wimp developer is quite responsive. As far as I know, the ms-windows theme engine tries to follow the XP theme's settings as closely as possible. But then, I am no theme freak myself (heck, I have middle gret as my desktop colour;), and I don't know how well it can do that if you use some really outlandish XP theme...
Actually it's you that reinforce the prototype of Slashdot commenters ;)
If you would have investigate more thoroughly what's happening, you would have noticed that the guy who released this installer and the wrapper executable (which apparently some people mistake for an X server, huh, how clueless can one be?), and posted to Slashdot, had nothing to do with the actual porting work that went on mostly during last year (by me). Announcing his installer on Slashdot was a bit premature in my opinion.
And yes, I do consider myself a pretty experienced Windows developer, although my experience is with porting software from Unix (GLib, GTK+, GIMP, Pango, GNOME platform libraries), not with writing code against Microsoft's proprietary toolkits.
--tml
X server? What drugs are you taking?
There are certainly no hardcoded paths in the actual Evolution and GNOME library code. That is one of the first things to take care of in porting software from Unix to Windows, removing all uses of configure-time hardcoded paths. Like GLib, GTK, Pango etc, all the GNOME libraries and Evolution that have been ported to Windows look up their installation folder at run-time, and construct the pathnames to files they open at run-time (like plug-ins, icons, etc) based on that. They can be installed anywhere, even in folders with totally random Unicode characters. (A couple of non-ASCII -related bugs have been fixed only recently and aren't yet in the binaries available on ftp.gnome.org, only in CVS).
This wrapper the installer the parent article is about is another thing. I don't know anything about what assumptions it does.
--tml (the guy who did the Evolution port to Windows)
The ms-windows ("wimp") theme engine certainly does *not* use "native" widgets. That would be quite impossible for a GTK+ theme engine. It just draws the normal GTK widgets in a way that makes them look more like "native" widgets.
But it does. Just install them in different places, and set PATH to point to the "bin" folder of the version you want to use.
Whether installers allow it or not is another thing, but that's their problem. I don't do installers.