June 2011 - Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] [CREATE] LGM2012 in Argentina?
by Josh Andler 13 Jun '11

13 Jun '11

If Felipe is in, I must make it a priority to attend. Perhaps we could also organize the proposed inkscape dev sprint for it as well. Cheers, Josh On Jun 12, 2011 7:23 PM, "Felipe Sanches" <juca@...2270...> wrote: > I would certainly attend LGM in Argentina! And I guess that Aurelio Hackert > (Inkscape developer), Joao Bueno (for sure!), Rodrigo Pitanga, Farid > Abdelnour, Nara Oliveira, Valessio Brito and Karlisson Bezerra are some of > the members of the brazilian libre graphics community that would probably > attend also. > > cheers, > Felipe Sanches (Juca) > Inkscape developer > > On Sun, Jun 12, 2011 at 12:57 AM, Dave Crossland <dave@...1555...> wrote: > >> Hi! >> >> I was running a bunch of libre font workshops in Argentina last month, >> and Fundacion Gutenberg was one of the institutions who hosted me in >> Buenos Aires. >> >> http://www.fundaciongutenberg.edu.ar/ >> >> The staff there are extremely enthusiastic about libre graphics, and >> made a serious comment about offering to host LGM 2012 if there was >> interest in the community. >> >> Is there such interest? >> >> -- >> Cheers >> Dave >> _______________________________________________ >> CREATE mailing list >> CREATE@...626... >> http://lists.freedesktop.org/mailman/listinfo/create >>

1 0

Connector Tool
by Josh Andler 12 Jun '11

12 Jun '11

Hey All, It would be really nice if someone would look into some of the issues with the connector tool, especially since they keep adding up and rarely get redued. It seems that at this point it is unmaintained and unfinished, which to me puts it in the same category as the our disabled technical/lpe tool. Meaning that if it doesn't see love by the time we're wrapping up 0.50 (or whatever that version will be), I personally feel that it should be disabled at that point and will request a vote. I know people have used it, it's cruft is in their documents, but if it's not going to be given a serious go, it makes no sense to have it. Just wanting to bring the issue up with plenty of notice. Cheers, Josh

6 5

Make errors (WPG and EMF)
by Nicolas Dufour 12 Jun '11

12 Jun '11

Hello, The trunk and 0.48.x branch don't compile on Windows XP with the current revisions due to the following make error: Make error line 299: problem compiling: In file included from c:\devlibs/include/libwpg-0.1/libwpg/WPGraphics.h:29, from c:\devlibs/include/libwpg-0.1/libwpg/libwpg.h:35, from src/extension/internal/wpg-input.cpp:51: c:\devlibs/include/libwpg-0.1/libwpg/WPGString.h:41: warning: type qualifiers ignored on function return type c:\devlibs/include/libwpg-0.1/libwpg/WPGString.h:45: warning: type qualifiers ignored on function return type In file included from c:\devlibs/include/libwpg-0.1/libwpg/WPGBitmap.h:30, from c:\devlibs/include/libwpg-0.1/libwpg/WPGPaintInterface.h:30, from c:\devlibs/include/libwpg-0.1/libwpg/libwpg.h:36, from src/extension/internal/wpg-input.cpp:51: c:\devlibs/include/libwpg-0.1/libwpg/WPGRect.h:50: warning: type qualifiers ignored on function return type c:\devlibs/include/libwpg-0.1/libwpg/WPGRect.h:51: warning: type qualifiers ignored on function return type In file included from c:\devlibs/include/libwpg-0.1/libwpg/WPGPaintInterface.h:30, from c:\devlibs/include/libwpg-0.1/libwpg/libwpg.h:36, from src/extension/internal/wpg-input.cpp:51: c:\devlibs/include/libwpg-0.1/libwpg/WPGBitmap.h:53: warning: type qualifiers ignored on function return type c:\devlibs/include/libwpg-0.1/libwpg/WPGBitmap.h:56: warning: type qualifiers ignored on function return type In file included from c:\devlibs/include/libwpg-0.1/libwpg/WPGPaintInterface.h:31, from c:\devlibs/include/libwpg-0.1/libwpg/libwpg.h:36, from src/extension/internal/wpg-input.cpp:51: c:\devlibs/include/libwpg-0.1/libwpg/WPGBinaryData.h:52: warning: type qualifiers ignored on function return type src/extension/internal/wpg-input.cpp: In member function 'virtual SPDocument* Inkscape::Extension::Internal::WpgInput::open(Inkscape::Extension::Input*, const gchar*)': src/extension/internal/wpg-input.cpp:72: error: 'input' was not declared in this scope src/extension/internal/wpg-input.cpp:78: error: 'olestream' was not declared in this scope src/extension/internal/wpg-input.cpp:79: error: type '<type error>' argument given to 'delete', expected pointer src/extension/internal/wpg-input.cpp:84: error: 'input' was not declared in this scope src/extension/internal/wpg-input.cpp:88: error: type '<type error>' argument given to 'delete', expected pointer src/extension/internal/wpg-input.cpp:97: error: 'input' was not declared in this scope src/extension/internal/wpg-input.cpp:97: error: 'output' was not declared in this scope src/extension/internal/wpg-input.cpp:98: error: type '<type error>' argument given to 'delete', expected pointer src/extension/internal/wpg-input.cpp:104: error: 'output' was not declared in this scope src/extension/internal/wpg-input.cpp:105: error: 'input' was not declared in this scope src/extension/internal/wpg-input.cpp: At global scope: src/extension/internal/wpg-input.cpp:66: warning: unused parameter 'mod' src/extension/internal/wpg-input.cpp:66: warning: unused parameter 'uri' The branch also show an error with emf-win32-inout.cpp: Make error line 299: problem compiling: src/extension/internal/emf-win32-inout.cpp: In member function 'virtual SPDocument* Inkscape::Extension::Internal::EmfWin32::open(Inkscape::Extension::Input*, const gchar*)': src/extension/internal/emf-win32-inout.cpp:2356: error: invalid conversion from 'int (*)(HDC__*, HANDLETABLE*, const ENHMETARECORD*, int, LPARAM)' to 'int (*)(HDC__*, HANDLETABLE*, ENHMETARECORD*, int, LPARAM)' src/extension/internal/emf-win32-inout.cpp:2356: error: initializing argument 3 of 'BOOL EnumEnhMetaFile(HDC__*, HENHMETAFILE__*, int (*)(HDC__*, HANDLETABLE*, ENHMETARECORD*, int, LPARAM), void*, const RECT*)' Not problem when compiling on Ubuntu. Regards, -- Nicolas

3 4

Build problems with r10266
by Tobias Ellinghaus 11 Jun '11

11 Jun '11

Hello, i have issues compiling inkscape on Debian/sid, gcc 4.6.0. I have enabled dbus and get the following error: CXX extension/dbus/document-interface.o ./document.h: In function 'void document_interface_update(DocumentInterface*, GError**)': ./document.h:99:13: error: 'SPRoot* SPDocument::root' is private extension/dbus/document-interface.cpp:979:40: error: within this context extension/dbus/document-interface.cpp:979:44: error: invalid use of incomplete type 'struct SPRoot' ./document.h:46:8: error: forward declaration of 'struct SPRoot' ./document.h:99:13: error: 'SPRoot* SPDocument::root' is private extension/dbus/document-interface.cpp:980:40: error: within this context extension/dbus/document-interface.cpp:980:44: error: invalid use of incomplete type 'struct SPRoot' ./document.h:46:8: error: forward declaration of 'struct SPRoot' ./document.h:99:13: error: 'SPRoot* SPDocument::root' is private extension/dbus/document-interface.cpp:984:40: error: within this context extension/dbus/document-interface.cpp:984:44: error: invalid use of incomplete type 'struct SPRoot' ./document.h:46:8: error: forward declaration of 'struct SPRoot' ./document.h:99:13: error: 'SPRoot* SPDocument::root' is private extension/dbus/document-interface.cpp:985:40: error: within this context extension/dbus/document-interface.cpp:985:44: error: invalid use of incomplete type 'struct SPRoot' ./document.h:46:8: error: forward declaration of 'struct SPRoot' make[3]: *** [extension/dbus/document-interface.o] Error 1 make[3]: Leaving directory `/home/houz/download/inkscape/inkscape/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/houz/download/inkscape/inkscape/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/houz/download/inkscape/inkscape' make: *** [all] Error 2 Do you need any additional information? Tobias

3 2

Depixelizing Pixel Art
by Alexandre Prokoudine 10 Jun '11

10 Jun '11

Hi, FYI: http://www.scribd.com/doc/56137278/Depixelizing-Pixel-Art "We describe a novel algorithm for extracting a resolution-independent vector representation from pixel art images, which enables magnifying the results by an arbitrary amount without image degradation. Our algorithm resolves pixel-scale features in theinput and converts them into regions with smoothly varying shad-ing that are crisply separated by piecewise-smooth contour curves" Alexandre Prokoudine http://libregraphicsworld.org

6 6

Avaailable build for Slackware.
by John Culleton 10 Jun '11

10 Jun '11

The latest build for Slackware is 48.1. It requires updates of a dozen libraries newer than what comes with Slackware 13.37. The first library I tried, GTKMM was not available from its home site. So----what about Inkscape 48? will it work with the older libraries that come with slackware 13.37? How far back in the Inkscape line do I have to go to find a version that will work with the libraries in Slack 13.37? Typically the libraries date back to Oct 2009. -- John Culleton

2 1

Save a copy in current dir?
by Johan Engelen 08 Jun '11

08 Jun '11

Hi all, I'd like some usabilty input for this bug: https://bugs.launchpad.net/inkscape/+bug/791098 It requests an option to have the Save a Copy dialog always open in the current document's directory. The Save As... dialog already has this option (preferences > save). Should I add an option below the Save As... dialog option in the preference dialog, or should I use the same setting for both dialogs? The reason I ask, is that I am a little afraid of adding yet another option... Thanks for advice :), Johan

5 6

Large but small change heads-up
by Jon Cruz 05 Jun '11

05 Jun '11

Hi, I just wanted to toss out a heads-up on change 10254 that I just pushed to trunk. It removed the outdated/unsafe SP_DOCUMENT_DEFS() macro, and changed about 58 files. Most of those were just a few lines, however, so it should not cause any major conflicts. However if anyone has some pending work, now might be a good time to re-sync from trunk so as to avoid potential extra steps being needed when committing.

3 7

Re: [Inkscape-devel] Inkscape 0.48.2 ... coming soon
by Daniel Macks 04 Jun '11

04 Jun '11

On Fri, 3 Jun 2011 13:49:23 -0700, Josh Andler wrote: Hey all, > > Apparently there is an exploit in the gtk we ship with 0.48.1. Given > that the recently updated devlibs required modifying trunk to compile, > it seems logical to just ship out the fixes that have landed in the > 0.48 branch since .1 was released. Do you have a link for this exploit? Trying to decide how to prioritize pushing this update when it's released (and also see if any other things with "their own" libgtk have an affected version). dan -- Daniel Macks dmacks@...2516...

2 2

Inkscape 0.48.2 ... coming soon
by Josh Andler 04 Jun '11

04 Jun '11

Hey all, Apparently there is an exploit in the gtk we ship with 0.48.1. Given that the recently updated devlibs required modifying trunk to compile, it seems logical to just ship out the fixes that have landed in the 0.48 branch since .1 was released. In keeping things up to date and all of that fun, the 0.48.x branch is currently upgrading on lp...so I just wanted to give a heads up to everyone on that (it will just be like when we upgraded trunk). It should hopefully be done in a few hours. If anyone has and questions or concerns, please let me know. Also, if you know of any "must have" fixes which don't already exist that you think should make it, please let me know. Cheers, Josh

3 3

Re: [Inkscape-devel] [Merge] lp:~valavanisalex/inkscape/fix-792263 into lp:inkscape
by Jon Cruz 04 Jun '11

04 Jun '11

On Jun 3, 2011, at 3:52 AM, Alex Valavanis wrote: > Alex Valavanis has proposed merging lp:~valavanisalex/inkscape/fix-792263 into lp:inkscape. > > Requested reviews: > Inkscape Developers (inkscape.dev) > Related bugs: > Bug #792263 in Inkscape: "Do not include individual GTK+ headers" > https://bugs.launchpad.net/inkscape/+bug/792263 > > For more details, see: > https://code.launchpad.net/~valavanisalex/inkscape/fix-792263/+merge/63364 > > I've gone through the code and replaced all gdk/gtk headers with generic headers in preparation for an eventual move to gtk+ 3. See http://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html#id1391340 for details. > > I have made sure that the code compiles with GTK_DISABLE_SINGLE_INCLUDES defined. > > It's quite a big diff, affecting many files so I don't feel comfortable committing it to trunk straight away. Please could someone take a look, and consider merging? > > Thanks Ah, yes. The change-to-really-slow-down-compile-time-and-break-modularity include mess GTK has doubled down on. :-( Thanks for slogging through the effort to get this together. I'll be going over it and hopefully getting it in soon. (I know I'd been procrastinating since the poor architectural choice has just grated on me, but we do need to get this resolved). BTW, we only just this past few weeks bumped Inkscape up to require GTK 2.20 for building, so it might be a fair bit more before we make a 3.x push overall. The header fix does help, though.

1 0

How to get path label/id
by Skinner, Ralph 03 Jun '11

03 Jun '11

Hi, I'm writing a Live Path Effect, and I'm trying to get the label and/or id of the path to which the effect is being applied. I tried this in the 'doEffect' method: Effect::doEffect_pwd2 (Geom::Piecewise<Geom::D2<Geom::SBasis> > const & pwd2_in) { LivePathEffectObject *myLPE = (LivePathEffectObject*)this->getLPEObj(); myLPE->defaultLabel(); ... ...but of course this returns the label of the path effect, not the path itself. Any suggestions? Thanks! "Misys" is the trade name for Misys plc (registered in England and Wales). Registration Number: 01360027. Registered office: One Kingdom Street, London W2 6BL, United Kingdom. For a list of Misys group operating companies please go to http://www.misys.com/corp/About_Us/misys_operating_companies.html. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys plc. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.

2 2