January 2004 - Inkscape Devel

[Fwd: [Sodipodi-list] Writing SVG code for editing with Sodipodi]
by Jonathan Phillips 26 Jan '04

26 Jan '04

Looks like the UNITS problem! Arg! It seems like there are all these containers of ideas and badly implemented ideas that are TODO that still hang over us still in INKSCAPE. I say we evaluate, disable, and remove any of this unimplemented or crappy code from the project. It will probably make our life easier in the long run. The units problem is horrible. Our printing system and export system are pretty bad too. ARG! Jon -----Forwarded Message----- From: Pierre Abbat <phma@...177...> To: sodipodi-list(a)lists.sourceforge.net Subject: [Sodipodi-list] Writing SVG code for editing with Sodipodi Date: Sun, 25 Jan 2004 11:22:47 -0500 I wrote a two-line program that generated a lemniscate and pasted the code into a <path> element in a Sodipodi file. Since the width and height are in millimeters I thought the coordinates would be in millimeters. They weren't. The lemniscate was too small. I then edited it so that it looked like M-87.4619707139396mm 42.4024048078213mm M-88.2947592858927mm 41.4518786277521mm M-89.1006524188368mm 40.4508497187474mm and tried again. The lemniscate went flat. I removed the millimeters and scaled it and put it in the middle of the 300*300mm square. The center is now at 531.4961,531.4961. What unit is Sodipodi using, and how do I tell it that the coordinates are in millimeters? phma -- Jonathan Phillips <jon@...15...>

2 1

export background
by bulia byak 26 Jan '04

26 Jan '04

Now the page color, settable in the document options dialog and saved with the document, is also used as the background color when exporting anything from this document. By default this color is white and 100% transparent, so the default export has transparent background as before. However you can set it e.g. to white 0% transparent and have white background in PNG without having to add any background objects. For this to be possible I added inkscape:pageopacity attribute to the namedview. Now the page color is split into the pagecolor and inkscape:pageopacity attributes - ugly but at least partially compatible with Sodipodi. By the way, Sodipodi now has an extra color picker right on the Export dialog for the same purpose (setting background color for export). I think simply using page color is more natural and convenient. Especially given that, in the typical Sodipodi fashion, that picker's color is not saved/restored anywhere... I'm also thinking about saving export dpi in the namedview as well, so that each document would remember its last dpi setting. I think it's logical. Other improvements today: font list in the text dialog is autoscrolled to always show selected font; text object description shows font in the statusbar; currentColor and userSpaceOnUse fixes ported from Sodipodi; and many other bugfixes. _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoi…

1 0

Proposal: "inkscape-user@" mailing list
by Bryce Harrington 26 Jan '04

26 Jan '04

For the purposes of assisting users following the 0.37 release, we should create an inkscape-user@ mailing list at this time. The purpose of this list would be to serve as a place for users to share tips and tricks and help each other learn how to make effective use of the tool. Having a place to build a user community will be adventageous, as many users may find devel lists overwhelming. If this sounds good, I'll set it up, and we can push membership in it as part of the 0.37 announce. Bryce

1 1

RE: [Inkscape-devel] Win32 - Bug in Markers?
by bulia byak 26 Jan '04

26 Jan '04

>Can someone check please? > >The line markers are not working with the freehand line or bezier curve >tools. I get the messages 'start_marker' marker is '<nil>', >'mid_marker'...... and 'end_marker'........is nil, as soon as I start. The >end cap choices are working. For me, nothing works at all in today's CVS. When I click any marker button, Inkscape crashes. >This is the first time I have used this so I do not know if it is recent >behaviour. Yes, I think Bryce added it recently. I hope it gets resolved for the release. Are the preferences problems resolved? I recently tested it on Windows 98 and it seems to work OK. _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

3 2

Inkscape on Windows
by Ryan Pavlik 25 Jan '04

25 Jan '04

Hello developers! I am not a member of the list, I just sent this in to alert you of a potential installer problem. I have GTK 2.2.4-2 (from the Gimp web site) installed, which is the official version for Windows. However, when I try to install Inkscape, it quits the installer, asking me to install GTK2. I will continue to try to override this setting in the installer, as the official GTK should work fine... Ryan (any replies please copy to me, since I am off list)

1 0

sodipodi:type namespace
by MenTaLguY 25 Jan '04

25 Jan '04

I realized one other place where we need to be careful about not polluting sodipodi's namespace -- sodipodi:type. Currently, we only have one "type" of our own, SPOffset, but we can expect to add more. I think the best way to approach this is to prefix any types we introduce ourselves with inkscape: -- e.g. now the sodipodi:type for SPOffset will be "inkscape:offset". I think it's important we get these issues sorted out before the release. As a result, I've changed the sodipodi:type used in HEAD -- if you have existing documents using SPOffsets, you'll need to fix their sodipodi:type from the XML editor. -mental

1 0

backups
by bulia byak 25 Jan '04

25 Jan '04

To fix this: https://sourceforge.net/tracker/index.php?func=detail&aid=866103&group_id=9… I want to back up the old prefs file before writing the new one. Adding an option to backup SVG files when saving would be great, too. There's a library here: http://www.gnu.org/software/gnulib/ that has this functionality and claims to be portable. So what do we do? - include gnulib as a dependency - lift just backupfile.c and copy-file.c from it and include in our codebase - find some other lib - write the backup function ourselves Any comments? _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=dept/features&pgmarket=en-ca&RU=http%3a%2f%2fjoin…

2 1

Re: [Inkscape-devel] do we need meters?
by bulia byak 25 Jan '04

25 Jan '04

OK, for now I simply added a check if the units are meters, and if so, coverted them to cm where the value is written to repr. So now it will size the canvas to 3100 by 1700 meters, even though it will not show you all of it. But that's another issue. So I'm closing this bug. Incidentally, just to prevent duplicating effort, is anyone working on any bugs at the moment? The release is near and we must concentrate on bugs for now. _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

3 2

RE: [Inkscape-devel] Re: new offset commands
by bulia byak 25 Jan '04

25 Jan '04

Actually, the reason for bug 877019 is simple: it's difference is size! The sploth-bad object is just small, and on this scale, the offset algorithm is erratic. When applied to a larger object, it works much better. Can you please have a look at what's wrong with this? > > - It appears that all offsets now use the imprecise > > algorithm (you once > > mentioned that there were two algorithms, one > > precise but slow and the othe > > imprecise but fast). I think we should use the > > precise algorithm for all > > kinds of offsets, dynamic or not. > >the "imprecise" algo is now the more precise one; the >problem whith the old "precise" is that sometimes it >doesn't produce the mathematically correct offset, but >is faster. this can happen when offseting the 'D' >letter with a big radius, for example: a hole appears >in the offset. since speed is an issue, the fast one >is back in place. > > >also the livarot stuff now uses NR::Point (and some >NR::matrix); it may contain some bugs since the >conversion touched a big portion of the code. you can >report any strange behavior in boolean operations and >offset to me. _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

1 0

Re: [Inkscape-devel] do we need meters?
by bulia byak 25 Jan '04

25 Jan '04

>>lists only cm, mm, in, pt, pc. So the question is: why do we have meters >>in the units drop-down lists at all? Isn't it safer to remove them? >> >>Any insights? > >I've used inkscape for doing house plans. Having meters was quite useful >for that. We may end up having a global scale factor for doing map work >(which is something that bryce was interested in). Of course it's useful, but what about SVG conformance? Even if we convert meters to e.g. inches on save, how will Inkscape know that they should be translated back to meters when loaded? Looks like we need inkscape: attributes in <svg> for scale factor and preferred length units. That will require changes in a lot of places I think. _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

3 2