January 2008 - Inkscape Devel

Problem with real units (mm)
by khiraly 19 Jan '08

19 Jan '08

Hi! Problem 1: I have switched everywhere (in inkscape) to unit mm. I only want to use that unit (and not px), for everything. Now, when I move something on canvas (or just a node) inkscape still write into the svg file the coordinates without unit (so pixel) and it calculates back and forth between pixel and millimeter. This approach has two disadvantages: - almost impossible to hand edit the resulted file or correct some inaccuracies in it. (because I need a calculator when I want to touch the file) - inaccuracies inserted for sure Problem 2: If I specify the unit in svg file, inkscape does not handle it, and misinterprets the file! Two Examples: 1: <path d="M 0,0 L 30mm,0 L 30mm,30mm L 45mm,30mm" id="path7887" /> becomes in inkscape (after modifying something in xml editor (ex: style), or moving a node): <path d="M 0,0 L 30,0 M 30,0 L 30,0 M 60,0 L 45,0" id="path7887" style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" /> Second example: <g transform="matrix(1 0 0 -1 0 297mm)">  </g> I want to use it for flipping my coordinate (to carteesian coordinate), so I could more easily hand-edit/correct my drawing. But it does not work (I assume because of the unit specificator) Does anybody know a workaround? Best regards, Khiraly

3 5

Inkscape 0.46pre0
by Ted Gould 19 Jan '08

19 Jan '08

Hello, I've gone and rolled a 0.46pre0 package for everyone's delight. Mostly the goal here is to start the packaging process and give packagers a chance to get angry at the distribution makers (me). This also gives a nice line in the sand for bug reports. 80fc7b7c1fe56976b8a2d33ed952c454 inkscape-0.45+0.46pre0.tar.bz2 ea746cd7b679e7c9790b45393513db2d inkscape-0.45+0.46pre0.tar.bz2.sig b5fe65ed8db1c5b23b82d2cbc5cc0447 inkscape-0.45+0.46pre0.tar.gz 4c6807e0d7c90e9ad78a687ffba57a90 inkscape-0.45+0.46pre0.tar.gz.sig cff5a26997c51079d51731a612ff3d11 inkscape-0.45+0.46pre0.zip 63c8853f3ae5f6dd6861b0502340d005 inkscape-0.45+0.46pre0.zip.sig I went ahead and MD5 summed the GPG signatures. I'm not sure if that makes things more secure, but I do find it funny. https://sourceforge.net/project/showfiles.php?group_id=93438&package_id=991… Tell me where I messed up! --Ted PS - I'll get SVN all tagged nice tomorrow, I'm tired now.

3 5

Inkscape 0.46 About Screen Contest - Developer choosing time
by Josh Andler 18 Jan '08

18 Jan '08

Hello all! Community voting results for the about screen contest: http://inkscapers.deviantart.com/journal/16414256/ As it goes, the developers are now choosing from the top 3 to decide which one best fits the upcoming release. If you click on the thumbnails of the about screens, on the page you are then taken to, there is a download link on the left to obtain the SVG files. Since I know that would be everyone's first question. ;) I imagine the decision can be made in 3 days so we can then request/discuss/make tweaks shortly thereafter. Cheers, Josh

14 20

Re: [Inkscape-devel] Attaching parasite information to an object (or group)
by khiraly 18 Jan '08

18 Jan '08

On sze, 2008-01-16 at 22:03 +0000, john cliff wrote: > if you add an attribute in the inkscape namespace such as > inkscape:whateveryouwant i believe it shouldnt get lost. I have read a bit of svg specification, and I have found what would be standard compliant. An container element (like 'g', the group) can have a <title> and a <desc> element. I have added this to my group, and inkscape preserves it. However, inkscape also adds an additional id to the <desc> which I dont think so is permitted. So when i copy my group, it becomes like this: <g id="g7890"> <desc id="desc9">this is my component</desc> <path id="path7884" d="M 168,215 L 397,215" style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" /> <text id="text7886" y="264" x="217" style="font-size:12px;font-style:normal;font-weight:normal;fill:#000000;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Vera Sans" xml:space="preserve"><tspan y="264" x="217" id="tspan7888" sodipodi:role="line">component's name</tspan></text> </g> If somebody are interested, here is a bit more information about this: http://www.w3.org/TR/SVG11/struct.html#DescriptionAndTitleElements I tried validate my svg document through validate.w3.org, but there are many errors, so I cant be sure if it is valide or not. The question is: Is it permitted and desirable to attache an id tag into a title or desc element? So which one is preferred?: <desc>this is a description</desc> vs. <desc id="desc9">this is a description</desc> And the latter is still valid svg? Best regards, Khiraly

2 1

Attaching parasite information to an object (or group)
by khiraly 18 Jan '08

18 Jan '08

Hi! Right now im developing a little extension, and I have a problem what I could not get workaround. I hope someone more knowledgeable can me give a hand. Im implementing cross referencing in inkscape (it can be found on many schematics), please take a look at this example: http://khiraly.googlepages.com/crossreference.png The problem is, when a group (or object) is copied, all the ids got a new random string, so it cant be determine the original ids or the original component's type. All the component is similar (from a svg point of view) so it consists lines and texts. So Im looking forward to attach infos to an svg group, which persiste, when the group is copied. Im interesting in any method, like defining a css style, adding a parasite information, or rename the resulting group's id back to its original form plus a random character. Can anybody help me here?

2 2

missing verbs
by Alexandre Prokoudine 18 Jan '08

18 Jan '08

Hi, Every time I start Inkscape from console I see this: $ inkscape Unable to find: FilePrintDirect ** (inkscape:26549): WARNING **: Unknown verb name: FilePrintDirect Unable to find: ToolCalligrphic ** (inkscape:26549): WARNING **: Unknown verb name: ToolCalligrphic Unable to find: ToolCalligrphic ** (inkscape:26549): WARNING **: Unknown verb name: ToolCalligrphic Unable to find: ToolCalligrphic ** (inkscape:26549): WARNING **: Unknown verb name: ToolCalligrphic Unable to find: EditCloneOriginal ** (inkscape:26549): WARNING **: Unknown verb name: EditCloneOriginal Unable to find: EditCloneOriginal ** (inkscape:26549): WARNING **: Unknown verb name: EditCloneOriginal Unable to find: HelpKeys ** (inkscape:26549): WARNING **: Unknown verb name: HelpKeys Is it normal? Alexandre

3 4

remove fedisplacementMap ?
by Felipe Sanches 18 Jan '08

18 Jan '08

feDisplacementMap seems to be so useless if we dont have feImage that I think we could hide it from users while we dont have feImage Juca

2 1

min/max values
by Alexandre Prokoudine 18 Jan '08

18 Jan '08

Hi, One of quite annoying usability issues is that in many cases min/max values are unknown and/or unpredictable. Few examples: - all LPE options - Gaussian blur - 0 to 100,0 of what - pixels? A hint for them could include the missing bit of information, e.g. "... (0 to infinity)." Should we be trying to fix those? Alexandre

2 1

"Ask a Question" on help menu
by Felipe Sanches 18 Jan '08

18 Jan '08

I suggest that we add an entry on the help menu that links the user to the "ask a question" page at launchpad Juca

3 6

disable some filters
by Felipe Sanches 18 Jan '08

18 Jan '08

we need to find out a way to hide some filters from the ui because they are not implemented yet. These filters are feFlood, feTile, feImage and feComponentTransfer feImage is only partially implemented. I wrote the patch that is attached to this email. It seems to work, but it crashed once when I tried to add a primitive to an opened SVG that contained one of these four filter primitives. Maybe we should instead let these 4 primitives listed on the combobox but display a message saying that they are part of the SVG specs but not implemented yet. Juca

5 18