June 2006 - Inkscape Devel - Inkscape Mailman

[Inkscape-tester] inkscape build report
by Bryce Harrington 19 Jun '06

19 Jun '06

Was there a change in the build system recently? The test system is seeing a bunch of warnings with one of the compiler options... ----- Forwarded message from root <root@...1070...> ----- Date: Mon, 19 Jun 2006 05:22:32 -0700 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Mon Jun 19 05:11:04 2006 (Run 3630) Snapshot: inkscape-20060619-0400.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 35 0 Test Status Score Info ------------------------------------------------------------------------ make check PASS 19/19 == Errors == none == Warnings == selection-chemistry.cpp:1880: warning: statement has no effect sp-flowtext.cpp:339: warning: 'sp_item_bbox_desktop' is deprecated (declared at sp-item.h:229) sp-shape.cpp:672: warning: 'sp_item_bbox_desktop' is deprecated (declared at sp-item.h:229) sp-text.cpp:486: warning: 'sp_item_bbox_desktop' is deprecated (declared at sp-item.h:229) display/canvas-arena.cpp:85: warning: invalid access to non-static data member 'SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:85: warning: (perhaps the 'offsetof' macro was used incorrectly) display/sp-canvas.cpp:132: warning: invalid access to non-static data member 'SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:132: warning: (perhaps the 'offsetof' macro was used incorrectly) cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C cc1: warning: command line option "-Wno-invalid-offsetof" is valid for C++/ObjC++ but not for C == Unit Tests == PASS: test-all PASS: style-test PASS: display/bezier-utils-test PASS: helper/units-test PASS: libnr/in-svg-plane-test PASS: libnr/nr-matrix-test PASS: libnr/nr-point-fns-test PASS: libnr/nr-rotate-test PASS: libnr/nr-rotate-fns-test PASS: libnr/nr-scale-test PASS: libnr/nr-translate-test PASS: libnr/nr-types-test PASS: libnr/test-nr PASS: removeoverlap/remove_rectangle_overlap-test PASS: svg/test-svg PASS: util/list-container-test PASS: xml/test-xml PASS: xml/quote-test PASS: xml/repr-action-test _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

Re: [Inkscape-devel] [Inkscape-tester] New translations we need?
by Ben Fowler 19 Jun '06

19 Jun '06

On 19/06/06, matiphas@...8... <matiphas@...8...> wrote: > Hi Ben Guessing that an on-list reply is OK ... .>[ snip ] > PS yes, porting poedit on macOSX would be valuable. Today's checkout of poedit builds just fine on the Mac. I've now only got to work out how to use it! Ben

1 0

trying to get Inkscape 0.44pre work on SuSE
by Tuukka Pasanen 19 Jun '06

19 Jun '06

Hi, Is there some trick to make Inkscape 0.44pre4 work on SuSE 10.1? I compiled it from sources and now I can't get it working (SIGSEGVs). I looked from sources and gdb it and find out it's something to do with UTF-8. Some one got clue how to make this work?? Tuukka

2 3

Color Cursors
by Joshua A. Andler 19 Jun '06

19 Jun '06

Hey all, The initial commit of color cursors is in... at this point it still needs to read from svg as opposed to pixbufs, and it will also need to be optional for color vs b&w (per bbyak). For note, this does gracefully get around the win2000 issue we had last time (it just falls back on the b&w xpms). I probably won't touch this again for the next few days, but I figured I'd be the first to commit in the reopened trunk. ;) Now to go finish the tutorial and screenshot stuff. I will add the New Feature post when it's complete. :) -Josh

1 0

Freeze Lifted; Inkscape 0.44 Branched
by Bryce Harrington 18 Jun '06

18 Jun '06

Development for 0.45 may resume on the main Inkscape subversion tree. :-) Aaron Spike has created the 0.44 release branch, and him and Jon soon give blessing to the release itself, so that we can begin announcements. Soon all the anticipation will be done! As mentioned previously, we also plan to create a series of stable releases, starting with 0.44.1. Presumably we can expect these every couple weeks or so. We also hope to have 0.45 out within a couple months. Any outstanding branches or patches that we postponed during 0.44 should be merged into HEAD. It's a good idea to pace yourself with these merges so it'll be easier to sort out conflicts. Bryce

1 0

inkscape rpm and libexpat
by Ralf Stephan 18 Jun '06

18 Jun '06

Hello, I thought I'd try to install our inkscape rpm on SuSE 10.1 but this is not possible out of the box, we rely on an old version of the expat library, the rpm needs libexpat.so.0, while SuSE ships version so.1. >From a look at rpmfind.net, the switch to .so.1 happened with version 2.0 and SuSE are the first and only to have this. How do we handle this case? Link to an older rpm ? ralf

1 0

Win32 lib bundle
by Bob Jamison 17 Jun '06

17 Jun '06

Hi all, Adib informed me of a dependency bug that one user experienced, where Python would not run because it depends on msvcr71.dll. We currently add msvcr70.dll to the Inkscape package, but apparently not everyone has 7.1. So I made another lib bundle that adds the newer dll. I also included bugfix updates of GLib and Cairo. It is here: http://inkscape.modevia.com/win32libs/gtk28-060617.7z I suggest that for this release we supply both dlls, just to be on the safe side. DLLs dont do versions like Unix. The exact file name must be found. bob

1 0

Inkscape 'breaks' SVG
by Ruud Steltenpool 17 Jun '06

17 Jun '06

Inkscape is implemented as if things that render the same (or just similar even) are the same too, thereby destroying clean code. Which is wrong and makes it near useless for coders, heavily frustrating the number 1 strong point of SVG: letting coders and clickers cooperate. If i use Inkscape for adjusting 1 thing, i want the SVG code of only that 1 thing to change, not have lots of my SVG code changed just because of some internal representation or convenience for the Inkscape implementors. 4 lines together visually forming a square, is not the same as a real square. A name/value attribute pair can sometimes by SVG specification be replaced with some CSS, but even that makes a difference in semantics. And with SVG support usually being partial, it often also makes a difference in rendering. Cheers, Ruud http://svg.startpagina.nl

7 7

[Fwd: Fwd: Call for screenshots]
by Aaron Spike 17 Jun '06

17 Jun '06

-------- Original Message -------- Subject: Fwd: Call for screenshots Date: Fri, 16 Jun 2006 20:43:36 -0300 From: bulia byak <buliabyak@...400...> To: Aaron Spike <aaron@...749...> References: <3c78ff030606151411x6334770dp2e1a0a26c4d8a216@...401...> Aaron, I sent this to devel and user lists, but gmail is spamblocked again so it bounced. Can you please forward it to both lists on my behalf? Thanks! ---------- Forwarded message ---------- From: bulia byak <buliabyak@...400...> Date: Jun 15, 2006 6:11 PM Subject: Call for screenshots To: Inkscape ML <inkscape-devel(a)lists.sourceforge.net>, Inkscape User Community <inkscape-user(a)lists.sourceforge.net>, Bob Jamison <rjamison@...357...> We need more screenshots of 0.44 release for our gallery: http://inkscape.org/screenshots/index.php. So far we only have 6. One feature I would especially like to get more screen space is the docked palette with the new default color set. For a user, screenshots are perhaps the most important resource at inkscape.org. It's what most people look at first. New users don't like to read descriptions; they want pretty pictures. Existing users considering upgrade don't like to read release notes; they want pretty pictures. Besides, our screenshots are borrowed by a lot of other sites and thus end up all over the web. All this means that screenshots must be as good as Inkscape itself, if not better. The lack or poor quality of screenshots means the entire project's bad health. What makes a good screenshot? * The best "feature screenshots" are made by the author of the corresponding feature. Nobody knows the feature better than him/her. In fact, if you contribute a major feature, you are pretty much supposed to submit a screenshot of it in action, much as you are supposed to describe it in release notes. [Note to Bob: Can you please make a good screenshot with several different examples of SIOX at work?] * However, we also need high quality "work screenshots" showing professional Inkscape work. If you are doing something complex and/or artistic and it turns out well, please take a moment to shoot the Inkscape window with your work. * Use PNG format (not JPG or GIF). * The screenshot should be dense and informative. 1280x1024 (the preferred screenshot size) is a lot of space, so don't waste it on just one or two bits. When doing a feature screenshot, combine the various aspects of the feature, add captions and descriptions, demonstrate all relevant tricks and nontrivial things that you can think of. When doing a work screenshot, find the best zoom/view of the document, and consider doing a double view of the same or different documents (as here: http://inkscape.org/screenshots/gallery/inkscape-0.41-CVS-linux-davinci.png). In both cases, open the relevant dialogs, switch to relevant tools, and do a selection so that the statusbar message adds more useful info to the picture. * When submitting a screenshot, please also submit a blurb (one-paragraph description) that will accompany it in the gallery. Briefly describe the feature you are demonstrating and the most nontrivial aspects of the screenshot. Try to be witty but comprehensive. * Also indicate what the usage terms are for the screenshot (in case magazine writers wish to use the screenshot in their articles). We recommend that you place your screenshots in public domain, as it saves a lot of hassle in asking for and obtaining permissions. To submit, please mail a link to your file to the devel list, or directly to buliabyak at gmail dot com. All this is quoted from a wiki page I wrote some time ago: http://wiki.inkscape.org/wiki/index.php/MakingScreenshots -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

Missing Russian dialog image
by Jon A. Cruz 17 Jun '06

17 Jun '06

The tutorial-tracing.ru.svg that's in the latest set of tutorial updates in a patch (#1506381) is missing the potrace-ru.png shot of the dialog. We have potrace.png, potrace-de.png and potrace-fr.png. If someone could attach a potrace-ru.png to the patch, that would let me commit it. Thanks http://sourceforge.net/tracker/? func=detail&aid=1506381&group_id=93438&atid=604308

2 1