November 2005 - Inkscape Devel

WEBFORM inkscape on pocket pc
by Miguel Ozonas 11 Nov '05

11 Nov '05

Message from Inkscape submission form Please note, that the submitter may not read this list. CC your answer to the submitter name: Miguel Ozonas email: miguelozonas@...1075... submitted the following: Enter your message or news here. Hi, i just have downloaded your software and play it, and i have a question. Are you thinking to convert te software for pocket pc?

1 0

inkscape windows icon refab
by Bob Jamison 11 Nov '05

11 Nov '05

Hi, all... Hey, we talked about this a year ago, but nothing happened. The inkscapexxxx.ico file that we use for the Inkscape "Application" icon (resource #300), is a fix of the crappy old .ico that I made myself when we first started working on a 'standard' Windows build. I am in no way an artist, and the thing looks utilitarian and boring. So I ask the question again: is there some guy who can make a new icon which is DIB-like (various sizes) and yet pretty at the same time? Of course there are lots of people who can make nice 48x48 or 32x32 images, but we need a Windows guy who knows and can cope with the constraints of a .ico (limited colors, etc) bob

6 6

NEW: shortcuts, misc
by bulia byak 11 Nov '05

11 Nov '05

- Now you can use Shift+middle button drag in any tool to zoom into an area. This works the same as simple drag in Zoom tool, but is faster because it does not require switching away from your current tool. Together with middle button drag (panning), middle button click (zoom in) and Shift+middle button click (zoom out), this completes the set of canvas navigation shortcuts available in any tool. - In Gradient tool, Shift+R reverses the gradient definition (i.e. mirrors the stop positions) without moving the gradient handles. For example, an elliptic gradient with blue center and red periphery becomes red in the center and blue in the periphery. This works on the gradient(s) of the currently selected gradient handle or, if no handle is selected, on all selected objects' gradients. (Compare with the Node tool where Shift+R reverses the direction of the selected path.) This is especially convenient for radial gradients which, unlike linear, you cannot simply rotate by 180 degrees for the same result. - When toggling one of the "transform with object" buttons (for stroke width, rounded rectangle corners, gradients, or patterns), a message is displayed in the statusbar explaining what has changed in the program's behavior. - Zoom commands in the View menu are moved to a submenu; the Zoom In and Zoom Out commands are added to that submenu. - The contents of the statusbar message are now duplicated as a tooltip that is shown when you hover the mouse over the statusbar. [TODO: need to strip <b></b> from the tooltips.] - Whole thousands above 2000 in the rulers are now displayed as 2k, 3k, 4k etc. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

NEW: Transform dialog redesign
by bulia byak 11 Nov '05

11 Nov '05

Fixes and improvements in the Transform dialog (Ctrl+Shift+M): - The "Apply to each object separately" checkbox is added, allowing you to scale/rotate/skew each selected object by the same amount, around that object's center. When off (by default), the selection is transformed as a whole. The status of this checkbox is remembered across sessions. (It has no effect on Move and Matrix tabs). - The new Clear button resets the values on the current tab to defaults. - The Scale tab now allows you to specify horizontal or vertical size increments in percentage or absolute units. Also there's a "Scale proportionally" checkbox which ensures that scaling preserves the width/height ratio. (If you are scaling several objects proportionally with "Apply to each object separately", you can only use the % unit to specify the scaling; otherwise each object's scale increments will have the width/height ratio of the entire selection, not of that specific object.) - The Skew tab can now specify the skew as an absolute displacement (e.g. for horizontal skewing of a rectangle, that means the shift of the top rectangle side relative to the bottom), as percentage displacement (e.g. a 1% horizontal skew of a rectangle means shifting the top side by 1% of the rectangle height), or as an angle (e.g. horizontal skew by 15 degrees results in the sides of a rectangle being rotated to that angle, while the top and bottom remain horizontal). - The Matrix tab (previously called "Transform") can either edit the current transform= matrix of an object, or post-multiply the transform= with the matrix you specify, depending on the "Edit current matrix" checkbox. As it is now redundant, the matrix in the Object Properties dialog is removed. - The dialog now correctly watches selection changes in the active document window and updates its values accordingly. - The layout of the dialog is simplified, tooltips and mnemonics added for better usability. - Many bugs are fixed, especially in value conversions between units. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

[root@...1070...: [Inkscape-tester] inkscape build report]
by Bryce Harrington 11 Nov '05

11 Nov '05

Some different build warnings than normal... ----- Forwarded message from root <root@...1070...> ----- Date: Thu, 10 Nov 2005 22:50:40 -0800 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Thu Nov 10 17:37:54 2005 (Run 734) Snapshot: inkscape-20051110-0700.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 6 0 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == none == Warnings == style.cpp:1254: warning: enumeral and non-enumeral type in conditional expression style.cpp:1261: warning: enumeral and non-enumeral type in conditional expression display/canvas-arena.cpp:87: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:87: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:133: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:133: warning: (perhaps the `offsetof' macro was used incorrectly) == Environment Summary == ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

[cworth@...573...: [cairo] Slipping 1.2.0 out to 2005-12-15, and help needed]
by Bryce Harrington 11 Nov '05

11 Nov '05

----- Forwarded message from Carl Worth <cworth@...573...> ----- Date: Thu, 10 Nov 2005 16:47:09 -0800 From: Carl Worth <cworth@...573...> To: cairo@...278... Subject: [cairo] Slipping 1.2.0 out to 2005-12-15, and help needed Shortly after cairo 1.0.0 was released, I picked an out-of-the-hat date of 2005-11-01 for cairo 1.2.0. That date has now come and gone, so so much for my powers of prognostication. I recently looked over the 1.2.0 roadmap [*] and saw that there's quite a bit still left to do. Personally, I've been focusing on the PS and PDF output quality issues. The hard parts of that are done now, but there's probably at least a week or two of work still to be done there. I had considered finishing those things up to get a 1.2.0 release out as soon as possible (in the next week or two) and letting everything else on the roadmap slip. But it looks like that's not going to be possible. I probably won't have much time to dedicate to this work until the beginning of December. So 1.2.0 won't be happening before 2005-12-15. This does provide more time for other interested people to jump in and fill the gaps for the remaining pieces of 1.2.0. If any of the following sound important to you, please consider getting involved: * win32 backend We basically just need to get it plugged into the test suite. For a long time, the issue here was missing support in the test suite for RGB24 output and for backend-specific reference images. But thanks to Keith's efforts with getting the PS backend into the test suite these two problems are fixed. So, is there a cairo-win32 developer that could fill in the two stubs in cairo/test/cairo-test.c: cairo_surface_t * create_win32_surface (int width, int height, void **closure); static void cleanup_win32 (void *closure); If so, that would be a great help and would definitely contribute a lot toward making sure that cairo-win32 remains stable in the future. * cairo_begin_group/cairo_end_group I sent a half-started patch for this to the list sometime ago. I feel good about the API, (though maybe the patch was before the addition of the current CONTENT support, and if so it should be updated to that). But the real work here is to make the intermediate surface auto-growable, which might require a tweak in the pattern code to get the offset right when the intermediate surface is finally painted. I really like this API, and I'm looking forward to having it available. I'd be glad to help anyone interested in working on this piece. * Performance fixes There's always more to be done here. I'm going to make that a big focus of my efforts post-1.2.0 by working on a performance regression suite and tackling some long-standing issues. We probably don't need much here before 1.2.0 since people are claiming that cairo 1.1.1 is already performing much better than 1.0.2. (Of course, there's still a lot of room for improvement, but this isn't something that should slow down 1.2.0 I think). * SVG backend The roadmap has this as experimental, so I think it can be thrown in at pretty much any point. It just needs someone to look at it first. I will do this after the PS and PDF stuff is done if nobody else has by then. * Bug fixes There are a couple of fairly serious bugs listed in ROADMAP already that I think really need to be fixed. A couple of the XFAILs obviously need to be fixed as well, (such as the *ahem* segfault from extend-reflect). Meanwhile, there have been a bunch of little bug reports, (slight build problems on various platforms for example), that should be pretty easy picking for almost any willing volunteer. As usual, there's almost no end of fun work to be done. I appreciate everything that so many of you are already doing. And this is also a great chance for some new faces to jump in and make some contribution. I'm glad to provide more details and guidance on any of the above as needed. -Carl [*] http://cairographics.org/ROADMAP _______________________________________________ cairo mailing list cairo@...278... http://cairographics.org/cgi-bin/mailman/listinfo/cairo ----- End forwarded message -----

1 0

newest gtkmm-dev necessary to compile HEAD
by Ralf Stephan 11 Nov '05

11 Nov '05

Hello, So it appears one needs the newest gtkmm libs to compile HEAD. I did not foresee this when using some features of the library, and, now that people have upgraded, it's nonsense to revert ;) What's unclear to me is which version is fine, here it is libgtkmm-2.4-dev 2.8.0-0ubuntu1, can others add info? thanks for your patience, ralf

9 15

Plugins translation
by Cédric GEMY 10 Nov '05

10 Nov '05

I would like to know how to translate plugins Dialog options ? it appears to me that they are not inside de *.po files. Should we have a look at *.inx or *.py files ? Cedric

4 3

Inkscape 0.43pre2
by Ted Gould 10 Nov '05

10 Nov '05

https://sourceforge.net/project/showfiles.php?group_id=93438&package_id=991… It is likely that this will be the last prerelease for Inkscape 0.43. If packagers can make packages to ensure the completeness of the package, and if users could make sure it is stable, we'll hopefully be ready to release 0.43! Please submit comments quickly, this prerelease will be a short lived one. MD5 Sums: daa81da8ca152d809aa39ee2c9cd5d04 inkscape-0.42+0.43pre2.tar.bz2 af42797a6b9d3e4d443b3f33717394ba inkscape-0.42+0.43pre2.tar.bz2.sig e46a04eb78ea53876f1fd77c34e5d7d6 inkscape-0.42+0.43pre2.tar.gz 82038ffc49dfb8ba7c9a309cf54046f1 inkscape-0.42+0.43pre2.tar.gz.sig --Ted

5 16

How do we deal with unnamed root layers?
by Wolfram Quester 10 Nov '05

10 Nov '05

Hi alltogether, some time ago I got a bugreport[1] against the debian package of inkscape 0.42.2. The user has problems with editing old drawings containing a "root" layer in the new inkscape version, where the layer is called "Layer 1". Don't we have a compatibility option somewhere? I quote two of his mails further down for details. With best wishes, Wolfi [1] 333779@...499... Ambrose Li wrote: If I edit a drawing with several layers and the root layer contains artwork: After selecting a non-root layer, the "(root)" in the layer selection menu (the one along the bottom edge of the window) disappears. For example, if the drawing has three layers: root, "layer 1" and "layer 2", after selecting "layer 1", only "layer 1" and "layer 2" will remain in the layer selection menu. (If I now click an object that is on the root layer, the "(root)" reappears in the layer selection menu. So the bug is not exactly serious, provided that I can select some object that is in the root layer.) ... I found that new drawings do not have a root layer, but a "Layer 1". So, I cannot reproduce the bug with new drawings, only old drawings with root layers. Perhaps the bug is caused by lack of backward compatibility. (I.e., the developers might have changed the default layer name, and then forgot that old drawings have an unnamed root layer.)

3 5