- Inkscape Devel - Inkscape Mailman

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

GSoC project ideas
by Krzysztof Kosiński 29 Mar '11

29 Mar '11

Hello I'm not 100% sure yet whether I'll be able to participate in GSoC 2011, but here are my ideas. They can be used by other potential participants. 1. Selections A lot of functions in Inkscape operate on the current selection. This includes things like moving objects to another layer, creating a bitmap copy, etc. This leads to a lot of unnecessary code duplication when some other function needs to reuse selection-specific logic in a way that is not tied to the UI. It also precludes any useful implementation of scripting (e.g. one that does not need to modify the user's selection every time a script is run). In order to rectify this, we should create an object that represents an arbitrary collection of SVG elements. It would work like the selection we have now, but would not be tied to any UI elements - it would just represent an ordered set of elements that can be passed to functions. 2. Fix flowtext Use svg:switch to fix flowtext. Make svg:switch transparent to the SP tree - e.g. a switch should not have its own SP element, the active part of the switch should be transparently included into the SP tree. This can be accomplished by allowing every object to have more than one representation. 3. Make XML private Discussed before. Was the object of a previous year project, but the main effect of that was mass renaming and moving of code into classes rather than any meaningful improvement in encapsulation. The main thing we need is an ability to create SP nodes. Right now we create XML nodes and rely on SP tree callbacks to construct the SP node for us. 4. Typed XML tree The XML tree stores strings, which is rather wasteful and leads to a lot of boilerplate in SP object implementations. We have enough knowledge about the document at the XML level to know the type of each attribute and CSS property based on its name. Storing parsed values would save space, particularly for embedded images, at the cost of slightly more expensive saving. GVariant could be used. 5. GTK3 compatibility This would involve removal of deprecated code, so that Inkscape compiles with both GTK2 and GTK3. 6. 2geom improvements Move and rewrite code 2geom to the point where it can take over the job of livarot, libavoid, etc. Document the new code and make sure it fits nicely with existing code. The scope of the project could be limited to implementing Boolean operations on paths. 7. Rendering speed improvements Further work on the Cairo branch in several small sub-projects: a) Instead of re-rendering the same pixels every time a new tile of a filter is rendered, cache them until the rendering is done. The implementation could involve allocating screen-size bitmaps for each layer of a filtered object and filling them with data in small increments. b) Render editing controls to a separate image that is composited on top of the drawing, so that what a path outline is highlighted, there is no need to re-render the object under it. c) Render each layer of the drawing to a separate image; alternatively, render 3 images: everything below current layer, current layer and everything above. This would allow the user to give us some hints. Regards, Krzysztof

3 3

Greetings
by Eric Kuzmenko 28 Mar '11

28 Mar '11

Hello there fellow inkscape-devel mailing list subscribers, I'm Eric Kuzmenko, a programmer want-to-be. Almost none of you have met me, I just want to establish a position in your community, hopeful I can obtain someone's friendship here. Anyway, I just wanted to state that I am going to attempt to apply for gsoc sometime late next week. I'm currently trying to get a grasp of the gtkmm wrapper in order to press that knowledge to fixing some bugs and getting those two patches in before April 8, though there's a great chance I won't be able to due to the amount I need to learn. Even if I fail to get that far this soon I will continue attempting to help patch up the code during the summer, whether it with gsoc or not, hopefully I can be of some help. If you've read this far then thank you. =)

2 1

Fedora, Open Clip Art Library, and Inkscape
by Tavmjong Bah 27 Mar '11

27 Mar '11

Hi, I just came across this. I don't know anything about how "Import from Open Clip Art Library" works but at least one person thinks it will be broken in Fedora 16 as Fedora is planning on removing gnome-vfs2. http://lists.fedoraproject.org/pipermail/devel/2011-March/149571.html Tav

3 2