- Inkscape Devel - Inkscape Mailman

bug 478157: Mid-markers are rendered above end-markers
by unknown＠example.com 28 Dec '09

28 Dec '09

Hi all, Who knows what determines the rendering order of the different markers? See https://bugs.edge.launchpad.net/inkscape/+bug/478157. Currently, endmarkers are drawn beneath midmarkers, although the code calls sp_marker_show_instance last for endmarkers. Perhaps this has to do with the 'key' that is passed to sp_marker_show_instance? (determines the layer?) Have a look at sp_shape_update_marker_view in sp-shape.cpp. Thanks, Johan

2 2

Re: [Inkscape-devel] Specification: Improved image propertiesdialog (0.48)
by Valerie 28 Dec '09

28 Dec '09

Just a small note on user cases: The lowest common denominator of Joe Schmoe out there (that can be expected to use Inkscape) is probably the Windows user who's only familiar with 2 programs: an internet browser and Microsoft Word. That's it. He's neither a webpage designer nor a raster graphics master. He's the type who (very regretfully) takes 2 MB photos, sends them as is to you by email, and doesn't even know (nor care) that he's doing it wrong (unfortunately, this is also about 90% of the people I've worked with...). Such a person's notion of copy/paste is: - Copy text. Paste in Word file. - Copy image. Paste in Word file. - If the image is modified, delete the original image and paste the new one in. - They don't expect anything they've pasted in to disappear when they move the file around or send it to their family/friends/boss. (and yes, that level of user may come to use Inkscape. I often use Inkscape to do charts for work, it's handy)

1 0

Node tool progress
by Krzysztof Kosiński 27 Dec '09

27 Dec '09

Hello everyone. Good news: there are only three regressions left in the new node tool now. 1. Sculpting (Alt+drag) doesn't work. 2. Snapping nodes doesn't work. 3. Transforming one handle using the keyboard (left/right Ctrl and Alt + various keys) doesn't work Everything else should work like in the old one. I think 1 and 3 are not critical, so the only thing left to fix before the tool is ready for prime time is snapping. Bad news: snapping is a complex feature, particularly because I want to provide it for nodeset transforms. Additionally, there is some code in SnapManager that assumes only one editable path. It could be finished before the new year, but it could as well take another month. Regards, Krzysztof

4 4

Passing data with sp_action_perform(SPAction *action, void * data)? [2]
by Alex Leone 25 Dec '09

25 Dec '09

Hello, (Sorry about the duplicate message - forgot to turn off rich text) I'm attempting to write a patch that adds a margin when setting page size through the "Fit page to selection" button in document properties. I've already added the ui elements (RegisteredScalarUnit's) for marginTop, marginLeft, etc, but I can't figure out how to get the values to the function that resizes the page. Here's how the page currently gets resized: 1. When clicked, "Fit page to selection" fires src/ui/widget/page-sizer.cpp: 487: PageSizer::fire_fit_canvas_to_selection_or_drawing() { Verb *verb = Verb::get( SP_VERB_FIT_CANVAS_TO_SELECTION_OR_DRAWING ); SPAction *action = verb->get_action(dt); sp_action_perform(action, NULL); } 2. sp_action_perform eventually calls src/verbs.cpp:2149: FitCanvasVerb::perform(SPAction *action, void *data, void */*pdata*/) { fit_canvas_to_selection_or_drawing(dt); } where the void *pdata parameter is the second argument from sp_action_perform. 3. This eventually calls src/document.cpp:601: SPDocument::fitToRect(Geom::Rect const &rect) My plan was to add marginTop, marginLeft, etc as parameters to SPDocument::fitToRect, and somehow pass these parameters through the void *data parameter in sp_action_perform. However, all the other calls to sp_action_perform in inkscape set the void *data parameter to NULL, and it looks like the action handler doesn't have any code to call free on the parameter after all the action listeners are serviced. Am I trying to do this completely wrong? Thanks, - Alex (Attached is a patch that adds the margin UI elements in document properties)

1 0

A request and a thank-you to the Inkscape developers
by Michael Grosberg 25 Dec '09

25 Dec '09

Hello all, jsut wanted to thank all of you developers for creating this amazing piece of software, just made a nice Christmas card (sorry, "season's greetings" card, gotta be PC these days) for my boss with it and he loved it. Anyway, there's this feature request I made long ago and every so often some other guy pipes in with a "me too" and I get a reminder in my email about it. It;s a request to make inkscape remember dialogs window status: https://bugs.launchpad.net/inkscape/+bug/171579 That is, make dialogs such as layers, paint/stroke, align etc. stay open if I opened them in a previous session. This is really important guys! It's really helpful not to have to open them again whenever you open a file. It doesn't have to be a file-specific feature, it should be global, so once you set up the interface to your liking, it should just stay this way across all documents you open later. Also, the layers dialog always opens very small on my machine (showing maybe 2 layers) and I always have to resize it. I will thank you without end if you decide to implement this on 0.48.

1 0

Re: [Inkscape-devel] [Bug 487038] Re: 0.47 build error with poppler 0.12.2 on Linux
by the Adib 25 Dec '09

25 Dec '09

So what about putting some effort in creating a poppler svg backend (as proposed earlier)? or should we move to plain poppler-glib connectors? my 2 ct. Adib. On Fri, Dec 25, 2009 at 1:00 AM, Launchpad Bug Tracker <487038@...1882...> wrote: > This bug was fixed in the package inkscape - 0.47.0-1ubuntu1 > > --------------- > inkscape (0.47.0-1ubuntu1) lucid; urgency=low > > * Merge with Debian testing (LP: #498150). Remaining changes: > - debian/control: > - promote python-lxml, python-numpy, python-uniconvertor to Recommends. > - demote pstoedit to Suggests (universe package). > - drop libssl-dev, no longer needed (Debian bug 484527). > - debian/rules: > - Handle parallel builds via -j (Debian bug 562226). > - Run intltool-update on build (Ubuntu-specific). > - Add translation domain to .desktop files (Ubuntu-specific). > - debian/watch: > - Correctly handle "pre" versions (Debian bug 562225). > * 50-poppler-API.patch, debian/control: poppler 0.12.2 changed the > GfxColorSpace API (LP: #487038). > > inkscape (0.47.0-1) unstable; urgency=low > > * Imported Upstream version 0.47 > * This is upstream version 0.47, I added the .0 because > I forget the ~ in the -pre versions. > * add proper Vcs-fields to debian/control > * upload sponsored by Guido Guenther <agx@...153...> > > inkscape (0.47pre4-1) unstable; urgency=low > > * Imported Upstream version 0.47pre4 > * upload sponsored by Guido Guenther <agx@...153...> > > inkscape (0.47pre2-2) unstable; urgency=low > > * fix installation of usr/share/application- > registry/inkscape.applications > * upload sponsored by Guido Guenther <agx@...153...> > > inkscape (0.47pre2-1) unstable; urgency=low > > * new upstream release (closes: #532277) > Improvements and new features include: > - code cleanups and refractoring > - autosave feature, configurable via Inkscape preferences > - new and enhanced tools, extensions and filters > - new path effects > - enhanced import and export features > - improved svg support > - many other improvements and new features. For a better and more > comprehensive decription of enhancements see the online release notes at > http://wiki.inkscape.org/wiki/index.php/Release_notes/0.47 > * remove 04-only-use-valid-font-families-in-text-tool.dpatch > since there is a better fix in the code now (closes: #496784) > * remove other patches which are no longer needed: > - 01_mips.dpatch > - 02-poppler-0.8.3.dpatch > - 03-chinese-inkscape.dpatch > - 05_fix_latex_patch.dpatch > - 06_gcc-4.4.dpatch > - 07_cdr2svg.dpatch > - 08_skip-bad-utf-on-pdf-import.dpatch > - 09_gtk-clist.dpatch > - 10_belarussian.dpatch > - 12_desktop.dpatch > fix patch permissions in clean target > * upload sponsored by Guido Guenther <agx@...153...> > * build-depend on libgsl0-dev > * small adations to debian/rules > -- Kees Cook <kees@...1792...> Wed, 23 Dec 2009 15:38:43 -0800 > > ** Changed in: inkscape (Ubuntu Lucid) > Status: Fix Committed => Fix Released > > -- > 0.47 build error with poppler 0.12.2 on Linux > https://bugs.launchpad.net/bugs/487038 > You received this bug notification because you are a member of Inkscape > Bug Team, which is subscribed to Inkscape. >

1 0

autopackage
by Alexandre Prokoudine 24 Dec '09

24 Dec '09

Hi, Any ideas what happened to the person who used to provide autopackages? :) P.S. Merry Christmas :) Alexandre

2 1

Wiki Contact Information
by unknown＠example.com 24 Dec '09

24 Dec '09

http://wiki.inkscape.org/wiki/index.php/Contact_information says, "Names are listed along with the associated SourceForge username in parenthesis. Given a username, a person can be contacted by emailing username at users.sf.net." I would like to propose that all the obfuscated email address be removed and the names in the "Contact Persons by Field" list be replaced with links to the appropriate Launchpad user pages which can then become the single source of contact information for each member of this project. I'll gladly make the first cut at this if it is an acceptable idea. NeoPhyte Representative

2 1

git-bzr?
by Maximilian Albert 23 Dec '09

23 Dec '09

Hi, does anyone have experience accessing a bzr repository using git (something similar to git-svn for subversion)? I haven't found time so far to dive into bzr, and I'm so much used to my workflow with git that I'd like to keep using it if possible (at least for some time). I saw that there is a git-bzr script (http://github.com/pieter/git-bzr) but it's not maintained any more and I couldn't get it to work with the inkscape repo (by the way, is there an absolute url to access the repository instead of lp:inkscape?). Any hints how to make the git-bzr interaction work would be greatly appreciated. Many thanks in advance and best wishes for a wonderful Christmas to everyone, Max

3 6

NEW: truncated text indication
by bulia byak 23 Dec '09

23 Dec '09

When a flowed text is truncated (i.e. the frame is too small for the entire text), the frame is shown red, and the statusbar hint includes [truncated]. You need to resize the frame to see the truncated end of the text. Analogously, if the path of a text-on-path object is too short to display the entire text, the statusbar will report it as [truncated]. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

7 15