- Inkscape Devel - Inkscape Mailman

Regarding GSOC 2011 - Project Continuing C++ification
by Abhishek Sharma 03 Apr '11

03 Apr '11

Hi everybody, It feels pretty nostalgic to be back to coding for inkscape after the last gsoc year. Last year along with Jon Cruz, we achieved some of object oriented build up in the codebase. This GSOC as well I would wish to continue on the same. I'll be glad to have community's views over this years milestone. As in what code customizations and cleanup and further enhancements are supposed to be done this year. I will be delighted to have responses over this. -- Regards, Abhishek Sharma

2 9

Setting margins in "Resize page to drawing or selection"
by Martin Sucha 02 Apr '11

02 Apr '11

Hi, I needed to add a margin around my drawing and noticed that setting the margin in Document Properties/Resize page didn't work, so I went ahead and looked into the code. I just commited a fix (r10145). Another weird behaviour is that when using the "Resize page to drawing or selection" for the second and subsequent times, only one margin is updated after clicking the button even though I change values in all four (the others are reverted to their remembered values). Any ideas what may cause this? Thanks. Regards, Martin Sucha

2 1

Re: [Inkscape-devel] Multipage support as a GSoC project?
by gespertino＠...400... 02 Apr '11

02 Apr '11

> So, yes, we could implement a "simple" fix that lets users specify a > font size in points. We could even just use the SVG unit pt, as that is > also defined as an "appropriate" multiple of px. And perhaps we should > do this if people find it useful. But I think it would give the wrong > impression (that you were actually using an absolute unit) and it could > lead to weird issues once Inkscape will let the user specify the > coordinate system (do we then stick to the somewhat arbitrary scaling > factor or do we want true points?). I admit that it's a slightly > academic debate, but still, what's the point if you're not really using > points? As I see it, we already have real world units in inkscape UI everywhere, all of them assuming a resolution of 90dpi. People is using those "real world units" based on that: the default document is A4, if inches or centimeters are selected as default units for the document, that's what the user gets in inkscape. Of course it's a problem when you want to take the artwork created in Inkscape to other applications (for instance Scribus, which apparently uses 72 dpi for imported SVGs) I'm aware that adding that option (real world units in the type dialog assuming 90dpi) won't be a good long-term solution, but I'm sure it will be well received by a lot of people as an acceptable interim solution. Type size in pixels was reported as a bug several times. Probably people working for web don't care, but designers creating brochures, posters and things that have to end up printed, are more used to DTP points than to any other unit for type. With that change things will be better for that part of the userbase, and won't be worse for anybody, since the real units confusion is already installed with the current implementation in most of the tools.

4 3

Multipage support as a GSoC project?
by Jason Creighton 02 Apr '11

02 Apr '11

Hi All, I'm a student considering applying to GSoC for Inkscape, and I'm wondering how you guys feel about multipage support as a project. I asked about this on the IRC channel and it was pointed out to me that multipage support was dropped from SVG 1.2, so the state of this in the SVG standard is kind of up in the air. Is the lack of an official standard a show-stopper? If not, is this even something you'd like to see worked on at this time? Or are there other, more pressing, features or issues that you'd prefer to see applications on? Thanks, Jason

8 20

[PATCH] Setting grid origin has no effect (bug #561503)
by Jason Creighton 01 Apr '11

01 Apr '11

Hi, I've been looking into the cause of this bug: https://bugs.launchpad.net/inkscape/+bug/561503 As far as I can tell, the bug is exposed when the spinboxes are initialized in CanvasXYGrid::newSpecificWidget(). (display/canvas-grid.cpp). Starting on line 732 or so, there is a series of calls to setValue() on the origin x/y and the spacing x/y RegisteredScalarUnit instances. These calls to setValue() end up setting the setProgrammatically flag to "true", which is supposed to be immediately cleared in the on_value_changed callback, *BUT* for the origin boxes, the on_value_changed callback is never called, and the flag never gets cleared. The initial value of the spinboxes is "0", and we're setting them to their default of "0", so my guess is that GTK doesn't bother to call on_value_changed in the case that the value hasn't actually changed. So then when the user changes the widget for the first time, it has no effect because the first call to the on_value_changed callback only clears setProgrammatically instead of actually doing anything. I wasn't totally sure about the best way to fix this. It's not clear to me why Scalar::setValue() doesn't just do a "setProgrammatically = false" after the call to the widget's set_value(). It seems like it would be simpler and more robust than clearing it in each callback. However, I assumed that there was some sort of reason I couldn't see for leaving it up to the callbacks to reset it, so my (attached) fix is to make Scalar::setValue() not do anything at all if the new value is the same as the old value. This fixes the issue at hand, however, as su-v pointed out to me on the IRC channel, it seems odd that this isn't a more widespread problem. What about all the other spinboxes that default to zero? I'm not familiar enough with the codebase to know why the bug was only exercised in that particular area. As an aside, what do you guys use to debug Inkscape? I tried just using gdb, but I found that setting breakpoints changed the behavior of the program (!), so I ended up just printing to stdout with debugging info, which is quite tedious. Cheers, Jason

2 1

Re: [Inkscape-devel] Multipage support as a GSoC project?
by gespertino＠...400... 31 Mar '11

31 Mar '11

I'd add hyphenation to the Text items. And the ability to specify in points instead of pixels at least the size of the type.

3 4

Doxygen cleanup
by Jon Cruz 30 Mar '11

30 Mar '11

First of all, is anyone using our doxygen docs, or does anyone care about the format? Our current usage is a bit inefficient, so I've been thinking of cleaning it up a bit. First on the hit list are those annoying "@brief" instances. Or config file has this: > # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen > # will interpret the first line (until the first dot) of a JavaDoc-style > # comment as the brief description. If set to NO, the JavaDoc > # comments will behave just like regular Qt-style comments > # (thus requiring an explicit @brief command for a brief description.) > > JAVADOC_AUTOBRIEF = YES So that means instead of : /** * @brief XML - prefs observer bridge * * This is an XML node observer that watches for changes in the XML document storing the preferences. * It is used to implement preference observers. */ We can do: /** * XML - prefs observer bridge. * * This is an XML node observer that watches for changes in the XML document storing the preferences. * It is used to implement preference observers. */ The key point is to just have a single period so that the first sentence *is* the brief description. No need for additional work or @ tags.

6 12

proposal to enhance the python extensions
by Mark Schafer 29 Mar '11

29 Mar '11

Hi everyone, I've been lurking on this list and making extensions for Inkscape in python. (I'm also keen on the dbus scripting but I use windows so no good for me right now...) I have had difficulty understanding what some of the extensions do and in writing my own I have discovered the notebook tab. I want to suggest using the notebook tab at the top of each extension to help document how they work. Here is a screenshot of a suggested UI from my Lasercut box extension. http://www.flickr.com/photos/33807726@...2603.../5569339514/ Extra tabs could break up the info for clarity and show data like author,url, etc So I propose: - supply a template for people writing extensions to use as a starter - and some docs/tutorials on making extensions in python - modify the existing extensions included in Inkscape to follow this guideline - maybe fix broken extensions if there are any (I haven't tried every one) But I don't want to do something the dev team thinks is a waste of time, and I am unsure of the translation issues with such an approach. Any thoughts ? Mark...

6 7

GSoC 2011 - Mentors
by Josh Andler 29 Mar '11

29 Mar '11

Hey all, It appears that Melange's invitation system is not currently working (I can't seem to invite via link_id or email addresses). If you're interested in mentoring, please visit http://socghop.appspot.com/gsoc/org/google/gsoc2011/inkscape and apply to be a mentor. Thanks for your time! Cheers, Josh

1 0

Merging the Cairo branch
by Josh Andler 29 Mar '11

29 Mar '11

Hey, So, I really think that we should entertain the idea of merging the cairo branch into trunk. The plan has been for us to not release 0.49 until it is ready, so the couple outstanding bugs in cairo shouldn't be a huge deterrent. We could also set up a PPA to produce the trunk builds of cairo & pixman so that fixed libs are easily installable in the meantime (at least for people using debian-based systems). I was talking to John Cliff and he put forth a very good point which is that we really need to get as much testing as possible on it prior to a release. Before it gets asked, yes Jon, color management is broken in it atm. The likelihood of it getting fixed in a branch as opposed to trunk is next to non-existent though... So, would people be okay with a little breakage of existing functionality to get more testing of a cairofied Inkscape? bulia, I included you in the to line here to help gauge the acceptability of this proposal. Cheers, Josh

6 10