August 2008 - Inkscape Devel - Inkscape Mailman

Easier unit testing on Windows
by Jasper van de Gronde 08 Aug '08

08 Aug '08

You can now run 'buildtool check' or 'buildtool dist-all-check' to run the unit tests (or build everything and run the unit tests). The dist-cxxtests target is gone.

1 1

Re: [Inkscape-devel] Tool Options Bar accessibility ideas
by Valerie 08 Aug '08

08 Aug '08

> Of course, another option (which would be a user-toggled > option) is to use a button to make extra tool options > bars available with the other options. Click it to toggle > them on, use what you need, click to toggle > off if you need the work space. Or, click to toggle on, > toggle off automatically on mouse-exit from the toolbar > (or entry onto the canvas). Say, I think that's a splendid idea! Most tool options can be grouped into sets: Pencil tool options include: - LPE (being implemented) - line style + marker style (would be handy for many) Text tool options include: - kerning (not yet implemented, many people want it) - buttons for flow into shape or text along path + padding (non-existing either) - and perhaps toggling between "simple" style options and advanced text options So basically, there could be some visibility buttons on the side for you to toggle what you want visible and what you don't. Apart from that, there could be an option for tool options to appear on two rows instead of one if it ever gets crowded.

2 2

Spray tool discussion
by Pajarico 08 Aug '08

08 Aug '08

Hi, I've just started to write a blueprint for a Spray tool. You can find it here: http://wiki.inkscape.org/wiki/index.php/SpecSprayTool I need input on the following topics: 1) I propose that 3 parameters can be controlled (scaling, rotation and color). Every parameter has limits and a randomness to fine tune how the variation works. I need to know your thoughts about this and any nuances that might appear while coding, or on the UI... which leads me to the second question. 2) Having so many boxes and buttons on a toolbar is going to take a lot of space. I suggest to have the settings placed like in the UI example and where 'Other options...' is put another button that unrolls a window with the variations controls (check boxes for activating scaling, rotation and color variations, limits and randomness). Any other viable suggestion with the purpose of reducing clutter will be welcomed ;) 3) I've put the use 'lightness of background' as an available option but I'm not sure what should affect exactly: width? scattering? Ideally, I would like to see that every parameter (width, scattering, scaling, rotation and color) could be altered by this switch independently (I'm going to aim high ;): and also by the tablet pressure). 4) This tool uses two radiuses: outer one is the Scatter radius, it's the maximum area in which the tool has effect. Inner one is the Width radius, it's the are in which most of the items are sprayed. I made the mockup this way but now I dislike it a bit. I think is more intuitive to adjust the maximum affected area with the Width parameter, and let the Scatter radius be a % of it but going towards the center (i .e.: always Width radius>Scatter radius). Tell me what you think of this behavior. I think that's was all. Regards.

4 5

python: example in wiki
by Daniel Hornung 07 Aug '08

07 Aug '08

Hello, I hope this list is the correct one for this kind of question: Has anyone managed to get http://wiki.inkscape.org/wiki/index.php/PythonEffectTutorial to work without major changes? It failed for me both on a gentoo system and on a pretty vanilla Ubuntu 8.04 box. I don't know if I will find the time to edit the wiki page according to the current lxml behaviour, but I might give it a try. Additionally Ishmal(I think) said on irc/jabber that lxml might not be used in the future anymore anyway. Now for the list of problems I encountered: * Simply making the file executable and putting it into ~/.inkscape/extensions/ is not sufficient, it won't find inkex there, but no problem, simply add import sys sys.path.append('/usr/share/inkscape/extensions') # or another path, as appropriate for your installation to the top of it. A minor problem. * All the getElementsByTagName, getAttribute, createElement,... methods are unknown to lxml, at least in the versions here (1.3.6). Inkscape returns the python error message ending with: File "/home/dhornun/.inkscape/extensions/helloworld.py", line 32, in effect svg = self.document.getElementsByTagName('svg')[0] AttributeError: 'etree._ElementTree' object has no attribute 'getElementsByTagName' If this is not a problem on the distributions' side, those can probably be fixed by adapting the code to reflect lxml's current API. Thank you very much for any useful advice! Daniel -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/wasistshortview.php?mc=sv_ext_mf@...1921...

2 4

Re: [Inkscape-devel] Spray tool discussion (Population)
by Tony Vigil 07 Aug '08

07 Aug '08

Pajarico, Is Population the number of objects sprayed out over a specific amount of time? - Tony

3 2

NEW: Clone/original visualization
by bulia byak 07 Aug '08

07 Aug '08

When you press Shift+D to find and select the original of the selected clone, Inkscape draws a dashed line between the centers of the bounding boxes of the clone and the original. This line disappears after one second. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

5 4

GTK build error
by Andy Fitzsimon 07 Aug '08

07 Aug '08

hey guys I've just come into this. what's up with GTK ? widgets/sp-widget.cpp: In function 'GtkType sp_widget_get_type()': widgets/sp-widget.cpp:58: warning: deprecated conversion from string constant to 'gchar*' depbase=`echo widgets/sp-xmlview-attr-list.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\ g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/freetype2 -pthread -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -DPOTRACE=\"potrace\" -pthread -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairomm-1.0 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/atk-1.0 -I/usr/include/freetype2 -I/usr/include/libxml2 -I/usr/include/libpng12 -I../cxxtest -Werror=format-security -Wall -Wformat -Wformat-security -W -D_FORTIFY_SOURCE=2 -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -g -O2 -MT widgets/sp-xmlview-attr-list.o -MD -MP -MF $depbase.Tpo -c -o widgets/sp-xmlview-attr-list.o widgets/sp-xmlview-attr-list.cpp &&\ mv -f $depbase.Tpo $depbase.Po In file included from /usr/include/gtk-2.0/gtk/gtk.h:222, from /usr/include/gtk-2.0/gtk/gtksignal.h:33, from /usr/include/gtk-2.0/gtk/gtkclist.h:35, from widgets/sp-xmlview-attr-list.h:17, from widgets/sp-xmlview-attr-list.cpp:22: /usr/include/gtk-2.0/gtk/gtkctree.h:110: error: 'GtkCList' does not name a type /usr/include/gtk-2.0/gtk/gtkctree.h:127: error: 'GtkCListClass' does not name a type /usr/include/gtk-2.0/gtk/gtkctree.h:149: error: 'GtkCListRow' does not name a type /usr/include/gtk-2.0/gtk/gtkctree.h:342: error: 'GtkCellType' does not name a type make[2]: *** [widgets/sp-xmlview-attr-list.o] Error 1 make[2]: Leaving directory `/home/afitzsim/Build/inkscape/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/afitzsim/Build/inkscape' make: *** [all] Error 2 whats happening with

2 4

drag/click mode in pen tool
by Maximilian Albert 06 Aug '08

06 Aug '08

Hi, for a while I have been wondering what the 'mode' variable in SPPenContext means. It seems that it can assume the two values SP_PEN_CONTEXT_MODE_DRAG and SP_PEN_CONTEXT_MODE_CLICK. But now I discovered that its value is read from preferences-skeleton.h where it is set to _DRAG, and there doesn't seem to be any way to change that. Can anyone enlighten me what _CLICK is useful for and if it is settable at all? Thanks, Max

1 0

Re: [Inkscape-devel] [Inkscape-user] Snap to grid when pasting
by Diederik van Lierop 06 Aug '08

06 Aug '08

Vincent Hennebert wrote: > Pasting at a multiple of the grid-pitch looks like a reasonable solution > to me. It's been re-invented and committed to SVN. Please be alert for any bugs I might have introduced. Regards, Diederik

1 0

NEW: Paraxial mode in pen tool
by Maximilian Albert 06 Aug '08

06 Aug '08

Hi, apart from the recent "zigzag" mode there is now a "paraxial" mode in pen tool. In this mode, the user can only create straight line segments that are parallel to one of the coordinate axes. Normally, each line segment is drawn perpendicular to the previous one. The direction of the line segment being drawn can be toggled with Shift. When clicking on the start anchor, the path is closed with an L-shaped segment (the direction of which can also be flipped with Shift). Let me know if you have any issues with it. [1] Max [1] Known bugs: When creating the initial segment with Shift, the second segment is parallel to the first one instead of perpendicular to it (although all subsequent ones get drawn correctly). Moreover, when closing a path the final segment is sometimes drawn slightly slanted.

2 1