RE: [Inkscape-devel] Win32 builds
Now that the files have been checked into the tree, it has become very easy to build on Win32. I have put a couple of recent builds here:
The latest one works perfect on Windows 98. Thanks a lot!
The only minor issue is that the size of all fonts in the UI is larger than that of native Windows apps - likely a GTK issue though. GTK even translated some (far from all) labels in the interface into Russian, because my Windows is Russian-localized :)
Now maybe you can have a look at some lingering issues with the win build: paths of files and preferences (search the source for "TODO:WIN32") and the transient dialogs (I had to switch transiency off for windows, because there was a weird problem: when you minimize a document window, it minimizes with its transient dialog, but when you restore them, only the dialog pops up, and you cannot access the document window unless you close the dialog. See src/dialogs/dialog-events.cpp for code and some comments.)
Oh, and detached toolbars also sink on Windows, as they do on KDE - and they cannot be restored unless you minimize all windows, because the toolbar "window" has no button in the taskbar :(
Anyway, great job and a nice Xmas present for Windows users :)
_________________________________________________________________ Make your home warm and cozy this winter with tips from MSN House & Home. http://special.msn.com/home/warmhome.armx
bulia byak wrote:
The only minor issue is that the size of all fonts in the UI is larger than that of native Windows apps - likely a GTK issue though. GTK even translated some (far from all) labels in the interface into Russian, because my Windows is Russian-localized :)
I would bet that this is Pango at work. Again, since GTK2 is dependent on Pango, we might as well use its services. On Windows, we must include the Pango DLL, or Windows will not run GTK2. So use it! ;-)
This goes along with what I said earlier, and is related to using Java on Netscape. If the customer does not have the library already, and we have a dependency on it, it is -OUR- responsibility to provide it. NOT THEIRS. Java on NS died because of the "download factor". Asking a user to download more stuff, else your software will not work, is a killer.
Po-russkij, our software must be samostoyatel'nij. It must survive in a harsh environment on its own. My idea is that when we consider libraries like Cairo, Javascript, LibWWW, etc., we must first investigate their portability, and if they are portable, then a part of our source tree should have snapshots of them in it, that we know are guaranteed to run. That is how Mozilla does it.
Just IHMO, poor humble opinion.
Anyway, thanks for testing it, and Merry Christmas to all.
Bob (ishmal)
On Wed, 2003-12-24 at 22:04, Bob Jamison wrote:
Po-russkij, our software must be samostoyatel'nij. It must survive in a harsh environment on its own. My idea is that when we consider libraries like Cairo, Javascript, LibWWW, etc., we must first investigate their portability, and if they are portable, then a part of our source tree should have snapshots of them in it, that we know are guaranteed to run. That is how Mozilla does it.
Very firmly agreed.
-mental
participants (3)
-
Bob Jamison -
bulia byak -
MenTaLguY