- Inkscape Devel - Inkscape Mailman

LGM
by Alexandre Prokoudine 10 Apr '09

10 Apr '09

Hi, Inkscape is listed as main project at Libre Graphics Meeting, and yet Ivan Louette seems to be the only guy who signed up. Is anybody else coming? Ted? Bryce? Jon? Bulia? Mental? Alexandre

4 3

Refactoring freeze: tomorrow!
by bulia byak 09 Apr '09

09 Apr '09

Guys: I understand that coding is addictive, but we must finally move ahead with the release. So, unless there are serious objections, I declare a refactoring freeze starting tomorrow at noon EST! Please do all your refactoring commits before then. To refresh your memory, a refactoring freeze means: > no lib migrations, no rewriting and rearranging code "for general correctness", and no 2geom syncs "just in case" until the release. I realize this is all done for good reasons, but experience shows that each such wave of changes brings bugs that keep popping up long after the wave has passed. So, let's stop refactoring and start bugfixing in a serious way. Thanks for cooperation! -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

4 4

SVG Open Call for participation
by Ted Gould 09 Apr '09

09 Apr '09

Hello, For those who are interested the Call for participation for SVG Open this year has gone out. Very exciting, and specifically I can comment on how nice conferences are on the Google campus. All the information is in this mail, of course Inkscape related SVG topics would be interesting to most of the participants. http://lists.w3.org/Archives/Public/www-svg/2009Apr/0052.html It would be cool to have a good showing at the conference. --Ted

1 0

Couple of text bugs
by Thomas Worthington 09 Apr '09

09 Apr '09

I went to print a piece of text on a path last night and nothing appeared. Once the text was converted to paths itself it printed fine. Version 21051. Another, long-standing bug, is that text behaves strangely when aligning. I generally find that of several pieces of text the one used for "relative to" is fairly random; certainly the choice in the alignment menu is frequently ignored. I've not found a pattern yet - the object's ID does not seem to be the basis of the choice nor does the type of alignment (baseline, left, top etc) seem to matter. The order of the objects on the page seem to have something to do with it. Anyone else seeing this? -- Thomas Worthington Tech Nouveau 32 Bangor Road Groomsport BT19 6JF 07748 792333

1 0

Conditional compilation in 2geom
by unknown＠example.com 09 Apr '09

09 Apr '09

Hi all, Recently in 2geom, "HAVE_GSL" and "GPL_TAINT" #defines were created, to optionally leave out certain parts of 2geom. How should Inkscape handle these things? Should the make script define those things on the commandline? Or should 2geom provide hooks to a 'config.h' of its own that Inkscape can tweak? Thanks for thoughts, Johan

3 2

The bias property for feConvolveMatrix
by Jasper van de Gronde 08 Apr '09

08 Apr '09

The SVG standard defines a "bias" property for feConvolveMatrix to offset the result of the filter. It specifies that this value should simply be added to the result for each channel. Implicitly the standard defines that these are premultiplied color values, however, this seems to make little sense, as the bias has very little meaning without taking the alpha channel into account. The standard also says that one of the applications of a bias is "to have 0.5 gray value be the zero response of the filter", this seems to be directly contradictory with adding bias to the premultiplied values (as then the same bias could suddenly stand for white if alpha was 0.5). So, what to do? Batik doesn't seem to support bias!=0 at all, so there is also no precedent. I currently let feConvolveMatrix make bias relative to alpha.

2 1

Re: [Inkscape-devel] lpe-crash
by Guillermo Espertino 08 Apr '09

08 Apr '09

This has been fixed as of rev. #21094 by Diederik. It was indeed a bug in snapping code. I created the report #356743 for that, which I'm closing as fixed right now. Gez.

1 0

lpe-crash
by jf barraud 07 Apr '09

07 Apr '09

Hi all, For some unknown reason, all lpes having theire own "addCanvasIndicators()" (namely lpe-knot and lpe-cpopyrotate) now crash inkscape whenever you try to edit with the node tool. Just in case someone is aware of some recent change in the code causing this, please make suggestions, it might save me some time trying to understand what is going on! ;-) Cheers, jfb.

3 2

group options in export dialogs
by the Adib 06 Apr '09

06 Apr '09

Hello, how is it possible to group several options in the export dialogue? I think about a grouping inside static box and grouping inside multi tab pane. I would like to group all options related to: - export area/object - font options - file format compatibility / subformats - handling of linked images Good would be if I can save/restore my settings :-) This could be done by defining <group> and <page> tags What do you think? Adib. ---

1 0

Re: [Inkscape-devel] Snapping toolbar
by Diederik van Lierop 05 Apr '09

05 Apr '09

Op Vr, 16 januari, 2009 01:39, schreef Rock Star: > The difference between creating and editing can be somehow seen from the > video [1]. That video indeed explains everything! A few months ago I introduced a snapping delay, which makes snapping in Inkscape much more responsive in complex documents. That snapping delay is what you noticed when editing objects, but it apparently it doesn't work when creating objects. I will fix that. If however you prefer the old behavior without any delay, then just go the preferences -> snapping and set the delay to zero. > Now I see the problem with guides and grid and toggles. However, since I > come more from a CAD world, I'm used of snapping to whatever is visible. > Hence, if there are 2 grids turned on, I would expect to snap to both. > This > would than mean 2 more toggles. If you see grid/guides it snaps, otherwise > not. Maybe it isn't a problem after all to add an additional toggle in series. When creating a grid, the per-grid snapping is turned on by default. So if a user is not aware of this then he won't notice, and if he turns it off then... well, that's his/here responsibility ;-). So we would end up with these options in series: 1) the global snapping toggle -> EVERY USER MUST KNOW ABOUT THIS** 2) the GLOBAL grid snapping toggle -> CLEARLY RECOGNIZABLE ON THE TOOLBAR 3) the PER-GRID snapping toggle -> ON BY DEFAULT 4) snap bounding box corners toggle or the snap nodes toggle -> EVERY USER MUST KNOW ABOUT THIS TOO** **) ... but only if they care about snapping obviously. > Anyway, thanks for the answer and additional explanation. You're welcome. Thanks for your feedback! Diederik

5 15