I uploaded another bundle with the new Glib and Pango libs that Adrian mentioned. Hopefully this will show improved OpenType support. http://inkscape.modevia.com/win32libs/devlibs-2.12-080313.7z There was also a new Atk available.
and started using it for builds: http://inkscape.modevia.com/win32/Inkscape0803131626.7z
bob (ishmal)
Brilliant,
OpenType fonts work now. Now I can use Computer Modern fonts with all non latin characters as well (from http://www.gust.org.pl/projects/e-foundry/latin-modern)
Thanks :)
Rok
On Thu, Mar 13, 2008 at 6:04 PM, Bob Jamison <rwjj@...127...> wrote:
I uploaded another bundle with the new Glib and Pango libs that Adrian mentioned. Hopefully this will show improved OpenType support. http://inkscape.modevia.com/win32libs/devlibs-2.12-080313.7z There was also a new Atk available.
and started using it for builds: http://inkscape.modevia.com/win32/Inkscape0803131626.7z
bob (ishmal)
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 2008-March-14 , at 11:07 , Rock Star wrote:
Brilliant,
OpenType fonts work now. Now I can use Computer Modern fonts with all non latin characters as well (from http://www.gust.org.pl/projects/e-foundry/latin-modern)
With the OTF version of those I find that the LM Roman version has too large letter spacing in Inkscape (but works correctly in other programs). Do you see the same?
example: http://jo.irisson.free.fr/dropbox/Picture%203.png Inkscape is above, below is TextEdit on OS X (which looks more faithful to what LaTeX does)
JiHO --- http://jo.irisson.free.fr/
I checked few cases, but to me it the letter spacing seams ok.
Below are the examples (made of screenshosts which were manually scaled to fit the text heigh)
http://img181.imageshack.us/img181/9301/lmromanrm3.png
Rok
On Fri, Mar 14, 2008 at 11:34 AM, jiho <jo.irisson@...400...> wrote:
On 2008-March-14 , at 11:07 , Rock Star wrote:
Brilliant,
OpenType fonts work now. Now I can use Computer Modern fonts with all non latin characters as well (from
http://www.gust.org.pl/projects/e-foundry/latin-modern)
With the OTF version of those I find that the LM Roman version has too large letter spacing in Inkscape (but works correctly in other programs). Do you see the same?
example: http://jo.irisson.free.fr/dropbox/Picture%203.png Inkscape is above, below is TextEdit on OS X (which looks more faithful to what LaTeX does)
JiHO
Bob Jamison-2 wrote:
I uploaded another bundle with the new Glib and Pango libs that Adrian mentioned. Hopefully this will show improved OpenType support. http://inkscape.modevia.com/win32libs/devlibs-2.12-080313.7z bob (ishmal)
Thanks Bob for all your efforts on the Win32 libs,
I'm wondering if it might be possible for you to do a build of the GTK libs with the GTK patch for the win32 printing surface? (http://bugzilla.gnome.org/show_bug.cgi?id=488833)
In the bug report for "no printing from windows" (https://bugs.launchpad.net/inkscape/+bug/179988), the team have made a lot of progress (thanks to a number of people there!). We now have fairly functional printing, but with white blocks on the page.
There is a hack to fix the white blocks that involves partially bypassing GTK and directly using the cairo win32 printing surface calls. This seems to fix the white blocks, but it is a hack and not ideal. What it does show is that using the cairo win32 printing surface calls gives us a nice clean print.
Bob (or whoever is willing and able), it would be great if we could have a build of the GTK libs with this patch to try. Several people have indicated that they are unable for technical reasons (the build readme is very scary for mingw newbs like me). It would be really helpful if we could try this, especially given only a few days before the official announcement of 0.46.
If anyone is able to do a patched build and you are stuck for somewhere to put it, I suggest mediafire.com
Thanks in advance for any help. Rygle.
On Fri, Mar 21, 2008 at 07:03:53PM -0700, rygle wrote:
Bob Jamison-2 wrote:
I uploaded another bundle with the new Glib and Pango libs that Adrian mentioned. Hopefully this will show improved OpenType support. http://inkscape.modevia.com/win32libs/devlibs-2.12-080313.7z bob (ishmal)
Thanks Bob for all your efforts on the Win32 libs,
Btw, how are things sitting with the windows version of 0.46 these days? There are 3 days before our PR announce blitz, so I hope the windows issues are sufficiently squared away now?
Bryce
I'm wondering if it might be possible for you to do a build of the GTK libs with the GTK patch for the win32 printing surface? (http://bugzilla.gnome.org/show_bug.cgi?id=488833)
In the bug report for "no printing from windows" (https://bugs.launchpad.net/inkscape/+bug/179988), the team have made a lot of progress (thanks to a number of people there!). We now have fairly functional printing, but with white blocks on the page.
There is a hack to fix the white blocks that involves partially bypassing GTK and directly using the cairo win32 printing surface calls. This seems to fix the white blocks, but it is a hack and not ideal. What it does show is that using the cairo win32 printing surface calls gives us a nice clean print.
Bob (or whoever is willing and able), it would be great if we could have a build of the GTK libs with this patch to try. Several people have indicated that they are unable for technical reasons (the build readme is very scary for mingw newbs like me). It would be really helpful if we could try this, especially given only a few days before the official announcement of 0.46.
If anyone is able to do a patched build and you are stuck for somewhere to put it, I suggest mediafire.com
Thanks in advance for any help. Rygle.
View this message in context: http://www.nabble.com/Win32-libs-tp16033417p16213841.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Getting close, but not perfect. Several people are working on it.
There is the issue I mentioned here with white blocks on prints - test code that partly bypasses the GTK print dialog to use cairo win32 printing surface directly indicates a patched GTK build should fix the white blocks. Any help with GTK libs appreciated in particular.
Blur on print is also not perfect (comes out too big at times). No blank prints, but a problem with radial gradients can cause occasional crashes - have found a good test case to isolate this problem.
Rygle.
The bug 168896 https://bugs.launchpad.net/inkscape/0.46.x/+bug/168896 is fixed in trunk, but still undecided for inclusion in .46 // Albin
Btw, how are things sitting with the windows version of 0.46 these days? There are 3 days before our PR announce blitz, so I hope the windows issues are sufficiently squared away now?
Bryce
I believe bug #168896 is a duplicate of #204779, a bug which causes the "Report A Bug..." feature, and ALL the extensions to crash before executing. I'm just checking if this bug has been fixed - it needs to have been, because it's totally critical!
Joel
On Sat, 2008-03-22 at 08:38 +0100, Albin Sunnanbo wrote:
The bug 168896 is fixed in trunk, but still undecided for inclusion in .46 // Albin
Btw, how are things sitting with the windows version of 0.46 these days? There are 3 days before our PR announce blitz, so I hope the windows issues are sufficiently squared away now?
Bryce
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Joel Holdsworth schrieb:
I believe bug #168896 is a duplicate of #204779, a bug which causes the "Report A Bug..." feature, and ALL the extensions to crash before executing. I'm just checking if this bug has been fixed - it needs to have been, because it's totally critical!
Joel
The original bug was about not able to execute correctly python and locating the python libs. This is fixed in trunk. Now I face the magical "error 3" where the spawn crashes and closes Inkscape. This problem did not exists in the previous versions of the win32 libs (20080303). I am narrowing down the problem but this is no guaranty to find, isolate and deliver proper patch.
HTH,
Adib.
On Sat, 2008-03-22 at 08:38 +0100, Albin Sunnanbo wrote:
The bug 168896 is fixed in trunk, but still undecided for inclusion in .46 // Albin
Btw, how are things sitting with the windows version of 0.46 these days? There are 3 days before our PR announce blitz, so I hope the windows issues are sufficiently squared away now?
Bryce
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
I don't know about "Error 3", but at the moment, everything (including the manual) crashes from the line Glib::spawn_async_with_pipes throwing a Glib::SpawnError exception, which mysteriously is never caught by any catch statement. I even tried inserting a "catch(...)" at the bottom of the try block, and still it crashes.
I'm currently compiling with devlibs-2.12-080313.7z. I've written more details in notes in bug #204779. It seems to be an upstream bug - will updated win32 libs fix the problem.
On Sat, 2008-03-22 at 11:26 +0100, Adib taraben wrote:
Joel Holdsworth schrieb:
I believe bug #168896 is a duplicate of #204779, a bug which causes the "Report A Bug..." feature, and ALL the extensions to crash before executing. I'm just checking if this bug has been fixed - it needs to have been, because it's totally critical!
Joel
The original bug was about not able to execute correctly python and locating the python libs. This is fixed in trunk. Now I face the magical "error 3" where the spawn crashes and closes Inkscape. This problem did not exists in the previous versions of the win32 libs (20080303). I am narrowing down the problem but this is no guaranty to find, isolate and deliver proper patch.
HTH,
Adib.
On Sat, 2008-03-22 at 08:38 +0100, Albin Sunnanbo wrote:
The bug 168896 is fixed in trunk, but still undecided for inclusion in .46 // Albin
Btw, how are things sitting with the windows version of 0.46 these days? There are 3 days before our PR announce blitz, so I hope the windows issues are sufficiently squared away now?
Bryce
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of Joel Holdsworth Sent: zaterdag 22 maart 2008 12:01 To: Adib taraben Cc: inkscape Subject: Re: [Inkscape-devel] Win32 libs
I don't know about "Error 3", but at the moment, everything (including the manual) crashes from the line Glib::spawn_async_with_pipes throwing a Glib::SpawnError exception, which mysteriously is never caught by any catch statement. I even tried inserting a "catch(...)" at the bottom of the try block, and still it crashes.
It's at the moment not possible to throw exceptions across DLL boundaries in our Windows build. See https://bugs.launchpad.net/inkscape/+bug/173116. I hope a new build of the libs will remedy this (people write about building with "--shared-libgcc"), as it also crashes Inkscape when selecting an invalid jpg in the open dialog for example.
Regards, Johan
On Sat, 2008-03-22 at 12:49 +0100, J.B.C.Engelen@...1578... wrote:
-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of Joel Holdsworth Sent: zaterdag 22 maart 2008 12:01 To: Adib taraben Cc: inkscape Subject: Re: [Inkscape-devel] Win32 libs
I don't know about "Error 3", but at the moment, everything (including the manual) crashes from the line Glib::spawn_async_with_pipes throwing a Glib::SpawnError exception, which mysteriously is never caught by any catch statement. I even tried inserting a "catch(...)" at the bottom of the try block, and still it crashes.
It's at the moment not possible to throw exceptions across DLL boundaries in our Windows build. See https://bugs.launchpad.net/inkscape/+bug/173116. I hope a new build of the libs will remedy this (people write about building with "--shared-libgcc"), as it also crashes Inkscape when selecting an invalid jpg in the open dialog for example.
Regards, Johan
I agree a new build of the DLLs would probably solve these problems. Both Adib and I have found that spawning works just fine with devlibs-2.12-080303.7z but not with the current devlibs-2.12-080313.7z. Maybe you can figure out what changed between the two builds!
Joel Holdsworth schrieb:
On Sat, 2008-03-22 at 12:49 +0100, J.B.C.Engelen@...1578... wrote:
...
It's at the moment not possible to throw exceptions across DLL boundaries in our Windows build. See https://bugs.launchpad.net/inkscape/+bug/173116. I hope a new build of the libs will remedy this (people write about building with "--shared-libgcc"), as it also crashes Inkscape when selecting an invalid jpg in the open dialog for example.
Regards, Johan
I agree a new build of the DLLs would probably solve these problems. Both Adib and I have found that spawning works just fine with devlibs-2.12-080303.7z but not with the current devlibs-2.12-080313.7z. Maybe you can figure out what changed between the two builds!
Tor Lillqvist made some changes in the gspawn-win32.c. http://svn.gnome.org/viewvc/glib/tags/GLIB_2_16_0/glib/gspawn-win32.c?view=l... 20080313 uses glib-2.14.5 20080313 uses glib-2.16.1 But if that is the real answer... .
Not all users facing this issue. For ishmal everythink works as expected.
Adib.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
-----Original Message----- From: Adib taraben [mailto:theadib@...1439...] Sent: zaterdag 22 maart 2008 14:18 To: Joel Holdsworth Cc: Engelen, J.B.C. (Johan); inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Win32 libs
J.B.C.Engelen@...1578... wrote:
...
It's at the moment not possible to throw exceptions across
DLL boundaries in our Windows build. See https://bugs.launchpad.net/inkscape/+bug/173116.
I hope a new build of the libs will remedy this (people
write about building with "--shared-libgcc"), as it also crashes Inkscape when selecting an invalid jpg in the open dialog for example.
Not all users facing this issue. For ishmal everythink works as expected.
Are you sure? Ishmal, are you not experiencing this bug anymore? https://bugs.launchpad.net/inkscape/+bug/173116
Thanks for trying, Johan
On Sat, Mar 22, 2008 at 11:26:57AM +0100, Adib taraben wrote:
Joel Holdsworth schrieb:
I believe bug #168896 is a duplicate of #204779, a bug which causes the "Report A Bug..." feature, and ALL the extensions to crash before executing. I'm just checking if this bug has been fixed - it needs to have been, because it's totally critical!
Joel
The original bug was about not able to execute correctly python and locating the python libs. This is fixed in trunk. Now I face the magical "error 3" where the spawn crashes and closes Inkscape. This problem did not exists in the previous versions of the win32 libs (20080303). I am narrowing down the problem but this is no guaranty to find, isolate and deliver proper patch.
Has the proper patch been found? It's a bit ambiguous to me at the moment which of the several proposed patches involved with these bug reports ought to be pulled in for the release.
Bryce
Bryce Harrington-5 wrote:
Btw, how are things sitting with the windows version of 0.46 these days? There are 3 days before our PR announce blitz, so I hope the windows issues are sufficiently squared away now?
The printing bug in windows is 99% sorted, with only has some very minor stuff left, but it will have to wait for 0.46.1
I've nominated the patch on the last post here (https://bugs.launchpad.net/inkscape/+bug/179988) for release in the 0.46.x and main branches (don't know if main is necessary).
There are also two patched cairo libs to stop a crash when printing radial gradients. How do we get this included in the libs?
Is there anything else needed to get this into the 0.46 release? Never done this before.
On Sun, Mar 23, 2008 at 11:21 AM, rygle <pittos@...1208...> wrote:
Bryce Harrington-5 wrote:
Btw, how are things sitting with the windows version of 0.46 these days? There are 3 days before our PR announce blitz, so I hope the windows issues are sufficiently squared away now?
The printing bug in windows is 99% sorted, with only has some very minor stuff left, but it will have to wait for 0.46.1
What will be released in 0.46.0 then? The crash? Why?
Just to clarify, we haven't yet officially released 0.46.0. Windows-only patches for it are still accepted.
bulia byak wrote:
What will be released in 0.46.0 then? The crash? Why?
Here's the status with printing under Win32;
* All known crashes - FIXED Adrian Johnson has patched the Cairo libs to fix a problem with radial gradients in Cairo itself where radial gradients cause a crash - http://annarchy.freedesktop.org/~ajohnson/cairo/ - this will need to be fixed upstream, but for now we can use both these patched libs and there is no crash.
* Non-printing - FIXED
* Default page size problems - FIXED
* Print Scaling problems - FIXED
* White or black boxes over printing - FIXED - This is because GTK uses the wrong call in Cairo (create_win32_surface, not the create_win32_printing_surface). There is a patch to make GTK use create_win32_printing_surface, but we can partially bypass GTK and use the Cairo call directly. This gives exactly the same results as a patched GTK would give.
Remaining problems with Windows printing are;
* Some blurs are misaligned/mis-scaled. There are some test cases in the bug report, e.g.: https://bugs.launchpad.net/inkscape/+bug/179988/comments/107 The workaround is to print to bitmap (under rendering in the print dialogue)
If someone has the time to look into this before 0.46.0 release then good, but it wasn't actually in the scope of the original bug report and is not a show stopper. I am still happy to test or whatever. I have opened a separate bug for this - #205732
* The postscript back end drops back to bitmaps more readily than the PDF back end at present. Again the workaround is to print to bitmap.
Again, if someone has the time to look into this before 0.46.0 release then good, I am happy to test here too.
On Mon, Mar 24, 2008 at 6:00 AM, Diederik van Lierop <mail@...1689...> wrote:
Excellent work! Now I can continue promoting Inkscape to my colleagues :-)
Thank you all very much!
Diederik
rygle wrote:
bulia byak wrote:
What will be released in 0.46.0 then? The crash? Why?
Here's the status with printing under Win32;
- All known crashes - FIXED
Adrian Johnson has patched the Cairo libs to fix a problem with radial gradients in Cairo itself where radial gradients cause a crash -http://annarchy.freedesktop.org/~ajohnson/cairo/ - this will need to be fixed upstream, but for now we can use both these patched libs and there is no crash.
Non-printing - FIXED
Default page size problems - FIXED
Print Scaling problems - FIXED
White or black boxes over printing - FIXED - This is because GTK uses the
wrong call in Cairo (create_win32_surface, not the create_win32_printing_surface). There is a patch to make GTK use create_win32_printing_surface, but we can partially bypass GTK and use the Cairo call directly. This gives exactly the same results as a patched GTK would give.
Remaining problems with Windows printing are;
- Some blurs are misaligned/mis-scaled.
There are some test cases in the bug report, e.g.:https://bugs.launchpad.net/inkscape/+bug/179988/comments/107 The workaround is to print to bitmap (under rendering in the print dialogue)
If someone has the time to look into this before 0.46.0 release then good, but it wasn't actually in the scope of the original bug report and is not a show stopper. I am still happy to test or whatever. I have opened a separate bug for this - #205732
- The postscript back end drops back to bitmaps more readily than the PDF
back end at present. Again the workaround is to print to bitmap.
Again, if someone has the time to look into this before 0.46.0 release then good, I am happy to test here too.
Did we get to the bottom of the extensions issues?
A few minor improvements have been made to the Win32 printing patch, and it's as ready as I think it will get for 0.46 release. Can someone please commit it? https://bugs.launchpad.net/inkscape/+bug/179988/comments/139
Here's the latest information on printing under Win32;
* Non-printing - FIXED
* Default page size problems - FIXED
* Print Scaling problems - FIXED
* White or black boxes over printing - FIXED - GTK uses the wrong call in Cairo (create_win32_surface, not the create_win32_printing_surface). There is a patch in the GTK bug tracker to fix this, but in the meantime we have bypassed that part of GTK. The code will revert to GTK automatically when GTK itself fixes the problem.
* All known crashes - FIXED Adrian Johnson has patched the Cairo libs to fix a rare crash with radial gradients. - There are two patched libs here (needs both) - http://annarchy.freedesktop.org/~ajohnson/cairo/ - A patch has also been submitted to the Cairo git repository - http://gitweb.freedesktop.org/?p=cairo;a=commit;h=ae9635bf33cb989f5c525800b8... - If the cairo dlls for inkscape are built by patching 1.5.14 instead of building from git head Adrian recommends also getting the PostScript bug fix as well: http://gitweb.freedesktop.org/?p=cairo;a=commit;h=13e05bffd5cae5690fada24c7a...
Remaining problems with Windows printing are;
* Some blurs are misaligned/mis-scaled - see https://bugs.launchpad.net/inkscape/+bug/205732 The workaround is to print to bitmap (under rendering in the print dialogue)
* When printing falls back to bitmap, the bitmap is not always an ideal resolution. Again the workaround is to print to bitmap (Print -> Rendering -> Bitmap).
Great work all!
I think the remaining issues are minor; so definitely commit ready!
-johan
-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of rygle Sent: maandag 24 maart 2008 16:30 To: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Win32 libs
A few minor improvements have been made to the Win32 printing patch, and it's as ready as I think it will get for 0.46 release. Can someone please commit it? https://bugs.launchpad.net/inkscape/+bug/179988/comments/139
Here's the latest information on printing under Win32;
Non-printing - FIXED
Default page size problems - FIXED
Print Scaling problems - FIXED
White or black boxes over printing - FIXED - GTK uses the
wrong call in Cairo (create_win32_surface, not the create_win32_printing_surface). There is a patch in the GTK bug tracker to fix this, but in the meantime we have bypassed that part of GTK. The code will revert to GTK automatically when GTK itself fixes the problem.
- All known crashes - FIXED
Adrian Johnson has patched the Cairo libs to fix a rare crash with radial gradients.
- There are two patched libs here (needs both) -
http://annarchy.freedesktop.org/~ajohnson/cairo/
- A patch has also been submitted to the Cairo git repository -
http://gitweb.freedesktop.org/?p=cairo;a=commit;h=ae9635bf33cb
989f5c525800b82b81daad699e01
- If the cairo dlls for inkscape are built by patching 1.5.14
instead of building from git head Adrian recommends also getting the PostScript bug fix as well: http://gitweb.freedesktop.org/?p=cairo;a=commit;h=13e05bffd5ca
e5690fada24c7a7e2457c39e4dbf
Remaining problems with Windows printing are;
- Some blurs are misaligned/mis-scaled - see
https://bugs.launchpad.net/inkscape/+bug/205732 The workaround is to print to bitmap (under rendering in the print dialogue)
- When printing falls back to bitmap, the bitmap is not
always an ideal resolution. Again the workaround is to print to bitmap (Print -> Rendering -> Bitmap).
-- View this message in context: http://www.nabble.com/Win32-libs-tp16033417p16254450.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
bulia byak wrote:
Just to clarify, we haven't yet officially released 0.46.0. Windows-only patches for it are still accepted.
I am new to this and unsure how long it takes to get patches in. The deadline is meant to be March 24 for the PR blitz isn't it? That's today.
As far as I know, no-one has committed the patches already there in https://bugs.launchpad.net/inkscape/+bug/179988. Can someone please commit what has been done so far?
We also need to include the patched cairo libraries from Adrian Johnson to prevent a showstopper crash. Can these be added to the win32 libs?
If you think there is time to fix the blur bug, then please look at https://bugs.launchpad.net/inkscape/+bug/205732 I am happy to keep working on this to get blurs fixed for 0.46.0 if you think it's still possible.
Thanks, Rygle.
Sorry to be a pain on this (I'm a commit newb! :blush:), but here's the latest wisdom from Adrian Johnson on the printing bug. He suggests there are a few things still to be tidied up before this can be committed to the 0.46 branch.
======== - I'll push out my cairo patch to the cairo repository in the next few hours. Then Ishmal can do a cairo build from that. As the current cairo snapshot (1.5.14) is the release candidate for 1.6.0 I need to do further testing to make sure I have not broken anything before I push out this patch.
- The workaround for using win32_printing_surface with gtkprint should be made more robust. It should be changed to check of the surface returned by gtkprint is of type CAIRO_SURFACE_TYPE_WIN32 before substituting it with win32_printing_surface. That way the code will work correctly if gtkprint returns some other surface like pdf. It will also ensure that when gtkprint is fixed to use the surface of type CAIRO_SURFACE_TYPE_WIN32_PRINTING, the workaround will be bypassed.
(suggested code omitted) ========
So we are very close, but please don't commit everything just yet.
On Sun, Mar 23, 2008 at 08:21:11AM -0700, rygle wrote:
Bryce Harrington-5 wrote:
Btw, how are things sitting with the windows version of 0.46 these days? There are 3 days before our PR announce blitz, so I hope the windows issues are sufficiently squared away now?
The printing bug in windows is 99% sorted, with only has some very minor stuff left, but it will have to wait for 0.46.1
I've nominated the patch on the last post here (https://bugs.launchpad.net/inkscape/+bug/179988) for release in the 0.46.x and main branches (don't know if main is necessary).
There are also two patched cairo libs to stop a crash when printing radial gradients. How do we get this included in the libs?
Talk with ishmal about these - he's the official packaging guy for Windows so is the one that takes care of this.
Is there anything else needed to get this into the 0.46 release? Never done this before.
Thanks, you've done exactly what's needed; I'll take it from here.
Fwiw, in the future I think the Windows patch coordination outside the normal release should be handled by the Windows packaging team, but I can do it this time through.
Bryce
Bryce Harrington-5 wrote:
Talk with ishmal about these - he's the official packaging guy for Windows so is the one that takes care of this.
Thanks for your help Bryce. Still looking at the fontfactory.h thing - I think it's an #ifdef win32 problem, but because I'm not a programmer I need some help.
About the packaging - I've tried emailing Ishmal several times to ask him about libs, both through the facility on Launchpad and via the email address used on this list, and I got no reply at all. I've tried raising the GTK stuff several times in the email lists, and again no reply.
I tried emailing another dev for clarification about the GTK thing, and got told that I should *never* email devs because they don't answer and it's considered rude. He said "keep public conversations public". But then I see others quoting from email conversations with other devs.
I've found this quite frustrating. There needs to be better communication than this, or some protocol or wiki page to help people know how to ask for advice. Even if a dev is too busy, perhaps they could just say that.
I know I had a rant a while back, and I said some things that were not at all justified, and for that I publicly apologise. I have learned to think more before emailing, but I hope that hasn't led to people not replying.
On Mon, Mar 24, 2008 at 05:42:10PM -0700, rygle wrote:
Bryce Harrington-5 wrote:
Talk with ishmal about these - he's the official packaging guy for Windows so is the one that takes care of this.
Thanks for your help Bryce. Still looking at the fontfactory.h thing - I think it's an #ifdef win32 problem, but because I'm not a programmer I need some help.
Okay, good luck. Thanks for working on the windows printing bug, it's a key one for getting the windows release out, and if your patch fixes it, it will earn much appreciation.
About the packaging - I've tried emailing Ishmal several times to ask him about libs, both through the facility on Launchpad and via the email address used on this list, and I got no reply at all. I've tried raising the GTK stuff several times in the email lists, and again no reply.
Be patient; he's probably just busy. He often does not reply to my emails either. If you can catch him on irc, that seems to work best.
I tried emailing another dev for clarification about the GTK thing, and got told that I should *never* email devs because they don't answer and it's considered rude. He said "keep public conversations public". But then I see others quoting from email conversations with other devs.
I don't know if that's necessarily a rule (I get such emails often), but it's a good point to keep public discussions public. Generally, a single email to the inkscape-devel list should be sufficient, with a follow up if you got no response after a few days.
I've found this quite frustrating. There needs to be better communication than this, or some protocol or wiki page to help people know how to ask for advice. Even if a dev is too busy, perhaps they could just say that.
Many developers will file their inkscape emails off to a separate folder from their regular day-to-day email, and only check it when they have time to devote to inkscape. Others only spot-check email. So esp. when you're new, you might find it hard to get quick responses. In general, just be patient, give some days for them to reply, and follow up if it's important after a few days.
Or if it's an important issue, ask on IRC since that sometimes can get a quicker response. A couple notes on IRC. First, never ask, "joe, can I ask a question?" or "joe, are you there?" It's better to just ask your question straight off. Second, don't expect an immediate answer; often people stay logged into IRC but wander off from the computer for some time (meetings, TV, dinner, sleep, whatever) and check the backlog when they return. So ask your question and just stick around on the channel a while; make sure to mention the person's nick that you want to answer the question so it'll highlight in their backlog; and then wait some hours (maybe up to 10 hrs) for a response. You can also privmsg people you know well - again, some people consider it rude to privmsg people you don't know out of the blue, but it varies; asking on the public channel is best, unless the topic is somehow sensitive or personal.
I know I had a rant a while back, and I said some things that were not at all justified, and for that I publicly apologise. I have learned to think more before emailing, but I hope that hasn't led to people not replying.
Thanks, we do try to maintain civil discourse, so this is appreciated. I suspect the non-reply is due to people either being busy or not knowing the answer, nothing personal.
Bryce
Actually, Rygle is right about this. He's been carrying the water for the last few weeks, and I've been unreachable. I'm sorry.
However, it's been good that someone else besides me has been pushing iron for Inkscape in the win32 world. I welcome Rygle to this stuff. :-)
This is similar to 2004, when Inkscape/win32 would have died without Simarilius (john cliff) coming to the rescue. It's too important to be relegated to such a jackass as me. Just like a football team, we need depth.
bob
I have learned a lot about team work in weeks since my flame. I have had lots of people helping me, especially Ulf and Adrian on the print bugs (well really me occasionally helping them), and I know several others have been putting in some hard yards elsewhere. I've just been the patch and test boy mainly, but glad that a Windows person can make a contribution. I can feel some wiki pages for Windows newbs coming out of this experience. :-D
Anyway, hopefully it will pay off as we push out this windows version.
Although I've been mostly out of this, I must say I was astounded by the level of activity on windows bugs. Initially I wan't sure the "fix bugs until 24th" ultimatum would work, but apparently it did. It's unprecedented in Inkscape history - looks like we've reached a new level of userbase dedication :)
participants (12)
-
unknown＠example.com -
Adib taraben -
Albin Sunnanbo -
Bob Jamison -
Bryce Harrington -
bulia byak -
Diederik van Lierop -
jiho -
Joel Holdsworth -
john cliff -
Rock Star -
rygle