June 2016 - Inkscape Devel - Inkscape Mailman

windows build environment, current options
by mathog 06 Jun '16

06 Jun '16

Hi all, I am in the process of migrating over to a W7 machine [from XP, always cutting edge here ;-)] and want a little feedback on which Mingw to use. The Windows build instructions http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows (still) say: TDM's GCC (MingW): Please use exactly the version 4.6.1 32bit bundle installer and follow the instructions below. In the setup, Uncheck the [Check for updated files on the TDM-GCC server] when installing, or it will install a newer version. Newer versions (tdm-gcc-4.7+) introduce important changes in gcc and don't work with the current Inkscape devlibs (see developpers' list discussion). (Note: "developpers" is verbatim from that page.) Is this still correct? My current build environment on XP is straight Mingw 4.6.2. Current versions of gcc are 5.10 for TDM and 4.9.3 for Mingw from those developers. TDM still seems to support sjlj but Mingw is only dwarf2. From feedback on the Mingw mailing list they have not had sjlj since gcc 3.6.something, yet the inkscape I built worked with devlibs OK, or at least it seems to, perhaps I never triggered code that would have failed on dwarf2 and worked with sjlj. So, really go with that one version of TGM GCC or will the others work? Thanks, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

2 1

Re: [Inkscape-devel] Doc scaling compatibility issue (Bug 1389723)
by Olof Bjarnason 06 Jun '16

06 Jun '16

Does the Inkscape 'extended' .svg file format not contain information on what version of Inkscape it was saved in? On 6 Jun 2016 00:47, "C R" <cajhne@...400...> wrote: Is this related to why flowed text line spacing sometimes freaks out when loaded? It's been really messing me up lately. For an example, load this file: https://www.dropbox.com/s/3f43lyrr494m8cm/testfile.svg?dl=0 and try to change the line spacing in the text box. Works okay in 0.91 stable and not at all in current trunk. -C On Sun, Jun 5, 2016 at 8:59 PM, Bryce Harrington <bryce@...961...> wrote: > What do you think we should do about the release-critical DPI bug? > We need a decision on a course of action. > > > One of the changes we're bringing in this release is changing the > definition of px from 90 dpi to 96 dpi, but a consequence of this is > that documents created in 0.91 or earlier will become mis-scaled if used > in 0.92. This is tracked in the following bug report: > > https://bugs.launchpad.net/inkscape/+bug/1389723 > > This is a release-critical bug, the sort that is likely to become a > thorn in our side in the near to mid term as users start running into > it more and more. Longer term it will diminish as our users move to > newer versions, but I imagine it'll take multiple years before it goes > away completely. > > I don't think we should consider reverting the change; it was introduced > pretty early on this development cycle so backing it out could cause > secondary bugs to crop up. Also, it's a change that has to be done, so > if we don't do it this release we'll have to go through all the trouble > again next release anyway. > > One proposed approach is to detect the affected files on load and > display a warning with a recommendation to convert the file manually. > Javier has posted a conversion tool that could be made use of; it's > received a fair bit of testing but there may be some remaining corner > cases to sort out; on the plus side with it being a discrete utility > fixes could be rolled out for it without needing full Inkscape releases. > > The other proposed approach would be for Inkscape to internally convert > files, so that no warning is needed. In theory this would provide a > better user experience, but is going to require a lot more developer > effort and thorough testing. I'm doubtful that all of this can be done > adequately within the timeframe we're looking at for the release. > > Both approaches also require a mechanism to detect affected files, which > sounds like it may be the tricky part here, as our SVG documents haven't > had versioning information we could rely on for this case. > > Do you have thoughts on other ways to address this issue? Do you have a > strong opinion on whether for this release we should use the expedient > approach or else postpone the release until the more user-friendly > approach can be developed? Or should we reconsider a revert of the DPI > switch so we can get the release out and re-enable it post-release in > hopes the issues can be worked out? > > Bryce > > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

2 1

Help Needed on Release Notes
by Bryce Harrington 05 Jun '16

05 Jun '16

Can you lend a hand in writing a section or two for the release notes? http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92 1. Release highlights The write ups on the new features are spot on and look beautiful. We need to select a few of them deserving special mention - say 3-6 items - to make mention of in the 'Release Highlights' section. These should be like major changes, broadly useful enhancements that lots of people have been wanting, or specialized but powerful new capabilities. Stuff that can be described concisely but that will resonate with readers. 2. Notable Bug Fixes Could someone produce a dump or query of the bugs closed during this release period? Include a link to that listing here in this section. Then we need someone to look through those and pick out the (small?) proportion worth mentioning for the release - this will be pretty subjective but that's okay. We might want to categorize the list as platform-independent issues, Windows issues, OSX issues, and Linux issues. 3. Known Issues A link to current high/critical bug reports would be worth including here. >From that list we should pick out a subset worth mentioning in the release notes. This should be severe issues that will affect a broad number of users, or issues we're likely to get a lot of duplicate bug reports about. This should include our three release-critical bugs (we can move them to notables once they're resolved). Where possible, it would be useful to provide a sentence or two describing recommended workarounds, maybe with a link to the appropriate bug comment, forum topic, or mailing list email. 4. Anything missed? In general, review the release notes to see if there's any features that haven't gotten documented yet. Any new dependencies that should be mentioned? More translations? Thanks, Bryce

1 0

Inkscape 0.92pre0 Mac OSX 10.11.5 Compile Error
by Partha Bagchi 05 Jun '16

05 Jun '16

Tried compiling on the Mac. Get the following error: make[2]: *** No rule to make target `src/inkscape-version.cpp', needed by > `src/CMakeFiles/inkscape_base.dir/inkscape-version.cpp.o'. Stop. > make[1]: *** [src/CMakeFiles/inkscape_base.dir/all] Error 2 > make: *** [all] Error 2 My command line invocation: CXX="g++ -stdlib=libc++ " cmake -DCMAKE_CXX_FLAGS="-std=c++11 > -Wno-error=c++11-narrowing -Wc++11-extensions -O3 -ffast-math > -ftree-vectorize -mmacosx-version-min=10.8" > -DCMAKE_EXE_LINKER_FLAGS="-headerpad_max_install_names" > -DCMAKE_INSTALL_PREFIX=./Release -DWITH_GTK3_EXPERIMENTAL=YES > -DCMAKE_BUILD_TYPE=Release ..

2 2

INX Parameters
by ugajin 03 Jun '16

03 Jun '16

Hi, Is it possible to set the min/max param attribute values for an .inx file from within its associated Python scrip? E.g. when an int type param is not declared with min/max attribute values, the default values 0, and 10 are applied, and I would like to overwrite these, or whatever the values declared in the .inx file may be, from the associative Python script. I am guessing this may prove difficult, if the .inx file is parsed on loading Inkscape. Many thanks in anticipation. -u

4 9