- Inkscape Devel - Inkscape Mailman

devlibs update?
by Nicolas Dufour 29 Jan '12

29 Jan '12

Hi, Apparently the latest GTK version (2.24.8) fixes lots of Windows issues, including tablet support (details on http://mail.gnome.org/archives/gtk-devel-list/2011-November/msg00026.html). Just tested with a local modified version of Inkscape, based on revision 10922, and I can confirm at least a bug and a regression (#786667 "Color drag and drop broken" and #707255 "Layer dialog - symbols disappear when mouse hover over") are gone. More tests planned later with a Wacom Bamboo tablet. BTW, the current devlibs introduced a regression in the trunk and 0.48.2 version (see #173116 Gtk::PixbufError exception not caught in Windows), and need to be recompiled to to prevent Inkscape from crashing on Windows when opening an invalid image. Krzysztof, would you be willing to update and recompile the devlibs so that more users can test before we release 0.48.3? Regards, -- Nicolas

2 1

Re: [Inkscape-devel] Powerstroke requests
by Valerie 25 Jan '12

25 Jan '12

Awesome! Some feedback of my own: 1) So powerstroke is now available from the shapes drop-down: Very neat! Can the "eclipse" form also be replaced by a powerstroke? It's actually the most common usage scenario. Also, I recommend adding a separation line between the powerstrokes and "from clipboard", to show that they are different functions. 2) Cusp styles are currently either Beveled or Rounded. How complicated is the coding for an "Angled" option? For font designers in particular, thick powerstrokes using successions of angled segments render a bit strangely, when some may be hoping for sharp edges (Example: the letter A with a sharp top) (I thought I suggested this before, but the mail never seems to have reached the mail archive...) 3) Does anybody think he might need an "assymetric" option? 4) +1 on the "Filled Powerstroke" (or whatever it will be called) option in the drop down. As for manually setting the width value for powerstroke points, I suggest click-enter for a numerical box to appear near the point, for the user to input the value. ------------------------------ Message: 6 Date: Tue, 24 Jan 2012 05:57:42 -0800 (PST) From: Defiant00 <defiant00@...400...> Subject: Re: [Inkscape-devel] Powerstroke requests To: inkscape-devel(a)lists.sourceforge.net Message-ID: <1327413462235-4335274.post@...2730...> Content-Type: text/plain; charset=us-ascii Hello again, here's some further feedback: 1) A way to directly set width values for Powerstroke points (or at least a command that sets the value to zero without having to directly edit the XML) would be useful. 2) I noticed the 'Triangle in' and 'Triangle out' shapes now use Powerstroke. Is there any chance we could get an extra shape option added to that drop down that produces both a Powerstroke and the clone original LPE at the same time. 3) Adding and removing Powerstroke control points should not require switching to another control and back to have them show up properly. 4) The 'Smoothness' control cannot be dragged (at least on Windows 7). Instead, it changes values by 0.01-0.03 (appears to be random) and then loses focus. Regards, Aaron

4 5

Re: [Inkscape-devel] Powerstroke requests
by Valerie 25 Jan '12

25 Jan '12

Glad to hear that "Angled" cusp style is the highest priority right now! It's probably the biggest thing missing functionality-wise. I'm not surprised that it'd take some time to code though. By the way, the interpolator type I tested most right now is "CubicBezierJohan", yes. Currently it seems to be the algorithm with the most predictable results. CubicBezierFit and SpiroInterpolator do seem to produce some interesting results though, I'm still trying to figure out use cases.

1 0

Merging Export and Create bitmap
by Ivan Louette 25 Jan '12

25 Jan '12

Hello As I wasn't able to add a mockup png image to the following blueprint I join it to this message. https://blueprints.launchpad.net/inkscape/+spec/merging-export-and-create-b… ivan

8 21

IRC meeting, anyone interested?
by Josh Andler 24 Jan '12

24 Jan '12

Hey All, Who would be interested in a good old fashioned IRC meeting to discuss various things about the project? It seems like other projects seem to be able to pull them together (on a regular basis no less), so why not us? I would especially like if we could get the likes of Krzysztof, Johan, Tavmjong, Jasper, Jon, Alex, Kris, and anyone else who would be interested. This especially goes for anyone who lurks on the devel list who is interested in contributing but still hasn't introduced themselves yet (they're always around). ;) I think it would be good to get people together to help us help each other. I think one of the things we should remember is that sometimes reviewing others work or just answering questions, can be more valuable than actually writing code yourself. I'm not asking for a huge time commitment or anything. If you are interested please chime in with any preferred dates or times so we can coordinate based on global distribution of participants. I'll throw out the 18th as a possible date... mainly because it's not terribly likely that this will happen and the 18th is my birthday so that's my wish. :P Cheers, Josh

8 15

Powerstroke requests
by Johan Engelen 24 Jan '12

24 Jan '12

Hi all, I don't know what to work on anymore... Please help me out by test driving the Powerstroke LPE and tell me what you dislike and what you'd like to be added. (I already know you want it to work with tablets, I am waiting for my tablet to arrive...) Ciao, Johan

5 18

New version of mesh branch.
by Tavmjong Bah 24 Jan '12

24 Jan '12

Hi, I just checked in a new version of my mesh branch. There was some major restructuring to use a simple array of nodes for the internal representation rather than the complicated side and corner classes I had before. This was motivated by adding support for tensor meshes which naturally calls for an array. Tensor meshes were added as an experiment to see if they would help in smoothing color transitions across patch boundaries (they don't seem to help very much) and are not envisioned to be part of the SVG specification for meshes. New/newish features: Corner operations: Ctrl-B: Toggle selected patch sides between linear and curve. (Select both corner nodes of side to select side.) Ctrl-C: Attempt to convert selected sides into elliptical arcs by changing the length of the Bezier handles. Ctrl-G: Toggle on/off tensor points for selected patches. (Select all four corner nodes of a patch to select patch.) Ctrl-J: Attempt to smooth color transition around a corner by changing length of Bezier handles. This needs lots of work to make it truly useful. Ctrl-K: Sample colors underneath mesh at corner nodes. For nodes at edge of mesh, move sample point inside mesh. Older features: 1. Create a simple one patch square mesh the size of an objects bounding box. (Select the third button on the Gradient Tool-Tool Bar and then click-drag on object. You won't see a change as the default mesh has all four corner colors set to the former object color. Click on object again to see mesh handles.) 2. Drag corner nodes (diamonds). 3. Change color of corner nodes. 4. Drag handles (circles). There is no indication of what handle belongs with which corner node or path so it can be confusing. And all handles are shown. (Should be able to toggle on/off handle visibility.) 5. Divide a row or column of patches into two rows or columns. (Double click on the lines connecting corner nodes. Double clicking elsewhere may lead to a crash.) The row/column will be split at the place you click. 6. Save the mesh. The mesh is saved in the proposed SVG standard format (likely to change). 7. Read in saved meshes. Bugs: * Frequent crashes. * Changing node color isn't saved until a node is moved. * Linear patch sides are shown as non-linear when corner node moved. * Selected nodes become unselected when any of the corner operations are done. * etc. Note, a trunk version of the Cairo rendering library is needed. My branch can be found at: https://code.launchpad.net/~tavmjong-free/inkscape/mesh Tav

5 11

Wacom inkling files
by Gaetano Lo Nigro 22 Jan '12

22 Jan '12

Good morning guys, I asked few files to a guy who bought, the new Wacom-inkling just in case if somebody want have a look on them. The Wacom website reports the possibility to record layers, for instance, to separate preparatory and final drawings. These layers are then retained after import. It creates native bitmap or vector versions of your sketches for Adobe Photoshop, Adobe Illustrator or Autodesk Sketchbook. With a simple click you can directly transfer your sketches into your preferred software. These imported versions retain the layers and line weights of your original sketches. Additionally, you can save all sketches in the native Inkling format or as single layer files in other popular image formats such as JPEG, PNG, PDF or SVG. You can find more details here with a full review from the owner`s sketch http://www.inkscapeforum.com/viewtopic.php?f=30&t=11278 You ll fin attached on the forum a svg file in three layers, pdf, ai, and wac directly Have a nice day

1 0

SpCursor
by Kris De Gussem 21 Jan '12

21 Jan '12

Hi all Is there a reason why the parameters named xpm of the functions in src/sp-cursor.cpp are refering to gchars and not guchars? As a result a signed char is used as index for colorMap from line 153 on and AFAIK using signed chars to index is risky business Regards K

1 0

Launchpad bug mail improvements
by Johan Engelen 20 Jan '12

20 Jan '12

Hi all, Have a look at this post: http://blog.launchpad.net/cool-new-stuff/better-bug-subscriptions Now, you can unsubscribe from the mails you get from your Inkscape Bug Team membership. In addition, you can add your own individual subscription with filtering on Launchpad's side (instead of in your mail client). Great work! Johan

1 0

Re: [Inkscape-devel] Writing an extension
by Trever L. Adams 19 Jan '12

19 Jan '12

> Date: Mon, 16 Jan 2012 10:24:00 +0100 > From: Jasper van de Gronde <th.v.d.gronde@...528...> > Subject: Re: [Inkscape-devel] Writing an extension > To: inkscape-devel(a)lists.sourceforge.net > > On 13-01-12 19:10, Trever L. Adams wrote: > > This relates to https://bugs.launchpad.net/inkscape/+bug/247463 and > > comment 37 in particular. > > > > I would like to be able to attach information to objects that are needed > > for high quality digitization. This includes stitch length and stitch > > direction. I am thinking of displaying the direction as gradient, > > although direction may be very complex. I am just learning about SVG so, > > I do not know if there are smart ways of doing this. (For example, think > > of a leaf, where you may have 20 different direction changes.) I also do > > not know XML very well (creating schema, etc). > So basically you want to embed information needed to convert a drawing > to something that can be embroidered? And you want this information to > be visible and manipulable in Inkscape's interface? Yes, I am starting from information I have found here: http://jumpnslide.tumblr.com/post/2557920924/how-to-use-inkscape-as-a-game-… I am missing just a few pieces of information: 1) How do I set values in the interface (fetch them from the SVG)? I have defaults working, etc. 2) How do I insert my custom attributes back into the SVG? The following partial code block doesn't do #2 properly and actually crashes inkscape: #Loop through all the selected items in Inkscape for id, node in self.selected.iteritems(): #Check if the node is a Group ( "svg:g" tag in XML ) if node.tag == inkex.addNS('g','svg'): #DO SOME THINGS TO GROUPS outputBlock += "Found a Group!" + "\n" children = list(node) for node2 in children: outputBlock += "Group " + str(node) + " contains: " + str(node2.attrib["id"]) + "\n" node2.attrib["max_stitch_length"] = str(max_stitch_length) I am sure I am going to have to create an XML schema right? If so can you point me in the right direction? > > > So, is there a standard way to extend SVG or embed such codes in SVG for > > a given object? > Extending SVG is in principle very easy, just define a namespace that > hasn't been taken yet (and preferably as specific as possible) and use > elements/attributes from that namespace. Ideally you would also create a > schema to define which elements/attributes are in that namespace and so > on, but I wouldn't necessarily start out that way (although it's > obviously a good idea to think about a formal definition if you want > this to be used by others as well, and/or save yourself some trouble in > the future). > > The idea is that viewers/editors will ignore anything they don't > recognize. The extent to which this is true in practice varies a bit, > and it's definitely not a given that an editor (Inkscape) will preserve > the tags, but in principle it should "work" (in the sense that nothing > will suddenly go wrong). Can you provide me with any urls which show an example of how to create an XML schema? In the past when I have looked, I just walk away with a headache. > > I would like to do this in SVG and Inkscape since I believe both are > > scriptable and both can be used for print as well. (This is a project > > for both print and embroidery.) > Inkscape itself is not really scriptable. What you can do is write a > python extension that essentially gets a piece of SVG to transform. But > this is fairly flexible. Also, if you know C/C++ you might be able to > write something like an LPE to help out. LPE? I do know several languages, including C/C++. I thought Inkscape was. I would like to be able to change colors (and maybe remove them in some cases), resize and place objects and save/load files from scripts. > > > Additional request for information: > > Is it possible to define a custom color table? Embroidery machines > > usually have a fixed color table (which can be converted to various > > thread vendor product/color numbers). > Not sure, but I think there is at least some support for color > management. Perhaps someone else knows more about this? I think the palettes was what I was looking for and have since learned how to do this. > > > Is it possible to turn an outline on for an object and give it a > > different color than the object, or easily create an outline? > You mean outline as in stroke? If so, that's trivial in SVG, every > object intrinsically has a fill and a stroke. Yes, I finally figured this out. As I said, new to inkscape and SVG. > > > Finally, is there a way to do "Ungroup repeatedly until there are no > > groups left, and convert objects to paths." as part of an extension > > (http://www.jonh.net/~jonh/inkscape-embroidery/) without modifying the > > original (as part of an export, etc.)? > I think it's possible to create extensions for output as well, so > conceivably this would be possible. In any case, you might want to have > a look at this extension: > > https://gitorious.org/various-small-stuff/inkscape-ungroup-deep/ > I am starting to wonder if I actually need this, but on having looked at that code, I was able to at least start working on groups with my code. Thank you, Trever

4 3

Codestyle: _*
by Johan Engelen 18 Jan '12

18 Jan '12

Hi all, I am busy 'improving' a small part of the code to use an underscore for class members. I think this helps fight bugs when converting C functions to class methods. For example, a SPPath function may define a temporary variable 'curve', but that one will hide the class's own 'curve' variable (inherited from SPShape). Since the class hierarchy is quite long at places, this is not so easily spotted. So I think the _* stuff for members is really nice and clarifies code a lot. However, now I read in our codestyle document: * Underscore as first character of identifiers Please consider that the C++ standard reserves _* identifiers [17.4.3.1.2]: "Each name that begins with an underscore is reserved to the implementation for use as a name in the global namespace". Hmm, quite a large part of our codebase already uses _* to signify class members. I think this is somewhat common practice? Do we agree to ignore this text in the C++ standard? And shall we change our codestyle text to indicate that we use _* to indicate class members? (I hope this does not result in long maillist discussions... Please answer yes or no. I am already convinced that _* is better than without, and cannot be convinced otherwise. (I _may_ consider 'm_' but it is perhaps overly verbose?)) Thanks, Johan

3 4

Re: [Inkscape-devel] Powerstroke requests
by Valerie 18 Jan '12

18 Jan '12

If I may add a few words about interface... Inkscape now has several pretty fun options for path shapes: - Simple line - Pattern along path - Powerstroke - Sketch brush - [anything I might have missed. There will probably be future options too] Now, for the "shape" drop-down I rarely use the presets because they are rarely the exact width I need them at, it's easier to create the right shape and copy it. So, how about the following? Shape: - Line - Thick stroke (<- powerstroke) - Sketch brush - Clipboard - Custom (insert drop-down of shapes you've saved for Pattern along Path) It's rather unfortunate that Inkscape's tool control bar is static, otherwise I'd recommend for common options (like width and repeat options in Pattern Along Path) to appear depending on the shape you've selected. (though in the meantime, can someone please add dashes and markers to the tool option bar? Having to hunt through two layersof Fill & Stroke dialogue each time is a bit annoying... also, a button to match marker colors to stroke color rather than hunting through the menus, please? Some of us do a lot of graphs in Inkscape...) More generally, I'd like to see some proper of sorting of LPEs eventually: - Path shapes can be integrated into pen and other tools - Effects like Gears seem like they belong in Extension -> Render - I'd also Really like easier and on-canvas access to some transformations that would probably be used more often if access were easier (not only LPE): Envelope, Perspective, and Envelope deformation. Couldn't we include them as a drop-down options (like with pen and Shape) in the Select and Transform tool? I can do mock-ups.

5 10

cannot compile rev 10891 (Windows XP)
by alvinpenner 17 Jan '12

17 Jan '12

attempting to compile rev 10891 I get the following error message: Make error line 289: problem compiling: src/2geom/conicsec.cpp:1491:20: error: prototype for 'std::vector<Geom::Point> Geom::xAx::allNearestPoints(const Geom::Point&) const' does not match any in class 'Geom::xAx' src/2geom/conicsec.h:477:24: error: candidate is: std::vector<Geom::Point> Geom::xAx::allNearestPoints(Geom::Point) const - Alvin -- View this message in context: http://inkscape.13.n6.nabble.com/cannot-compile-rev-10891-Windows-XP-tp3677… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

3 2

Traversing nodes of a path in order
by Maximilian Albert 17 Jan '12

17 Jan '12

Hi all! After a long break I just had a quick play-around with some of the Inkscape code. At some point I needed to traverse the nodes of the selected path in the order in which they appar along the path, but I couldn't find out how to do it in the limited time I was able to spend. What's the correct/recommended way of doing this? Are there some examples on the wiki or somewhere else? Cheers, Max

5 8

Writing an extension
by Trever L. Adams 16 Jan '12

16 Jan '12

This relates to https://bugs.launchpad.net/inkscape/+bug/247463 and comment 37 in particular. I would like to be able to attach information to objects that are needed for high quality digitization. This includes stitch length and stitch direction. I am thinking of displaying the direction as gradient, although direction may be very complex. I am just learning about SVG so, I do not know if there are smart ways of doing this. (For example, think of a leaf, where you may have 20 different direction changes.) I also do not know XML very well (creating schema, etc). So, is there a standard way to extend SVG or embed such codes in SVG for a given object? How would I go about attaching buttons, etc. in the GUI? Can I have Inkscape view the direction code as a gradient for display (if an option is set)? Or, show the fill as lines going in that direction? (Again, this wouldn't be done in printing/export/etc., only in viewing with an option set.) I would like to do this in SVG and Inkscape since I believe both are scriptable and both can be used for print as well. (This is a project for both print and embroidery.) Additional request for information: Is it possible to define a custom color table? Embroidery machines usually have a fixed color table (which can be converted to various thread vendor product/color numbers). Is it possible to turn an outline on for an object and give it a different color than the object, or easily create an outline? Finally, is there a way to do "Ungroup repeatedly until there are no groups left, and convert objects to paths." as part of an extension (http://www.jonh.net/~jonh/inkscape-embroidery/) without modifying the original (as part of an export, etc.)? Thank you, Trever

2 1

nigthlies ppa
by Alexandre Prokoudine 14 Jan '12

14 Jan '12

Hi, Apparently https://launchpad.net/~inkscape-nightly/+archive/ppa turns up first in google for "Inkscape nightly", even though it's an outdated PPA. Could we please somehow redirect people to the real one? Alexandre Prokoudine http://libregraphicsworld.org

1 0

Extended input issues with later GTK2
by Jon Cruz 13 Jan '12

13 Jan '12

Just wanted to toss out a note that I think I've found a main problem with how Inkscape deals with extended input devices. The issue where they give no extended pressure, etc. on later GTK2, including that in Ubuntu 11.10, is due to missing event initialization. I'm trying to narrow it down a bit. Of course, there are still some other bugs that appear to give random garbage in the middle of extended input. There's a good chance that a simple work-around could even filter those out. So, the main thing now is to know if anyone is trying to use tablets currently and is tripping over GTK2 extended input problems. Speak on up and we might be able to get things at least passible soon. Thanks.

6 10

regression in current trunk (r10873) when zooming in/out
by ~suv 12 Jan '12

12 Jan '12

A recent commit (one of r10870-10873) has changed how the canvas gets redrawn (prior build r10869 is still ok): with my latest builds of r10873 [1], the canvas is not properly cleared when zooming in/out. Steps to reproduce: 1) open the attached file in Inkscape 2) zoom in closer and then zoom back out several times --> result: <http://imgh.us/regression-test-r10873-2-screenshot.png> (compare to <http://imgh.us/regression-test-r10873-2.svg>) ~suv [1] tested on Leopard and Lion: - Gtk+/X11 with cairo 1.10.2 (32bit, 64bit), debug + optimized - Gtk+/Quartz with cairo 1.11.2 (32bit), optimized

2 2

Re: [Inkscape-devel] Extended input issues with later GTK2
by Jasper van de Gronde 11 Jan '12

11 Jan '12

On 11-01-12 16:22, jbc.engelen@...2731... wrote: > ---- Jasper van de Gronde <th.v.d.gronde@...528...> wrote: >> I usually just download the latest TDM GCC from this site: >> http://tdm-gcc.tdragon.net/download >> I would recommend taking the 32 bit bundle installer. >> >> Any objections if I update the Wiki page to point to the site above >> instead of the direct download? > > Not at all. We should always be able to build with latest TDM GCC. > Done.

1 0

Re: [Inkscape-devel] NULL vs. 0
by Jon Cruz 09 Jan '12

09 Jan '12

On Jan 7, 2012, at 11:39 AM, Tomaz Canabrava wrote: > Stroustrup answer to that: > > Should I use NULL or 0? > > In C++, the definition of NULL is 0, so there is only an aesthetic > difference. I prefer to avoid macros, so I use 0. Another problem with > NULL is that people sometimes mistakenly believe that it is different > from 0 and/or not an integer. Actually, for a modern compiler NULL is not an integer. C++ did a bit of a change, and 0 gained special meaning. I believe that most of the systems where it made an actual difference are now gone, but it did. However... the main reason I made the code change is that when I updated to gcc 4.5.2, it started warning on that constructor. It complained that we were setting a pointer value into a non-pointer variable. So we probably have NULL defined as some pointerish macro or value and which should not be assigned to integer variables, while '0' is a magical constant that the compiler knows to just do the right thing with for both pointers and integers. '0' by the C++ language definition works in all cases, but NULL does not. This and the associated warning start to become very important for 64-bit code. Mixing integers and pointers leads to major problems. Bottom line, though, is that we need to remove warnings by fixing the code. The pointer assignments in that initializer could be changed to "NULL", but the integer ones need to stay changed to zero.

5 5

Janitorial tasks
by Kris De Gussem 08 Jan '12

08 Jan '12

Hi all I like to go on with the replacement of the deprecated wrapper functions in src/xml/repr.h with direct calls to their respective functions (as listed in the first section on http://wiki.inkscape.org/wiki/index.php/Janitorial_tasks). Any objections? Kind regards Kris

4 8

Unweirdification of preferences button location in toolbar ; )
by Johan Engelen 08 Jan '12

08 Jan '12

Hi all, With the unweirdification of the preferences dialog in place... shall we exchange the locations of the document properties and inkscape preferences buttons in the toolbar? I am always confused to see them in the order they are in now. Ciao, Johan

1 0

NULL vs. 0
by Johan Engelen 07 Jan '12

07 Jan '12

Hi all, Before reading on, have a look at this code fragment, and ask yourself the question "what type is _desktop, _verb_t, _css, _tool_obs, etc.?" StyleSwatch::StyleSwatch(SPCSSAttr *css, gchar const *main_tip) : _desktop(0), _verb_t(0), _css(0), _tool_obs(0), _style_obs(0), _table(2, 6), _sw_unit(0) The correct answer is: _desktop is a pointer _verb_t is an int _css is a pointer _tool_obs is a pointer _style_obs is a pointer _sw_unit is a pointer Please STOP changing NULL into 0. It makes the code completely unreadable and makes me want to quit Inkscape. I am not kidding. Thanks, Johan

1 0

New: add nodes at extreme values
by Johan Engelen 05 Jan '12

05 Jan '12

Hi all, To help font designers, I just added new functionality to the node tool. It adds a node at the extreme values of a path, if there is not already a node there. (because of a bug in 2geom, it does not work for some special cases, we are working on it) At the moment, this new feature adds 4 buttons to the node tool. Way too much of course. The plan is to move them into a submenu of the Add nodes button. This should not be too hard, the first step is to rewrite in /src/widget/toolbox.cpp: " <toolitem action='NodeInsertAction' />" " <toolitem action='NodeInsertActionMinX' />" " <toolitem action='NodeInsertActionMaxX' />" " <toolitem action='NodeInsertActionMinY' />" " <toolitem action='NodeInsertActionMaxY' />" to " <toolitem action='NodeInsertAction'>" " <menu action='NodeInsertActionMenu'>" " <menuitem action='NodeInsertActionMinX' />" " <menuitem action='NodeInsertActionMaxX' />" " <menuitem action='NodeInsertActionMinY' />" " <menuitem action='NodeInsertActionMaxY' />" " </menu>" " </toolitem>" or so I learn from a gtk demo [1]. It uses a new GtkMenuToolButton [2]. But, alas, if you rewrite it, you get GTK errors and Inkscape terminates... I hope someone can find the time and spirit to work on this. Thanks! Cheers, Johan [1] http://git.gnome.org/browse/gtk+/tree/demos/gtk-demo/appwindow.c?id=2.24.8 [2] http://developer.gnome.org/gtk/2.24/GtkMenuToolButton.html

2 3