May 2014 - Inkscape Devel - Inkscape Mailman

Inkscape doesn't apply a changed display profile
by Tobias Ellinghaus 17 May '14

17 May '14

Hello, after annoying su_v with this for a while in IRC I'm taking this to the list now and hope that someone here can have a look -- otherwise I will try to file it in launchpad. The bug (?) I see is that Inkscape fails to apply a changed display color profile. More precisely, when I tick "Retrieve profile from display" in the settings Inkscape correctly gets whatever I set in the X atom. When I change the assigned profile while Inkscape is running it doesn't change the used profile though. After digging into the code a bit I found that src/ege-color-prof-tracker.cpp correctly notices that the profile was changed in handle_property_change(), it manages to extract the correct data and calls set_profile(). Afterwards fire() is called and the innermost if() is also reached, resulting in the g_signal_emit() being executed. This looks all fine and dandy. However, there is no further reaction I could see. I didn't try to understand what signal exactly was emitted there and what pieces of code connected to that, so I can't tell if the signal isn't caught by anyone, or if the subsequent code is buggy. All I could notice is that the newly found profile is not used. The easiest way to test this is using a regular sRGB profile and one of those profiles that swap color channels (BRG.icc or the like). I would expect that changing the display profile makes a noticeable difference then. I hope that it's just a small fix and that it can be taken care of for the upcoming release. Thanks for your attention, and thanks for Inkscape. Tobias

1 0

Re: [Inkscape-devel] Rejuvenated build system for Mac OS X
by su_v 16 May '14

16 May '14

On 2014-05-06 11:49 +0100, Partha Bagchi wrote: > Yes, my builds open PDF files and I saw this Debian bug report where > someone claimed that Inkscape uses gs instead of pstoedit: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=366797 That bug report was originally filed against older versions of inkscape (0.43-0.46). With the release of Inkscape 0.47 on 2009-11-24, PS/EPS import was switched from pstoedit to ps2pdf (from Ghostscript): <http://wiki.inkscape.org/wiki/index.php/Release_notes/0.47#PostScript_and_E…> <http://tavmjong.free.fr/INKSCAPE/MANUAL/html/File-Import.html> pstoedit [1] (used in older Inkscape versions for PS/EPS import) is a different application than ps2pdf [2] (used by current Inkscape stable and trunk [3]). 'ps2pdf' is part of Ghostscript i.e. it is one of the many separate command line tools installed by Ghostscript. [1] pstoedit: <http://www.pstoedit.net/> [2] ps2pdf (Ghostscript): <http://www.ghostscript.com/> <http://www.ghostscript.com/doc/9.10/Ps2pdf.htm> [3] (e)ps_input: <http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/e…> <http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/e…> <http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/e…> > On Mon, May 5, 2014 at 10:01 PM, su_v <suv-sf@...58...> wrote: > >> On 2014-05-06 03:38 +0100, Partha Bagchi wrote: >>> On Mon, May 5, 2014 at 8:40 PM, su_v <suv-sf@...58...> >> wrote: >> >>>>> and I was not able to open EPS files (got a parsing error with >>>>> "expecting "<" ...). >>>> >>>> Since you don't share details about how your app was created (I assume >>>> you used custom packaging routines, too, besides your own build env for >>>> the dependencies), I can only guess what the underlying issue might be: >>>> >>>> I build all gtk/glib dependencies from scratch, everything I need for >> Gimp >>> (you can check out my Gimp builds on my website). >>> >>> I downloaded your branch and built the Inkscape App using the same >>> structure as my Gimp builds. The Inkscape App like my Gimp builds is self >>> contained and does not rely on the User for any dylibs. >>> >>>> 1) Is your Inkscape.app (Inkscape-0.48-dev) able to open PDF files? >>>> (these kind of parser errors are known from contexts where PDF >>>> support in Inkscape is broken - e.g. because poppler was configured >>>> without xpdf headers, or not built in at all). >>>> >>> See above. My builds have poppler configured with xpdf headers and >>> associated dependencies included. My Gimp builds open PDF/EPS/PS just >> fine. >>> :) I'll be happy to share my Inkscape build with you (or anyone) if >> needed. >> >> So your Inkscape.app build does open PDF files or not? Please note that >> GIMP's PostScript import feature is different from Inkscape. >> >>>> (If poppler support was not properly compiled in, >>>> 'org.inkscape.input.pdf' might be a logged missing dependency for input >>>> formats like PS and EPS (see 'extension-errors.log' in the inkscape user >>>> profile dir used by Inkscape.app - the exact location depends on whether >>>> you used the launcher script of the 'osxmenu' branch, or your own)). >>>> >>>> 2) Did you verify that the bundled ps2pdf and GhostScript (I assume you >>>> included it in the app bundle, since it is a required helper app for >>>> PostScript input in Inkscape) works as expected? >>>> >>> I was going to build ps2pdf till I saw the bugreport where you said that >>> one does not need it anymore. Gimp does not need ps2pdf to open EPS files >>> (or Ghostscript for that matter). Just the dylib. I'll build ps2pdf and >>> recheck this. >> >> Which bug report for inkscape - do you have a link? I can't imagine that >> I said that Inkscape no longer needs ps2pdf for EPS/PS import (it still >> does). >> >> In Inkscape, PS/EPS import works in two steps: >> 1) the PostScript file is converted to a PDF file with ps2pdf from >> Ghostscript (needs to be in $PATH). >> 2) the just created PDF file is imported in Inkscape using built-in >> (poppler-based) routines. >>

2 1

Windows devs: IMPORTANT, buildtool improvement
by Johan Engelen 15 May '14

15 May '14

Hi all, If you bzr up, you have to rebuild buildtool. I added a cxxflags attribute, so we no longer get warnings about C++ flags that are not applicable to C compilation. This is cmd you need: g++ buildtool.cpp -o btool.exe -O3 -fopenmp regards, Johan

1 0

Careful with merging!
by Johan Engelen 15 May '14

15 May '14

Hi all, Look here: http://bazaar.launchpad.net/~inkscape.dev/inkscape/experimental/changes rev 13365 <http://bazaar.launchpad.net/%7Einkscape.dev/inkscape/experimental/revision/…> managed to 'rename' my earlier commit to include poppler in win64 build. My recommendation to not waste too many brain cycles: don't merge. You can create you own branch, fine, just don't merge it in. Just create a separate trunk/experimental checkout and copy your changes in, then commit. Whatever you think about better workflows, it is paramount to maintain a clean version history. And again and again, we have proven that we are not capable of maintaining a clean history by using bzr merge. Thanks, Johan

4 5

[win32] really long initial startup times on Windows 7/8
by Liam White 15 May '14

15 May '14

This one almost certainly has to be fixed before we release. To be quite honest, I am unsure of the cause. I did test this out on Windows XP and it worked perfectly well. I compiled on a Windows 8.1 x64 machine, and launched it on a Windows 7 machine. The console window appeared, as normal, but I wondered why it didn't go away. Interested, I launched it with not gdb, as would be recommended, but instead with Visual Studio (as it would have symbols for all of the Windows libraries). The long startup didn't cause any sort of trap, but the preferences.xml I had did. (the trap seems to happen when you launch with default prefs, iconify the Fill and Stroke dialog, close it normally, and restart it with gdb: https://bugs.launchpad.net/inkscape/+bug/1317700) After I had stepped through every single one of the several hundred breakpoints, I could not find the issue (although mainly because the Microsoft devs refuse on releasing the details to their PDB format, and do not seem to support DWARF debug symbols in their debuggers). I am unable to reproduce the exceptionally long startup time issue, as it went away immediately after the first startup. Possibly a registry key was set. However, the traps are a persistent issue and make my loading time about five seconds longer. What I am envisioning right now is thousands of people downloading the update, launching Inkscape, and not seeing anything at all (compiled with -mwindows), despite the process showing in Task Manager and consuming many resources. We have also had at least one complaint about this before. (If I could put a bounty on this bug, I would!) What is this madness?

5 6

Setting up sub-projects for Inkscape
by Bryce Harrington 14 May '14

14 May '14

The question has come up a couple times now, so figured a definitive official answer might help, while the steps are still fresh on my mind. tldr: Contact one of the admins for help (see https://launchpad.net/~inkscape.admin/+members) Anyone can set up an independent project in Launchpad, unassociated with Inkscape. Anyone can also create their own Inkscape branch, unofficially associated with Inkscape, ala lp:~bryce/inkscape/my-stuff. But what about making separate projects that are *associated* with inkscape? And what about making official branches associated with inkscape that other devs can contribute to? Official Team Branches ====================== If you're a member of the inkscape-dev team, you can also upload official branches by doing: bzr push lp:~inkscape.dev/inkscape/branch-name A full list of all branches associated with Inkscape can be seen here: https://code.launchpad.net/inkscape (Please delete branches when you no longer need them, to cut down on clutter!) Setting up Sub-Projects ======================= But what if you want a distinct project from inkscape, but want to enable your fellow inkscape developers to work on it? To enable others in inkscape.dev to commit, first you upload the branch as you would an official inkscape branch. I.e.: bzr push lp:~inkscape.dev/my-project-name/branch-name Then under the Code tab of your project in Launchpad, click 'Configure code hosting' and specify this branch name for "Link to a Bazaar branch already on Launchpad". Optionally, you can also change the Maintainer for your project to 'inkscape.admin'. Note that you lose some ability to configure the project once you do this, so only change it if you really want to turn over administration to the inkscape admins. Launchpad permits establishing groupings of projects under an umbrella project. All the sub-projects would share certain settings. Presently we don't have a project group for inkscape, but I think we've accumulated enough projects that it's time to set one up. Once this is done, to add another project to the Inkscape project group you'd go to your project's configuration page and under "Part of" hit the Choose button and type 'inkscape', and then select the inkscape group project. On Tue, May 13, 2014 at 11:10:55PM +0200, Johan Engelen wrote: > On 13-5-2014 23:05, Vinícius dos Santos Oliveira wrote: > >Em Ter, 2014-05-13 às 21:14 +0200, Johan Engelen escreveu: > >>Please apply the attached patch to the libdepixelize repo > > > >Done (r187). > > > >>(inkscape dev's have no access). > > > >This is a mistake. > > > >How do I transfer a repo to the Inkscape organization? > > > >I remember Jabier had to create another org just to give commit > >access to other Inkscape developers. > > I don't know. > Perhaps you can add people with commit rights. The one you want to > add is "inkscape.dev", which is the team of all people with commit > access to Inkscape trunk. > > regards, > Johan > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 0

[inkscape-devel] Cannot compile with newest version of poppler
by Preben Soeberg 14 May '14

14 May '14

Hi devs, I recently ugraded poppler on Linux from version 24.5 to 26.0, and can no longer compile inkscape. See attached file for details. I do strongly believe the problem comes from changes in poppler, as I can no longer compile older revisions, that I have compiled before. I have also upgraded gcc to version 4.9.0, but don't find it likely to be the cause this problem. Regards Preben

3 2

Use of mailto: in Inkscape web page.
by john Culleton 14 May '14

14 May '14

Inkscape has a facility for addressing urls. Does this extend to the mailto: feature? Has anyone used it successfully? -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: "Create Book Covers with Scribus" available at http://www.booklocker.com/books/4055.html

1 0

Slow boot term window
by Jelle Mulder 14 May '14

14 May '14

Hi guys, Maybe this helps in solving the slow start mystery. I had the slow start on win7 until I rebooted the machine. This morning Inkscape booted quite a bit faster, but the load screen had quite a bit of these warnings. Those however seem to be bogus as MS Serif is being loaded and usable. Not sure what the 10 is about though? Fontsize? Or did that accidentally get added to the string? In the latter case it wouldn't be surprising that Inkscape gets a wee confused. For those that are wandering what the slow boot time is about, I would like to ask if they have large font sets on those win7, win8 and Mac. Large font sets have been a long standing issue for slow boot times and maybe it is related to that. This morning my Inkscape boot was faster than ever before though, regardless of the list of warnings. (Inkscape.exe:6112): Pango_Warning ** couldn't load font "MS Sans Serif 10", falling back to "Sans 10", expect ugly output. etc. Interesting as most win and mac do not have "Sans". Oh, and another rather silly bug I found was at filling in the Dublin Core metadata. After typing in the first letter of the Title, the input loses focus it seems and nothing happens anymore (or it doesn't display) reselecting the field will allow you to finish the word. Doesn't seem like a biggie to me, but it IS annoying and highly visible to all and every user that would use the form. i.e. anyone who produces content professionally. I would use the bugtracker if I was able to, but I have not been able to connect to it since I live in China. This may be an issue for Chinese people that would like to help with Inkscape dev as well. If tools are unreachable... Continue to test. Cheers, Jelle

3 2

inkscape-0.91pre0 source tarball
by Bryce Harrington 14 May '14

14 May '14

Download it at: https://sourceforge.net/projects/inkscape/files/inkscape/0.91pre0/ Tagged in trunk as: INKSCAPE_0_91_PRE0 The dist directions[1] are outdated, so I'm not confident the package is perfect, but that's why we do pre-releases right? Anyway, if anyone knows a step I missed, please raise it with me so pre1 will be better. I'll try to put some time in this cycle to get these directions up to date, and hopefully streamline the process a bit. I'm hoping to do several pre-releases in support of this. It would be helpful if packagers could generate binary platform packages from this tarball. If you spot packaging problems (like version numbers that didn't get updated, or missing files needed for builds), please raise these problems with me ASAP. Bryce 1: http://wiki.inkscape.org/wiki/index.php/Creating_Inkscape_distributions

11 28