August 2007 - Inkscape Devel - Inkscape Mailman

Announcing Raster Effects (via ImageMagick)
by Christopher Brown 21 Sep '07

21 Sep '07

Dear fellow Inkscape users, My Google Summer of Code project is now in SVN. My project is "Raster Functionality in Inkscape," which involved integrating ImageMagick libraries into Inkscape, in order to manipulate bitmaps from inside Inkscape. You'll have to install ImageMagick with Magick++ support (which is default) in order for these new extensions to work. They can be accessed under the sub-menu "Raster" in the extensions drop-down menu. The code is not quite in its final state--I am still perfecting and smoothing it out--but it's functional and I'd love to get feedback from all of you, especially from Windows users (because I have not tested it on that OS yet). Thank you all, -Christopher Brown

9 19

raster effects crashing
by Alexandre Prokoudine 19 Sep '07

19 Sep '07

Hi, Following raster effects crash Inkscape here (Ubuntu Gutsy Gibbon) on most recent SVN trunk: convolve shade wave raise And a couple of notes: 1. Do we really need flop effect since we can already flip raster images horizontally and vertically, while flop does it only horizontally and in a destructive way? 2. Types of noises in "Noise" effect are not translatable. 3. Names of channels in Channel and Level Channel effects are not tranlsatable. 4. Does Threshold actually work? I tried it on several images but didn't see any effect whatever value I specified (0-100). 5. Should raster effects probably provide some hints to tell range of possible values for each variable? 6. We seem to use "Variable: [value]" convention in GUI, but no (boh raster and path) effect uses ":" after name of variable. Should it be fixed? Alexandre

3 6

Re: [Inkscape-devel] Scheme Scripting Console
by Ted Gould 16 Sep '07

16 Sep '07

On Sun, 2007-08-12 at 18:47 -0500, Samuel A. Rebelsky wrote: > I'm the faculty member who supervises David and Soren's work. Thanks > for your regular and rapid feedback on their work! I hope we'll find > a way to get some Scheme scripting console into InkScape, even if > it's not the one that they've written. Anyway, I thought I should > respond to your two questions. Great to meet you. I don't see any major barriers to using theirs, just a couple details we need to work out. > I don't have much to say about the document locking issue; if there's > a better approach, I'm sure that they'd be happy to adopt it. What would you guys think about building the patch without this? I know it'd be slower, but then we could get some of the code into the tree so that you'd have less of a branch to maintain. > In terms of the TinyScheme issue, as best as I can tell, TinyScheme > semms to have replaced SIOD as the implementation language for Script- > Fu in the Gimp, starting with 2.3 (development) and 2.4 (release, > eventually), but I'm working as an outsider. I'm pretty sure the > discussion was in mid-2006. Let's see ... the developers mailing > list had a note about the replacement in week 42. <snip> > If you'd prefer that Soren and David use guile, rather than > TinyScheme, as the base implementation of Scheme for their InkScape > scripting console, that's fine with me. (And probably with them.) > However, it will delay their work somewhat, since they're starting > classes again, and their available time is going away. It really isn't as much about which Scheme interpreter, as much as how to include it. The problem that we run into is that if we include it in our source tree we end up maintaining that code. If we keep it as an external dependency, someone else maintains it. I like less work if possible. :) It would also make sense that if GIMP is using the same interpreter that we are, we make it an external package. That way bugs can be fixed in one place. From some of the stuff I've been reading on the GIMP webpage it seems that their version of TinyScheme is patched to work better with GTK+ (UTF-8 fixes). Is that the version you guys have included? > p.s. Your message to the Gimp developers' list did get posted, it's > at http://www.gimpusers.com/mailmsg.php?1186687639.4436.4.camel%40bender Still haven't received any responses. I'll see what I can find out. I'll wait for "Monday" to finish around the world first :) --Ted

3 3

object properties
by Alexandre Prokoudine 15 Sep '07

15 Sep '07

Hi, I have a very tough question, so feel free to punch me for that one :) What do we actually plan to do with Object Properties palette? It looks like it wasn't touched for ages. Recently I had a talk with a newbie user and he told me that he expected seing there more properties, both "global" and "specific". In that particular case he couldn't figure out how to change amount of an already created polygon's sides and he expected to see that in Object Properties palette. Then there was another feature request to make it possible choosing what properties of selected objects can be changed. E.g. in a selection of 25 objects you can have 12 objects which should not lose either fill or stroke or opacity or any specific for this type of objects property or any combination of the above, when you change it for the whole group. And as you know ;-) Inkscape, unlike Scribus, doesn't store changes per object within a session, so you can't aply changes to a group and then undo it for individual objects. So the second part of the question is whether we can make a better use of the Object Properties palette. In addition to what there already is in that palette we could add two groups of options: 1. Global options, i.e. Fill, Stroke, Opacity, Filters. 2. Specific options, i.e. the ones from tools options toolbar. For selections with multiple objects of different types (e.g. 2 stars and 3 rectangles) specific options would be greyed out. Each option would have a checkbox to allow/forbid changes to it, with 3 positions: yes, no, fuzzy (when at least two of the selected objects have different values, gtk supports it). Am I daydreaming? :) Alexandre

3 4

Inkscape native on OS X... almost
by jiho 12 Sep '07

12 Sep '07

hello all, Motivated by all the good things I saw about gtk on os x these days and repulsed by all the statistics I should be doing for my real life work, I gave a try at compiling inkscape with GTK native using MacPorts (so not using the all in one build script that Michael cook up a little while ago). MacPorts is the OS X equivalent of apt-get, portage, yum or whatever. We use it to provide Inkscape dependencies currently and it is very convenient to compile Inkscape that way. It is both easy (all second level dependencies are managed by macports) and economic (the libraries I compile for inkscape can be used in other projects). I wanted to keep this ease of use and to leverage the work of others, so I wanted to keep using MacPorts. The steps: 1- MacPorts includes native versions of gtk and cairo, which can be installed with: port install cairo +quartz gtk2 +quartz (gentoo and bsd users will recognize the "variants" switches added to both packages). there is a small bug in gtk which is known and solved by the patches in this ticket, at MacPorts: http://trac.macports.org/projects/macports/ticket/12566 hopefully they will commit this soon... but the bug report is quite old already. 2- Other libraries compiled against gtk or cairo need to be recompiled to use these new variants. namely: port -f uninstall cairomm gtkmm pango port install cairomm gtkmm pango this could possibly be solved by a clever use of upgrade when compiling gtk2 and cairo but I did not bother (I should have though...) 3- then compile inkscape from fresh make distsclean cd packaging/macosx/ change the compilation options to remove "--enable-osx-app" for now and then update, configure, build and install: ./osx-build-sh u a c b i compilation goes smoothly for latest svn... great great great!!! Now, on for the hard part: 4- run inkscape cd ../../Build/bin/ ./inkscape and here: (inkscape:20759): Pango-WARNING **: Error loading GDEF table 85 (inkscape:20759): Pango-WARNING **: Error loading GPOS table 85 (inkscape:20759): Pango-WARNING **: Error loading GSUB table 85 (inkscape:20759): Pango-WARNING **: Error loading GDEF table 85 (inkscape:20759): Pango-WARNING **: Error loading GPOS table 85 (inkscape:20759): Pango-WARNING **: Error loading GSUB table 85 (inkscape:20759): Pango-WARNING **: Error loading GDEF table 85 (inkscape:20759): Pango-WARNING **: Error loading GPOS table 85 (inkscape:20759): Pango-WARNING **: Error loading GSUB table 85 (inkscape:20759): Gdk-WARNING **: Unsupported cursor type 14, using default 2007-08-31 16:18:34.382 inkscape[20759] *** _NSAutoreleaseNoPool(): Object 0x14fef7a0 of class GdkQuartzWindow autoreleased with no pool in place - just leaking 2007-08-31 16:18:34.382 inkscape[20759] *** _NSAutoreleaseNoPool(): Object 0x14fee200 of class GdkQuartzWindow autoreleased with no pool in place - just leaking 2007-08-31 16:18:34.386 inkscape[20759] *** _NSAutoreleaseNoPool(): Object 0x14ffa730 of class GdkQuartzWindow autoreleased with no pool in place - just leaking 2007-08-31 16:18:34.390 inkscape[20759] *** _NSAutoreleaseNoPool(): Object 0x14fb9830 of class GdkQuartzWindow autoreleased with no pool in place - just leaking (inkscape:20759): Gdk-WARNING **: Unsupported cursor type 14, using default CGBitmapContextGetBitsPerPixel: invalid context cairo.c:91: failed assertion `status > CAIRO_STATUS_SUCCESS && status <= CAIRO_STATUS_LAST_STATUS' Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. (inkscape:20759): GLib-WARNING **: g_main_loop_run(): called recursively from within a source's check() or prepare() member, iteration not possible. Aaaargh. Anyway, the good points are that it is now quite easy to get GTK native in our regular building system and that Inkscape builds and links fine against it! Now, about the crash, it may well be that my system is still kind of dirty (I have some native things but the rest of the libraries are the old ones) but I think it is more likely a bug in cairo +quartz. I'll be happy to try to track it down and see if it is fixable in Inkscape or if this needs to be solved ahead. From the gdb backtrace below it seems to involve pango_cairo_renderer_draw_glyph. If that rings a bell to anyone I'll be glad to know what you think or provide more info where it is needed. I will also probably try to reinstall a separate macports hierarchy this week end and reinstall everything with gtk native there, to be sure the dependencies are clean. We'll see. Anyway, even if I only saw a blank window instead of Inkscape UI, I was still quite happy to see it without the X11 icon in the dock!! Cheers, Backtrace: #0 0x9003d66c in kill () #1 0x9010e8cf in raise () #2 0x9010d422 in abort () #3 0x02000356 in __eprintf () #4 0x01f9d893 in _cairo_error () #5 0x01f9d8ab in _cairo_set_error () #6 0x01dbe0f6 in pango_cairo_renderer_draw_glyphs () #7 0x01dddd4c in pango_renderer_draw_glyphs () #8 0x01dbe6e4 in _pango_cairo_do_glyph_string () #9 0x01c9bae4 in gdk_pango_renderer_draw_glyphs () #10 0x01dddd4c in pango_renderer_draw_glyphs () #11 0x01ddf09c in pango_renderer_draw_layout_line () #12 0x01ddf2b9 in pango_renderer_draw_layout () #13 0x01c9d99a in gdk_draw_layout_with_colors () #14 0x01c9dca7 in gdk_draw_layout () #15 0x01a17406 in gtk_default_draw_layout () #16 0x01a1a113 in gtk_paint_layout () #17 0x01966e1c in gtk_label_expose () #18 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #19 0x01e0a634 in g_closure_invoke () #20 0x01e1b3e3 in signal_emit_unlocked_R () #21 0x01e1c857 in g_signal_emit_valist () #22 0x01e1d177 in g_signal_emit () #23 0x01ae03c3 in gtk_widget_event_internal () #24 0x01adffdb in gtk_widget_send_expose () #25 0x018ce122 in gtk_container_propagate_expose () #26 0x018cdcaa in gtk_container_expose_child () #27 0x01a1d7fe in gtk_table_forall () #28 0x018cbab6 in gtk_container_forall () #29 0x018cddad in gtk_container_expose () #30 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #31 0x01e0a634 in g_closure_invoke () #32 0x01e1b3e3 in signal_emit_unlocked_R () #33 0x01e1c857 in g_signal_emit_valist () #34 0x01e1d177 in g_signal_emit () #35 0x01ae03c3 in gtk_widget_event_internal () #36 0x01adffdb in gtk_widget_send_expose () #37 0x018ce122 in gtk_container_propagate_expose () #38 0x018cdcaa in gtk_container_expose_child () #39 0x01880aea in gtk_box_forall () #40 0x00c26ebf in Gtk::Container_Class::forall_vfunc_callback () #41 0x018cbab6 in gtk_container_forall () #42 0x018cddad in gtk_container_expose () #43 0x00ca9502 in Gtk::Widget::on_expose_event () #44 0x00ca5e8a in Gtk::Widget_Class::expose_event_callback () #45 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #46 0x01e0a634 in g_closure_invoke () #47 0x01e1b3e3 in signal_emit_unlocked_R () #48 0x01e1c857 in g_signal_emit_valist () #49 0x01e1d177 in g_signal_emit () #50 0x01ae03c3 in gtk_widget_event_internal () #51 0x01adffdb in gtk_widget_send_expose () #52 0x018ce122 in gtk_container_propagate_expose () #53 0x018cdcaa in gtk_container_expose_child () #54 0x01880aea in gtk_box_forall () #55 0x018cbab6 in gtk_container_forall () #56 0x018cddad in gtk_container_expose () #57 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #58 0x01e0a634 in g_closure_invoke () #59 0x01e1b3e3 in signal_emit_unlocked_R () #60 0x01e1c857 in g_signal_emit_valist () #61 0x01e1d177 in g_signal_emit () #62 0x01ae03c3 in gtk_widget_event_internal () #63 0x01adffdb in gtk_widget_send_expose () #64 0x018ce122 in gtk_container_propagate_expose () #65 0x018cdcaa in gtk_container_expose_child () #66 0x01880b35 in gtk_box_forall () #67 0x018cbab6 in gtk_container_forall () #68 0x018cddad in gtk_container_expose () #69 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #70 0x01e0a634 in g_closure_invoke () #71 0x01e1b3e3 in signal_emit_unlocked_R () #72 0x01e1c857 in g_signal_emit_valist () #73 0x01e1d177 in g_signal_emit () #74 0x01ae03c3 in gtk_widget_event_internal () #75 0x01adffdb in gtk_widget_send_expose () #76 0x018ce122 in gtk_container_propagate_expose () #77 0x018cdcaa in gtk_container_expose_child () #78 0x0187c3e3 in gtk_bin_forall () #79 0x018cbab6 in gtk_container_forall () #80 0x018cddad in gtk_container_expose () #81 0x018f3a4c in gtk_event_box_expose () #82 0x0197e1ce in _gtk_marshal_BOOLEAN__BOXED () #83 0x01e0a634 in g_closure_invoke () #84 0x01e1b3e3 in signal_emit_unlocked_R () #85 0x01e1c857 in g_signal_emit_valist () #86 0x01e1d177 in g_signal_emit () #87 0x01ae03c3 in gtk_widget_event_internal () #88 0x01adffdb in gtk_widget_send_expose () #89 0x0197b424 in gtk_main_do_event () #90 0x01cbf535 in -[GdkQuartzView drawRect:] () #91 0x933123b1 in -[NSView _drawRect:clip:] () #92 0x9331140b in -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] () #93 0x9332336f in _recursiveDisplayInRect2 () #94 0x9083eb30 in CFArrayApplyFunction () #95 0x93311613 in -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] () #96 0x93310473 in -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisible RectForView:topView:] () #97 0x93311041 in -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisible RectForView:topView:] () #98 0x9330fb78 in -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisible RectForView:topView:] () #99 0x9330f362 in -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] () #100 0x9330ec8e in -[NSView displayIfNeeded] () #101 0x9330ea32 in -[NSWindow displayIfNeeded] () #102 0x9335ed6c in _handleWindowNeedsDisplay () #103 0x9082dd6e in __CFRunLoopDoObservers () #104 0x9082ce10 in CFRunLoopRunSpecific () #105 0x9082cace in CFRunLoopRunInMode () #106 0x92ded8d8 in RunCurrentEventLoopInMode () #107 0x92decf19 in ReceiveNextEventCommon () #108 0x92dece39 in BlockUntilNextEventMatchingListInMode () #109 0x93293465 in _DPSNextEvent () #110 0x93293056 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] () #111 0x01cb8a86 in gdk_event_prepare () #112 0x0223faf4 in g_main_context_prepare () #113 0x022401b6 in g_main_context_iterate () #114 0x022408cd in g_main_loop_run () #115 0x0197a9f0 in gtk_main () #116 0x00c48d02 in Gtk::Main::run () #117 0x00004451 in sp_main_gui () #118 0x00158732 in Inkscape::NSApplication::Application::run () #119 0x00003357 in main () JiHO --- http://jo.irisson.free.fr/

6 10

NEW: Dockable dialogs
by Gustav Broberg 07 Sep '07

07 Sep '07

I have now committed the patch [1],[2] I've been working on for quite some time. It gives Inkscape a dock panel right of the canvas on which dialogs can be docked. A part of an external library, GDL, has been included in the tree with this patch, this had to be done as GDL isn't widely available and the fact it demanded some Inkscape specific customizations. The good thing is that this implies that Inkscape's list of dependencies remains unchanged. The design of the dialog system allows the new dockable dialog behavior to exist along side the old floating dialogs behavior. If the old behavior is preferred, one can select it under Inkscape Preferences > Windows > Dialog behavior. Know issues ----------- * It doesn't work well with multiple open documents. Fixing it requires a bit of rewrite of the current dialog manager. I'll focus on doing this before the code freeze. * Resizing in-dock dialogs can be cumbersome. More specifically, one won't be able to expand a dialog placed in the dock unless all dialogs beneath it are expanded in advance. Fixing this requires some changes in GDL, I've got it somewhat working, but decided that it's still too flaky to commit in its current state. * Remembered positions of dockable floating dialogs is inexact. For me (using Metacity), I'm not able to get the exact position of dockable floating dialogs, the values I get are off by an unpredictable number of pixels. Could be related to the problems described here: http://www.gtk.org/api/2.6/gtk/GtkWindow.html#gtk-window-get-position * Compiler warnings. Including GDL in the tree introduced a lot of compiler warnings. They're not serious, but it looks bad... Note that this change only applies to gtkmm:ified dialogs, i.e. dialogs that subclass UI::Dialog. I've gtkmm:ified "Fill & Stroke" and with this change, that version is now default. Dialogs left to be gtkmm:ified are the "XML Editor", "Tiled Clones", "Object Properties" (though it's about to be removed/replaced IIRC), "Text and Font". The "Find" dialog has been gtkmm:ified by Johan but is disabled by default as it needs testing (please help). Now let's hope I didn't break something important... ;) 1.https://sourceforge.net/tracker/?func=detail&atid=604308&aid=1688508&grou… 2.http://www.nabble.com/-PATCH--Dockable-dialogs%2C-and-some-concerns...-tf… -- Gustav

14 33

Inkscape is a staff pick at Apple downloads
by jiho 05 Sep '07

05 Sep '07

Hello everyone, Looking for something else I just passed cross this on Apple's site: Inkscape is marked as staff pick by Apple currently. http://www.apple.com/downloads/macosx/unix_open_source/index_sp.html I don't remember that it was before so that's great news, given that the interface is X11 (which Mac users typically don't like), and not very pretty by default (which mac users usually care much about). However it seems to be a little lower in the most downloaded counts: it was in top 10 and is now 17. http://www.apple.com/downloads/macosx/unix_open_source/index_top.html But no doubt that the 0.46 release will bring all that up. Congratulations anyway. I've some GTK themes which look OK when integrated with OS X. Now if someone could tell me how to use GTK2_RC_FILES I'll be glad to try and use them in Inkscape. Cheers, JiHO --- http://jo.irisson.free.fr/

5 8

menus
by Alexandre Prokoudine 02 Sep '07

02 Sep '07

Hi, With lots of additions overal last year menus become quite busy. A couple of observations. 1. We have both "Effects - Images" and "Effects - Raster" menus. Do we keep "Images" submenu for any possible effect not altering contents of raster images or just embedding/disembedding? If it's emdedding related only, should we probably then rename submenu? btw, I'm not really sure that the current way of dealing with embedding/exporting raster files in SVG document really optimal. See, opening an arbitrary file I can't tell if an image used there is embedded or not without looking into source code.There's no indicator to tell that. An improved hint in status bar could probably be the first step in the right, IMO, direction. Something like "Embedded image A x B size in layer N" and "External image A x B size in layer N". What do you think? 2. Text case altering commands live in "Effects - Text". Should it probably belong to "Text" menu? As user of applications like Scribus or OpenOffice.org (sorry, Scribus guys :)) I don't perceive those as effects --- this is rather altering of text that its look'n'feel. Same goes for "Replace text..." --- to me it rather belongs to "Edit" or "Text" menu, not speaking about some kind of clash with "Edit - Find...". Comments? :) Alexandre

4 6

build break on 2geom change
by Jon A. Cruz 01 Sep '07

01 Sep '07

It appears that as of tonight the build is broken due to a missing dependency. The update to the 2geom code brought in a dependance on gsl. If someone could look into that and then update configure.ac with a check for the needed version, that would be helpful. Just FYI, on a Mac here I have version 1.8.

2 2

Changing layer opacity affects other layers
by microUgly 31 Aug '07

31 Aug '07

I'm creating a set of amimated cursors which involves exporting each frame from Inkscape. One of the animations involves reducing the opacity of a number of layers for each frame. I'm finding when I change the opacity of one layer then select another layer this layers opacity will also change. Quite frustrating as I've exported the frames for an animation 5 times now and each time I've found there's been a mistake with opacity on a layer :) I'm not sure if the problem is related to the amount of time Inkscape takes to redraw the image after changing opacity - I think if I select the next layer before the redraw is finished the setting is carried across. I've used blur so the redraw can be a little slow. I'm currently experiancing this in the dev build but I was having the same issue on another PC where I think I was running 0.45 -- View this message in context: http://www.nabble.com/Changing-layer-opacity-affects-other-layers-tf4339104… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

1 1