- Inkscape Devel - Inkscape Mailman

Inkscape 0.46pre3
by Ted Gould 08 Mar '08

08 Mar '08

Hello Inkscapers, We've put out another pre-release of Inkscape. As we're getting very close to releasing 0.46 on platforms other than Windows testing is critical. On Windows, there are some release blocking bugs that could use developer attention. If you're a Windows developer please come help. If not, but you know one, time to buy him/her their favorite pizza and beer then tie them to a chair :) [1] --- All bugs should be submitted to --- http://bugs.launchpad.net/inkscape/ --- Release --- https://sourceforge.net/project/showfiles.php?group_id=93438&package_id=991… --- MD5Sums --- 0daed93fbf24da295499d844b54be621 inkscape-0.45+0.46pre3.tar.bz2 d486eb8b02641b90cb7750afd8477efc inkscape-0.45+0.46pre3.tar.bz2.sig 39a5d9451120cf953a811d6dde92adfe inkscape-0.45+0.46pre3.tar.gz 635ed77f488d2bf18b2c2be19cf900bc inkscape-0.45+0.46pre3.tar.gz.sig 427584d96ef0f07d5b78c74e96414a6b inkscape-0.45+0.46pre3.zip 190ca9ee4f96e180ce851bcb7bdd99f1 inkscape-0.45+0.46pre3.zip.sig Thank you everyone for continuing to use and help out with Inkscape. --Ted [1] Neither Ted nor the Inkscape project encourage violence towards Windows developers. They're all future Linux developers ;)

5 5

0.46.x stable branch practices for bugs and patches
by Bryce Harrington 07 Mar '08

07 Mar '08

With 0.46.0 nearly finished, bug fixes for our release should be targeted to 0.46.1. For 0.46.x we want just critical bugs: crashes, data loss, security vulnerabilities, severe regression, failure to build, etc. To mark an acceptable bug as needing fixed in a Stable Release, please 'milestone' it to 0.46.1 (or 0.46.2, ...) To mark a patch for an acceptable bug as needing integrated into the Stable Release: 1. Attach the patch to the bug report. 2. Confirm that the fix is in the main development trunk. 3. 'Nominate it for release' in launchpad for 0.46.x 4. Include this information: * Justification why its release-critical * Steps to reproduce * Explanation of the patch * Discussion of regression potential (Translation updates only need to follow steps 1-3) This makes it easier both for us to review patches, and for distro packagers to cherrypick and backport them. A more detailed version of this is at: http://wiki.inkscape.org/wiki/index.php/StableBranchUpdates Thanks, Bryce

1 0

Inkscape 0.46-final plans (March 10th)
by Bryce Harrington 07 Mar '08

07 Mar '08

ScislaC and I are quite pleased with how -pre3 has shaped up, and are making the last call for 0.46.0 bug fixes, translations, etc. We will tag 0.46.0 at UTC 04:00 Mar 11 2008. I've incorporated all patches sent to me or nominated for 0.46.x. If you have something I've missed, please get it to me this weekend. There are 7 milestoned bugs left: 3 are translations, 3 are windows-specific, and 1 has a patch that just needs a quick test. The translation patches I trust will be squared away in the coming days. Bug 189432 has a fix committed to trunk for upside down text with PDF, that just needs checked and I can commit the patch. For any remaining translation work, please arrange to get it incorporated in the release branch by March 10th. For the 3 windows bugs, progress has been slow on these. The consensus from the lengthy "0.46 release debate" thread is to tag 0.46.0 for Linux so we can get the release into Ubuntu and Fedora (which have a drop-dead date of March 13th for getting new Inkscape incorporated), but hold off on PR two weeks to give the extra time for Windows developers, because we would prefer to have full platform support for maximum PR effectiveness. If the Windows bugs are not sufficiently resolved by March 24th, we'll proceed with 0.46.0 being a non-Windows release, and hope they can be addressed in time for 0.46.1. Bryce

1 0

LGM 3 Presentation call — Heya!!!
by Louis Desjardins 07 Mar '08

07 Mar '08

Heya! Time to get yourself on the wiki for your presentations at LGM 3... it's coming! May 8-9-10-11 yes! 4 days! in Wroclaw, Poland, just 5-hour train ride from Berlin. http://create.freedesktop.org/wiki/index.php/Conference Please, don't be shy! Louis p.s. let us know you'll be there too. The Create List is our preferred one for talking most LGM stuff. Or get on IRC at freenode #lgm — Cheers!!!

5 5

Re: [Inkscape-devel] [Fwd: Re: Extensions on win32]
by Aaron Spike 06 Mar '08

06 Mar '08

Ted Gould wrote: > -------- Forwarded Message -------- > From: Ted Gould <ted@...11...> > To: bulia byak <buliabyak@...400...>, Aaron Spike <aaron@...749...> > Cc: Inkscape Devel List <inkscape-devel(a)lists.sourceforge.net> > Subject: Re: [Inkscape-devel] Extensions on win32 > Date: Sun, 02 Mar 2008 21:00:16 -0800 > > On Sun, 2008-03-02 at 20:01 -0400, bulia byak wrote: >> On Sun, Mar 2, 2008 at 9:59 AM, <J.B.C.Engelen@...1578...> wrote: >>> Now there should be a somewhat cleaner/better fix, however these two effects are broken again. The effects run successfully, but the parameters are not passed correctly. >> In rev 17608, function plotter works but dimensions and add nodes do >> not. Ted, can you please look into whether this might be caused by >> your recent fixes? > > With "Add Nodes" I get: > > Traceback (most recent call last): > File > "/home/ted/Development/inkscape.work/install/share/inkscape/extensions/addnodes.py", line 91, in <module> > e.affect() > File > "/home/ted/Development/inkscape.work/install/share/inkscape/extensions/inkex.py", line 154, in affect > self.effect() > File > "/home/ted/Development/inkscape.work/install/share/inkscape/extensions/addnodes.py", line 81, in effect > splits = math.ceil(length/self.options.max) > ZeroDivisionError: float division The inx file would seem to indicate that a value of 0 for max is unallowed. Are these constraints no longer enforced? When you run add nodes do are you passing 0 for the parameter? <param name="max" type="float" min="0.1" max="10000.0" _gui-text="Maximum segment length (px)">10.0</param> > and with Dimensions I get: > > /home/ted/Development/inkscape.work/install/share/inkscape/extensions/dimension.py:60: TagNameWarning: Tag names must not contain ':', lxml 2.0 will enforce well-formed tag names as required by the XML specification. > marker.set('inkscape:stockid', name) > > Aaron, do you have any ideas on what these could be caused by? This is a real error in the script: marker.set('inkscape:stockid', name) should be: marker.set(inkex.addNS('stockid','inkscape'), name) Aaron

3 5

lpe-blueprint
by jf barraud 06 Mar '08

06 Mar '08

Hi all, I just added an lpe-blueprint<http://wiki.inkscape.org/wiki/index.php/Lpe-blueprint>on launchpad. The goal is to gather ideas/props about lpe futur generations. The first part is about stacking lpe's from the UI viewpoint. Individual effects specifications are also collected, including propositions of new effects... (notice that things are not supposed to be developped in a short term; in particular, handling full svg data as parameter or output might require a lot of work!...) Remarks, comments, additions are wellcome! jfb.

2 1

Fix for #168283 in 0.46?
by Joel Holdsworth 06 Mar '08

06 Mar '08

I've just committed a bug fix for bug #168283: "possible to create empty paths via text -> object to path". Should the change be merged into the 0.46 branch? If so, the release wardens simply need to apply the attached diff. Thanks Joel

2 1

NEW: flasher when hovering over a path
by unknown＠example.com 06 Mar '08

06 Mar '08

Quickly: When you hover over a path in nodetool, it highlights itself briefly like a helperpath. (this means it only works for things that have a helperpath: paths only for now... work in progress i guess) When you leave the object with the mouse, it hides instantly. I haven't add preferences yet, so you cannot turn it off now, sorry; it's probably pretty annoying if you don't want it. What preferences do people want? - on/off - flash time? - flash color? ( i don't know how to XOR it, so right now it is invisible for red stroked paths ) - show knots aswell? Thanks for your input, and thanks to Josh for the excellent idea :-) Johan

6 8

Beyond CSS Fonts
by Gail Carmichael 06 Mar '08

06 Mar '08

Just wanted to let you know that I sent an email yesterday to the Pango mailing list, asking about the possibilities of expanding the fonts Pango can represent beyond what CSS can represent. Haven't heard back yet, and have no idea if they will tell me this is technically impossible or philosophically undesirable. However, if I get good news, this may mean I can help expand it and then support more fonts in Inkscape as a result. Will keep you updated. Gail

1 0

0.46 fails building on MacPorts
by Guido 05 Mar '08

05 Mar '08

I am trying to build Inkscape 0.46pre2 after updating the portfile of the 0.45 version (<http://trac.macports.org/projects/macports/browser/trunk/dports/gnome/inksc…>) which works flawlessly, including the Python plugins. Since the first previews, the compilation has been failing reporting the following error: /opt/local/include/python2.5/Object.h:104: error: 'Py_ssize_t' does not name a type [...] extension/internal/pdfinput/pdf-parser.h:343: error: 'Object' has not been declared extension/internal/pdfinput/svg-builder.cpp: In member function 'gchar* Inkscape::Extension::Internal::SvgBuilder::_createTilingPattern(GfxTilingPattern*, GfxState*, bool)': extension/internal/pdfinput/svg-builder.cpp:659: error: no matching function for call to 'PdfParser::parse(Object*)' extension/internal/pdfinput/pdf-parser.h:162: note: candidates are: void PdfParser::parse(int*, GBool) make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1 This happens also when cairo is built with the support for the PDF backend. Any suggestions? -Guido

1 0