- Inkscape Devel - Inkscape Mailman

RFE [ 1700987 ] Window title should contain file name instead of full path
by Jon A. Cruz 18 Apr '07

18 Apr '07

What do people think of RFE [ 1700987 ] Window title should contain file name instead of full path? It seems reasonable to me, and should be fairly simple to implement. Comments? Opinions?

7 13

Plug-In or Extension System???
by Redefined Horizons 18 Apr '07

18 Apr '07

I was bugging the lib2geom folks a few months back when I had to get pulled away on another project of mine. That project has finished and I thought I'd see about helping just a little bit with Inkscape development. I have posted a message on the lib2geom Jabber conference room. I also thought I would find out if Inkscape had a plug-in or extension system just yet. If it did I thought I might take a stab at making small improvements to the program. I'm not an experienced C++ developer and I'm a little scared about trying to build Inkscape. Is there an extension or plug-in system in place? Or will I need to build Inkscape to test any changes I might make? I took a look at the road map and found these items interesting: Revisit coordinate system (move away from Cartesian) Tech Drawing Abilities DXF Import/Export Thanks for the help. I hope I can make time to tinker with Inkscape or lib2geom and improve my C++ skills as I work. Landon

5 13

Lib bundle
by Bob Jamison 17 Apr '07

17 Apr '07

Hi again, I checked the lib bundle that I uploaded last, and yes it does have the defect that Bill mentioned. So I uploaded another bundle here: http://inkscape.modevia.com/win32libs/gtk210-070417.7z It should produce Inkscape builds without the icon artifacts. There will be another build uploaded in a few minutes. bob

1 0

Re: [Inkscape-devel] LPE diff
by Johan Engelen 17 Apr '07

17 Apr '07

Hey Aaron, Thanks a lot for the links to the mail discussion. Very very helpful! I think you won't mind me throwing this on the devel maillist? >From what I gather from the discussion, no consensus was reached on the SVG representation. Perhaps it is best, like Bulia said, to first make it working the 'ugly' simple way, <path original-d= ... d = ... path-effect="sample" path-effect-param1="0.0" path-effect-param2="0.0" path-effect-param3="0.0" path-effect-param4="0.0" /> Then we can see what needs to be improved, what UI needs there are etc. Does that make sense? Once I have this working, we can discuss how to make a more versatile SVG representation. I want to make skeletal strokes first, because it also probes for on-canvas UI needs (on-canvas parameter editing). <path original-d="..." (input curve) d = "..." (result curve) path-effect="skeletal_strokes" (how are we going to name the effects?) path-effect-param1="..." (input curve) /> Cheers, Johan On Sun, 2007-04-15 at 22:13 -0500, Aaron Spike wrote: > I'm already sick of typing Live Path Effects over and over so I'm > abbreviating. :-) > > I believe we can harvest a diff of my changes on the branch with a > command like: > > svn diff > --new=https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/branches/live-effects@...1724... > --old=https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk@...1725... > > Now this takes a long time to execute and I haven't stuck it out all the > way yet. I'll try to remember to leave it running when I go to work > tomorrow. The idea is to diff the current head of the branch with the > last revision merged in from trunk. I think reading this diff will give > you a pretty good idea of what has been done so far. > > Aaron Spike

8 9

gcc 3.3 bug: configure -Wno-pointer-sign test uses wrong compiler
by jiho 17 Apr '07

17 Apr '07

Hi all, looking into compiling Inkscape on Mac OS X 10.3 an error appeared which is apparently not limited to OS X but more generally to old gcc versions (3.3 is used here). John Faith, the investigator of these issues, submitted a patch to configure.ac which fixes this. I am not knowledgeable enough with autoconf to review this. Could someone knowledgeable have a look at it and commit it or give me a go to commit this? Thank you in advance. JiHO --- http://jo.irisson.free.fr/

1 0

Accessing the user selection...
by Redefined Horizons 16 Apr '07

16 Apr '07

I have a quick question about building a tool for Inkscape. How would I access the current user selection in a document? After modifying all or part of the user selection, how would I commit my changes? I don't need the exact syntax, but perhaps someone could point me to the classes that I need to take a look at. Thanks, Scott Huey

3 2

Re: [Inkscape-devel] Win32 Nightly Build (Apr 15) Bugs
by Tony Vigil 16 Apr '07

16 Apr '07

I wasn't sure if this should be posted here or in the SF bug tracker. This seemed more appropriate to me since these nightly builds aren't considered to be stable releases. If these bug reports belong over there, please let me know. So, here's what I've got for ya... The object handles don't display properly. When the do display, they are very large rectangles that have bitmap fills. The bitmaps appear to be icons or small bits of the Inkscape gui display. I can't import images or open Inkscape documents with images. I get an error that says, "Failed to load the requested file...". It's the same for all image types (png, jpg, bmp, etc). Any ideas? - Tony

3 2

Fellow SoC'ers
by Gail Banaszkiewicz 16 Apr '07

16 Apr '07

From the official Summer of Code blog <http://googlesummerofcode.blogspot.com/2007/04/what-happens-now.html>: > Encourage them [the students] to talk amongst themselves to build > camaraderie and mutual inspiration. So? Where's everyone from? I only spoke to a couple of people and realized their posts were coming from SoC applicants. For those that don't know me yet, you can find out more on my web page (gasp! Making you work!): http://www.scs.carleton.ca/~gbanaszk/ Looking forward to getting to know you, Gail

4 5

Minimum GTK+ and GTKmm versions
by Jon A. Cruz 16 Apr '07

16 Apr '07

What are our minimum versions currently? Our requirements say gdkmm-2.4 glibmm-2.4 gtkmm-2.4 gtk+-2.0 >= 2.8.0 First I was thinking that the *mm ones should match the GTK+ requirement. Second, I was wondering when we're moving up past 2.8.x?

3 3

Re: [Inkscape-devel] Escaping $ in commandline parameters
by Kees Cook 15 Apr '07

15 Apr '07

Ted wrote: > Kees, is there some way to validate a command line to make sure you're > not causing any security holes by calling shell variables that you don't > mean to? It seems like there should be something generic out there. Sorry, I'm way busy. From the looks of it, glib provides g_shell_quote(), which should be used in a per-argument fasion. e.g. if the extension is running: PROGRAM ARG1 ARG2 SVGPATH via something like: sprintf("%s %s %s %s", program, arg1, arg1, path); Then each element should be quoted: prog_q = g_shell_quote(program); arg1_q = g_shell_quote(arg1); arg2_q = g_shell_quote(arg2); path_q = g_shell_quote(path); sprintf("%s %s %s %s", prog_q, arg1_q, arg2_q, path_q); g_free(prog_q); g_free(arg1_q); g_free(arg2_q); g_free(path_q); However, I much more recommend using arrays for doing execution, since that forces the right arguments and stops any kind of shell expansion. -- Kees Cook @outflux.net

2 5

Re: [Inkscape-devel] NEW: Engraver's Toolbox
by Tom Lechner 15 Apr '07

15 Apr '07

Hi, The new engraver's tool is quite neat! Now what is needed is an engraver's bucket fill by somehow defining a sort of fluid flow direction field to say which direction lines will be laid down, and perhaps then adjust line thickness and/or spacing based on color variations beneath, in order to facilitate making drawings of this (my) sort of style: http://tomlechner.com/cartoons/weakdaze/img-daze-gray0003.html http://tomlechner.com/consumption/cons12/img-messingwiththelights.html Though, I'd probably still use pens and paper since I love drawing so much. But it would make engraved animation much easier! For a really long time, I've wanted to animate something like a Durer print. Tom

2 1

New: grid stuff
by unknown＠example.com 15 Apr '07

15 Apr '07

Hi all, Today I removed all 'old' grid code, and fully enabled the new grid stuff. >From a user perspective this means: ** a new tab in the document properties dialog, solely meant for grids; the former grid/guide tab is now solely for guides. I envision a list of guides there in the future, for easier deletion of guides etc. ** more than one grid can be active at the same time, although i am having trouble in finding a usefull case for this ** multiple views on the same document share the same grids, but the grid can be turned off for each view separately. For example: one could have an overview view without grid enabled. Duplicate that window and zoom in on some detail; then grids can be shown only for that view, and snapping will only happen in those views for which grids are enabled. (sorry i am not able to explain more clearly) ** grid information is now stored in SVG as a child of sodipodi:namedview. Can someone please make an extension that converts an old grid definition to the new format? >From developer perspective: ** implementation of new grids is much easier now; subclassing CanvasGrid and adding an entry in the is enough. Have a peek at how the rectangular grid is implemented (CanvasXYGrid). ** note that there is no longer "the grid", there might be several grids active now! Future plans (i will not be working on this soon, due to GSoC Live effects!): ** possibility of enabling not all but a selection of grids for a view. Eg. when there are 4 grids defined in the document, only enable grid2 for a certain view. ** new grids! ** better snapping mechanism to enable snapping to intersections of guides&grids and grids&grids. A side effect of removal of old gridcode: apparantly the origin of the desktop rules used to be set to the origin of the grid. I find this strange: specifying a grid origin of (2,2) would have me think the origin would be at ruler location (2,2) instead of (0,0) as it is in 0.45.1. I have commented the grid-origin correction to the ruler range, because now there is not a single grid anymore to correct it for. Isn't there a control somewhere to define the documents origin? Now the ruler origin is set to (0,0) Cheers, Johan

2 1

NEW: Engraver's Toolbox
by bulia byak 15 Apr '07

15 Apr '07

Several new features were added to the Calligraphic pen to make Inkscape capable of the ancient art of '''line engraving'''. Traditional engraving is a very labour-intensive process, and while for a long time it was the only practical way of reproducing lifelike images in black-and-white print, about a century ago it was almost completely displaced by automatic halftone screens. However, line engravings have their characteristic charm, and there's no reason not to try to resurrect this art form with the help of Inkscape. A brief visual guide to the new functionality can be seen on these screenshots: http://inkscape.org/screenshots/gallery/inkscape-0.46-engraving1.png http://inkscape.org/screenshots/gallery/inkscape-0.46-engraving2.png 1. Tracking a guide path with Ctrl One of the most common operations in line engraving is '''hatching''' (or sometimes ''cross-hatching'' when several hatching grids cross): filling a space with many parallel straight or variously curved lines (usually of varying width to represent a gradual shading). You could try to achieve a similar effect with e.g. path interpolation (blending), but it is rather cumbersome and limited; manual drawing of hatch lines, on the other hand, is tedious and nearly impossible to do uniformly. Now Inkscape provides "assisted hatching" by '''tracking a guide path''', allowing you to hatch quickly and uniformly and at the same time giving you sufficient manual control over the process. Here's how to do this. First, select the '''guide path''' that you will track. It may be another calligraphic stroke, any path or shape, or even a letter of a text object. Then switch to Calligraphic pen, select the desired parameters (line width, angle, fixation etc.) and, before starting to draw, press Ctrl. You will see a gray '''track circle''' centered at your mouse pointer and touching the closest point on the selected guide path. (If you have no guide path selected, a statusbar message will tell you to select it). Now move your mouse close to the guide path, so that the track circle radius is equal to the desired spacing of your hatch pattern, and start drawing along the guide path. At that moment, the radius of the circle gets locked; now the circle slides along the guide path - and the actual stroke is drawn by the center of the tracking circle, '''not'' by your mouse point. As a result, you are getting a smooth stroke going parallel to the guide path and always at the same distance from it. When the stroke is ready, release your mouse button (or lift your tablet pen) but '''do not let go of the Ctrl key''' because as long as you have it pressed, the tool remembers the hatch spacing you set when you started drawing. Now, you have just created a new stroke and, as usual with Inkscape tools, it gets selected instead of what was selected before. In our case, this means that the newly drawn stroke itself becomes the new guide path. Next, you can draw a second stroke along the first one, then a third one along the second, etc. Eventually you can fill any desired space with uniform hatching. The attachment to the guide path is not absolute. If you stray your mouse pointer far enough from the guide path, you will be able to tear it off (the track circle turns from green to red) and move freely. This is intentional; this feature allows you, for example, to continue drawing a stroke past the end of a guide stroke, thus making your hatching cover a wider area than the initial guide path. Special care is taken to make such tearing off as smooth as possible and to suppress violent jerks, but this is not always possible; the general advice is to not try to hatch too fast. If jerking and unintended tearoffs still bother you, try increasing the Mass parameter. Also, special code is in place to prevent flipovers - accidental jumps to the other side of the guide path. Brief flipovers are suppressed, but if you intentionally go over to the other side and stay there, eventually Inkscape will obey and your tracked stroke will also flip over to follow you. Tracking a guide also allows some slight feedback by gradually changing the tracking distance in response to your drawing behavior. Thus, if you're consistently trying to draw closer or farther from the guide than the current tracking distance, the distance will correspondingly decrease or increase, so you will get a hatching that is slightly spacing in or out. (The effect is very slight, however, so as not to become a nuisance.) Also, note that since tracking follows the edge of the stroke, strokes of varying width (such as those tracing background, see below) will result in gradual change of the hatching shape as you proceed. 2. Tracing background by stroke width There is a new toggle button on the Calligraphy tool's controls bar, '''Trace background'''. When on, the width of your pen depends on the lightness of the background under the stroke in each point, so that white translates into the minimum stoke width (1) and black translates to the maximum (which set by the Width parameter). This can work alone or in combination with pressure sensitivity, depending on whether the Pressure button is also toggled. This feature allows you to not only hatch over an imported bitmap image or any drawing, but to do so automatically reproducing the highlights and shades of the background with your strokes becoming lighter and heavier as needed. 3. Thinning/thickening of paths with Alt Even with background tracing, the visible lightness/darkness of a hatching may not correspond too well to your artistic intention. Also, with guide tracking, the ends of strokes are often far from ideal - they may be too blunt or have unsightly bends or blobs. This is where the new thinning/thickening function is indispensable. While in the Calligraphy tool, press Alt. You will see a orange-colored circle indicating the area that will be affected; this area is 10 times the size of the pen when you draw (so you can change it by changing the Width parameter on the toolbar). Now select some or all of the paths (as with most tools in Inkscape, only selected objects are changed), for example by pressing Ctrl+A, and start '''Alt+dragging''' over the paths. Where you touch them, paths become thinner, as if melting away, up until total disappearance. Conversely, '''Shift+Alt+dragging''' makes selected paths thicker in places where you touch them. As with the Calligraphy pen itself, the '''size''' of the thinning/thickening area by default depends on zoom; simply zooming in or out is often easier than adjusting the width if you want to cover a smaller or larger area. The '''force''' of the effect also depends on zoom (or in other words, it stays the same when measured by screen pixels, same as when you move and object by Alt+arrow keys). Also, if you have a pressure-sensitive tablet, the force of thinning/thickening also depends on '''pen pressure'''; tapping slightly produces gradual lightening or darkening of your drawing, while pressing heavily will work as a kind of quick "erasing" (with Alt) or "blackening" (with Alt+Shift). Of course, thinning/thickening is very useful '''not only for calligraphic strokes'''. You can select any simple path (such as an ellipse converted to path) and start '''sculpting''' it, spawning smooth treacle-like appendages with Alt+Shift and melting them away with Alt. Unlike the "node sculpting" mode in the Node tool, however, this does not require adding new nodes to the shape or selecting any nodes. This new functionality is somewhat similar to the "Pucker" and "Bloat" tools in the latest versions of Adobe Illustrator, except that in Inkscape it works softer and is easier to control. '''Known problems with thinning/thickening:''' (1) it is rather slow; (2) it quickly eats memory; and (3) it is sometimes buggy - thin calligraphic strokes may suddenly disappear or change their shape drastically as you're Alt+stroking them. For (3), it helps to undo the bad change and try again with less pressure on the pen - if you do your thinning in several light touches instead of one heavy press, usually you will be able to get the desired result without the buggy behavior. In general, however, all these problems stem from the livarot library that we use for geometric manipulation of paths. Fortunately, livarot is scheduled for replacement by lib2geom, a new library now in development, so hopefully these issues will be addressed then. 4. Misc features * For consistency with other drawing tools, drawing with '''Shift''' in Calligraphy tool automatically '''unions''' the newly created stroke with whatever paths were selected (and selects the result). Thus, you can do a series of overlapping Shift+strokes to create one unioned path object instead of separate objects as before. * To facilitate changing the Width parameter, the Home/End keys in Calligraphy tool switch you to the minimum (1) and maximum (100) width, correspondingly. (This is in addition to the Left/Right arrow keys that change Width by 1; remember also that you can press Alt+X, type any width, and press Enter.) -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

14 22

Req.: Clip and mask editing
by Pierre-Luc Auclair 15 Apr '07

15 Apr '07

It would be very much useful if we could access masks and clipping paths without releasing them, cause right now it's a mess, especially when you start doing mask of mask of clip + mask. Would have posted this on the tracker but I wanted people to discuss how you'd want this implemented. Made a mockup here: http://heliosmulti.com/inkscape-clip-mask-access.png Pierre-Luc

3 2

I can't compile SVN
by Tobias Jakobs 15 Apr '07

15 Apr '07

Hi, I can't compile SVN. I have this errors: $ make make all-recursive make[1]: Entering directory `/home/tobias/cvs/inkscape' Making all in src make[2]: Entering directory `/home/tobias/cvs/inkscape/src' if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/lib/perl/5.8/CORE -I/usr/include/python2.5 -I/usr/include/freetype2 -pthread -DORBIT2=1 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DRELAYTOOL_CRYPTO='static const int libcrypto_is_present = 1; static int __attribute__((unused)) libcrypto_symbol_is_present(char *m) { return 1; }' -DRELAYTOOL_SSL='static const int libssl_is_present = 1; static int __attribute__((unused)) libssl_symbol_is_present(char *m) { return 1; }' -DHAVE_SSL -I/usr/include/freetype2 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/gtk-2.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -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/freetype2 -I/usr/include/libpng12 -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/libxml2 -I../cxxtest -Wall -Wformat-security -W -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -D_FORTIFY_SOURCE=2 -Wno-unused-parameter -g -O2 -MT extension/script/inkscape_py_wrap.o -MD -MP -MF "extension/script/.deps/inkscape_py_wrap.Tpo" \ -c -o extension/script/inkscape_py_wrap.o `test -f 'extension/script/inkscape_py_wrap.cpp' || echo './'`extension/script/inkscape_py_wrap.cpp; \ then mv -f "extension/script/.deps/inkscape_py_wrap.Tpo" "extension/script/.deps/inkscape_py_wrap.Po"; \ else rm -f "extension/script/.deps/inkscape_py_wrap.Tpo"; exit 1; \ fi extension/script/inkscape_py_wrap.cpp: In function 'int SWIG_Python_ConvertPtr(PyObject*, void**, swig_type_info*, int)': extension/script/inkscape_py_wrap.cpp:795: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp:805: error: invalid conversion from 'const char*' to 'char*' extension/script/inkscape_py_wrap.cpp: In function 'PyObject* SWIG_Python_NewPointerObj(void*, swig_type_info*, int)': extension/script/inkscape_py_wrap.cpp:910: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp: In function 'void SWIG_Python_FixMethods(PyMethodDef*, swig_const_info*, swig_type_info**, swig_type_info**)': extension/script/inkscape_py_wrap.cpp:980: error: invalid conversion from 'const char*' to 'char*' extension/script/inkscape_py_wrap.cpp: In function 'PyObject* _wrap_delete_Inkscape(PyObject*, PyObject*)': extension/script/inkscape_py_wrap.cpp:1123: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp: In function 'PyObject* _wrap_Inkscape_getDesktop(PyObject*, PyObject*)': extension/script/inkscape_py_wrap.cpp:1141: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp: In function 'PyObject* _wrap_Inkscape_getDialogManager(PyObject*, PyObject*)': extension/script/inkscape_py_wrap.cpp:1159: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp: In function 'PyObject* _wrap_delete_DialogManager(PyObject*, PyObject*)': extension/script/inkscape_py_wrap.cpp:1183: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp: In function 'PyObject* _wrap_DialogManager_showAbout(PyObject*, PyObject*)': extension/script/inkscape_py_wrap.cpp:1200: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp: In function 'PyObject* _wrap_delete_Desktop(PyObject*, PyObject*)': extension/script/inkscape_py_wrap.cpp:1224: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp: In function 'PyObject* _wrap_Desktop_getDocument(PyObject*, PyObject*)': extension/script/inkscape_py_wrap.cpp:1242: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp: In function 'PyObject* _wrap_delete_Document(PyObject*, PyObject*)': extension/script/inkscape_py_wrap.cpp:1266: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp: In function 'PyObject* _wrap_Document_hello(PyObject*, PyObject*)': extension/script/inkscape_py_wrap.cpp:1283: warning: dereferencing type-punned pointer will break strict-aliasing rules extension/script/inkscape_py_wrap.cpp: At global scope: extension/script/inkscape_py_wrap.cpp:233: warning: 'swig_type_info* SWIG_TypeDynamicCast(swig_type_info*, void**)' defined but not used extension/script/inkscape_py_wrap.cpp:271: warning: 'swig_type_info* SWIG_TypeQuery(const char*)' defined but not used extension/script/inkscape_py_wrap.cpp:346: warning: 'void SWIG_PropagateClientData(swig_type_info*)' defined but not used extension/script/inkscape_py_wrap.cpp:619: warning: 'void SWIG_Python_addvarlink(PyObject*, char*, PyObject* (*)(), int (*)(PyObject*))' defined but not used extension/script/inkscape_py_wrap.cpp:829: warning: 'void* SWIG_Python_MustGetPtr(PyObject*, swig_type_info*, int, int)' defined but not used extension/script/inkscape_py_wrap.cpp:843: warning: 'int SWIG_Python_ConvertPacked(PyObject*, void*, size_t, swig_type_info*, int)' defined but not used make[2]: *** [extension/script/inkscape_py_wrap.o] Error 1 make[2]: Leaving directory `/home/tobias/cvs/inkscape/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/tobias/cvs/inkscape' make: *** [all] Error 2

2 6

Re: [Inkscape-devel] Req.: Clip and mask editing
by Juan Miguel Ramirez 15 Apr '07

15 Apr '07

I think we need the option to edit the clipped (or masked) object on live. For example I think the clip for a specific graphic is the correct but later I want to change the dimensions on this graphics but not the clip (or the mask) itself. Right now, I have to release, made the changes and clip(or mask) again. Maybe I have to do it 3 times to obtain the right results or even more times. I think the best way is to have an option to edit the clipped(or masked) object/graphic without to release it and clipped(or masked) again. I know that, for example, Freehand has got a similar option when you use "paste inside"(is similar to clip) and you can modify the "inside" graphic or object.

2 1

NEW: touch selection
by bulia byak 13 Apr '07

13 Apr '07

In Selector tool, a new object selection mode is available: selecting by touch. In this mode, you draw a freehand path across the objects; when you release mouse button, all objects that are touched by this path get selected. This mode is very convenient in situations where you need to select objects so intermingled that selecting them by the rectangular rubberband is too difficult and so numerous that click-selecting them one by one is too tedious. To activate selecting by touch, whenever you are drawing a rubberband rectangle, just press Alt to switch it to the touch mode. The rectangle will disappear and a red touch path will be shown instead. When dragging from an empty space, you can press Alt first and then start to drag to get the touch mode (note that your selection must be empty, otherwise Alt+dragging will move the selected objects instead). To start a touch selection from a point over an object, or to add to existing selection by touching, press Shift+Alt and then start to drag. Comments: I'm not too fond of the name "touch selection"; naming suggestions are welcome. Note however that this is not a "lasso" because you don't need to enclose objects, just touch them; and it is not "magic wand" because it does not try to select similar-styled objects. Some Adobe Illustrator users have requested a support for an AI-like selection mode where any object _touched_ by the selection rectangle is selected. Inkscape's new touch selection mode should satisfy them - it is a superset of AI's functionality because a touch path can be arbitrary and not only a box. Note, however, that AI gets this exactly backwards: in it, a rectangle selection selects by touching, whereas a freehand "lasso tool" needs to enclose objects to select them (although its definition of "enclosing" is rather strange - I was able to get very difficult to explain results with that tool). -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

8 7

Snapping bbox or nodes
by unknown＠example.com 13 Apr '07

13 Apr '07

The options "snap to bbox" and "snap to nodes" have been removed, but now I find gridsnapping to be very very difficult. For my drawings I always use snap to nodes, with snap to bbox turned off. Now it snaps to both, which is imho extremely inconvenient. For example, it means that you can never be sure to which point a rectangle has snapped (bbox snapping and node snapping is often a 1/100 pixel difference); so for each rectangle I draw I have to zoom in to check whether it snapped according to what I want (nodes) :( Can we please have these options back? Thanks! Johan

2 1

Google Summer of Code projects for Inkscape
by Bryce Harrington 13 Apr '07

13 Apr '07

Google has just announced the project's for this year's summer of code: http://code.google.com/soc/inkscape/about.html Text Improvements by Gail Banaszkiewicz, mentored by Richard Hughes Native PDF import capability based on libpoppler by Miklos Erdelyi, mentored by Jon Cruz Live path effects in Inkscape by Johan Engelen, mentored by Aaron Spike 3D box tool for Inkscape by Maximilian Albert, mentored by bulia byak UI for SVG Filter Effects by Nicholas Bishop, mentored by MenTaLguY Raster Functionality in Inkscape by Christopher Brown, mentored by Theodore J. Gould Importing from, and Exporting to, a remote ccHost instance by Bruno Lu Gon-alves Dilly, mentored by Bryce Harrington Since the full text of the applications don't seem to be made public by google, could each of you post your proposal either to Inkscape's wiki or your own website, add a link to it from the Inkscape Summer of code wiki page, and report it here? I'm sure everyone is curious. :-) Thank you to all the students who applied, and congratulations to those whose applications were selected. We will all look forward to working with you over the summer! Bryce

8 10

Re: [Inkscape-devel] Google Summer of Code projects for Inkscape
by Gail Banaszkiewicz 12 Apr '07

12 Apr '07

Wow, seven projects! I'm very happy to hear that you guys got so many! Congrats on that end! I'm really excited to work with you all and hopefully I will meet some of you at LGM (I'm officially signed up!). My application can be found on my portfolio web site: http://www.scs.carleton.ca/~gbanaszk/code/soc07/index.htm I can add this link to the Wiki, but I wanted to see how you guys wanted to do it this year. Should we keep the current list of "ideas" intact and start a separate section for accepted applications, or would you rather just add our names and links to the idea we applied for? Gail Bryce Harrington wrote: > Google has just announced the project's for this year's summer of code: > > http://code.google.com/soc/inkscape/about.html > > Text Improvements > by Gail Banaszkiewicz, mentored by Richard Hughes > > Native PDF import capability based on libpoppler > by Miklos Erdelyi, mentored by Jon Cruz > > Live path effects in Inkscape > by Johan Engelen, mentored by Aaron Spike > > 3D box tool for Inkscape > by Maximilian Albert, mentored by bulia byak > > UI for SVG Filter Effects > by Nicholas Bishop, mentored by MenTaLguY > > Raster Functionality in Inkscape > by Christopher Brown, mentored by Theodore J. Gould > > Importing from, and Exporting to, a remote ccHost instance > by Bruno Lu Gon-alves Dilly, mentored by Bryce Harrington > > Since the full text of the applications don't seem to be made public by > google, could each of you post your proposal either to Inkscape's wiki > or your own website, add a link to it from the Inkscape Summer of code > wiki page, and report it here? I'm sure everyone is curious. :-) > > Thank you to all the students who applied, and congratulations to those > whose applications were selected. We will all look forward to working > with you over the summer! > > Bryce

2 1

Re: [Inkscape-devel] [Inkscape-user] NEW: touch selection
by Jon Phillips 12 Apr '07

12 Apr '07

Agree, it sounds cool and is mega useful. Jon -----Original Message----- From: "kaver" <kaver@...68...> To: "bulia byak" <buliabyak@...400...>; "inkscape-devel" <inkscape-devel@...1721...sts.sourceforge.net>; "Inkscape User Community" <inkscape-user@...1722...forge.net> Sent: 4/12/2007 9:58 AM Subject: Re: [Inkscape-user] [Inkscape-devel] NEW: touch selection I am happy with touch selection. It describes what it does and has already been used half a dozen times :-) Erik Erik Halbert kaver@...68... ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Inkscape-user mailing list Inkscape-user(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user

1 0

Re: [Inkscape-devel] [Inkscape-user] NEW: touch selection
by jiho 12 Apr '07

12 Apr '07

On 2007-April-12 , at 10:39 , Bill Baxter wrote: > On 4/12/07, bulia byak <buliabyak@...400...> wrote: >> In Selector tool, a new object selection mode is available: selecting >> by touch. In this mode, you draw a freehand path across the objects; >> when you release mouse button, all objects that are touched by this >> path get selected. This mode is very convenient in situations where >> you need to select objects so intermingled that selecting them by the >> rectangular rubberband is too difficult and so numerous that >> click-selecting them one by one is too tedious. >> > [...] > Other possible names would be : > * contact selection > [...] This one seems to correctly represent the behavior for me. While you are at it, I just entered a bug report on the selector tool ;-) https://sourceforge.net/tracker/? func=detail&atid=604306&aid=1699065&group_id=93438 Thank you very much. JiHO --- http://jo.irisson.free.fr/

1 0

Libre Graphics Meeting Sign up Available
by Plinnell 12 Apr '07

12 Apr '07

Hi, We have the sign up module now active for the LGM2 in Montreal. http://www.libregraphicsmeeting.org/signup If you are planning to attend please do register at the earliest opportunity so we can plan according to the numbers we receive. Look forward to seeing you in Montreal. Cheers, Peter

1 0

Pedro/Whiteboard
by Joshua A. Andler 11 Apr '07

11 Apr '07

I was just going to connect a private whiteboard session to myself to record a drawing and decided to check out the About screen for Pedro. I don't know if Pedro is 1.0 or not, but the About dialog for Pedro pops up with the title "About inkscape" and in big bold text says "inkscape 1.0". I figured I'd bring this up since it should probably get corrected to be more clear, but since it's Bob's pet project I didn't want to mess with it. I'd think that the title being changed to "About Pedro" or something like that would help. Plus it saying Pedro XMPP Client 1.0 (or whatever) instead of Inkscape 1.0 would also clear things up. Just my observation. -Josh

2 1

Booking your room for LGM 2007 - UPDATE
by Louis Desjardins 10 Apr '07

10 Apr '07

Hello all, Due to the demand for cosier bedrooms that would include a private bathroom, and since there are no more Cosy Suites left in the Studio Hôtel (student residences), we have posted new info on the Create wiki under the Hotel section. Please review. We let it up to you to find out where you want to stay during LGM and we're making every effort to make you happy! http://create.freedesktop.org/wiki/index.php/Conference#HOTELS In short: • There are lots of single rooms at CAD $46 taxes included in the Studio Hôtel. • There are no more Cosy suites at Studio Hôtel. • There are about 15-20 available rooms with a private bathroom at Terrasse Royale for CAD $99 plus taxes (around 113$ taxes included). Don't forget to mention the name of the event when you make your online reservation to ensure you get the special price of $99. • Studio Hôtel is located on the campus, 5 minutes walk from LGM • Terrasse Royale is located nearby the campus, 10-12 minutes walk from LGM Please make sure you have made your reservation. Cheers, Louis -- Louis Desjardins Organisateur / Organiser Libre Graphics Meeting 2007 - Montréal www.libregraphicsmeeting.org/fr www.libregraphicsmeeting.org +1 514 934 1353 HAE / EDT GMT -4

2 1