- Inkscape Devel - Inkscape Mailman

problems when opening file from 0.47 in 0.48
by Rafael Z. Frantz 19 Aug '10

19 Aug '10

Hi all, I'm testing the 0.48 version and I've noticed that when opening an svg file created in version 0.47 in 0.48, some elements (arrows, in this specific case) that I had grouped with a main figure with other elements (rectangles, circles, etc..), now the arrows appears far away from the main figure in the canvas. Is that any known issue or problem ? Best regards, Rafael Z. Frantz PhD Student University of Sevilla - Spain http://www.tdg-seville.info/rzfrantz *Guaraná *for Enterprise Application Integration http://www.tdg-seville.info/rzfrantz/guarana Seeking for a paper? Try TDG Scholar at http://scholar.tdg-seville.info

3 3

GSOC spatial indexes
by Vangelis Katsikaros 19 Aug '10

19 Aug '10

Hi everyone I worked on the spatial indexes GSOc project, and made progress but unfortunately the last month has been quite problematic, due to external issues (nothing to do with GSOC or programing). So, I won't be able to deliver the project completed in time. However, I will continue the work (after a small break). I want it to be available for the 0.49 release and I hope that I'll have results by mid to end September. I'll soon upload the work I've done so far. Regards Vangelis __________________________________________________ ×ñçóéìïðïéåßôå Yahoo!; ÂáñåèÞêáôå ôá åíï÷ëçôéêÜ ìçíýìáôá (spam); Ôï Yahoo! Mail äéáèÝôåé ôçí êáëýôåñç äõíáôÞ ðñïóôáóßá êáôÜ ôùí åíï÷ëçôéêþí ìçíõìÜôùí http://mail.yahoo.gr

2 1

Cannot compile on XP since rev. 9698
by Preben Soeberg 18 Aug '10

18 Aug '10

Make error line 299: problem compiling: src/ui/dialog/filedialogimpl-win32.cpp: In function 'int Inkscape::UI::Dialog::<unnamed>::sanitizeWindowSizeParam(int, int, int, int)': src/ui/dialog/filedialogimpl-win32.cpp:103: error: 'lower' was not declared in this scope src/ui/dialog/filedialogimpl-win32.cpp: At global scope: src/ui/dialog/filedialogimpl-win32.cpp:100: warning: unused parameter 'minimum' Regards Preben

2 1

Win32 Inkscape trunk build : gomp not found
by Yann Papouin 18 Aug '10

18 Aug '10

Hi, I'm trying to build Inkscape trunk on Win32, I have an issue on the link step, I'm using latest devlibs from launchpad: ##### link objects and library to create executable --- link / rc --- link / link ============ cmd ============ mingw32-g++ -o build/inkscape.exe -mwindows -mthreads build\inkres.o build\obj\main.o build\obj\winmain.o build\libinkscape.a -LC:\devlibs/lib -LC:\devlibs/lib -lpoppler -LC:\devlibs/lib -lpoppler-glib -LC:\devlibs/lib -lgobject-2.0 -LC:\devlibs/lib -lglib-2.0 -lintl -LC:\devlibs/lib -lgdk-win32-2.0 -LC:\devlibs/lib -lgdk_pixbuf-2.0 -LC:\devlibs/lib -lpangowin32-1.0 -lgdi32 -LC:\devlibs/lib -lpango-1.0 -LC:\devlibs/lib -lpangocairo-1.0 -LC:\devlibs/lib -lcairo -LC:\devlibs/lib -lpoppler -LC:\devlibs/lib -lgtkmm-2.4 -LC:\devlibs/lib -lglibmm-2.4 -LC:\devlibs/lib -lgobject-2.0 -LC:\devlibs/lib -lglib-2.0 -lintl -LC:\devlibs/lib -lsigc-2.0 -LC:\devlibs/lib -lgiomm-2.4 -LC:\devlibs/lib -lgio-2.0 -LC:\devlibs/lib -lgdkmm-2.4 -LC:\devlibs/lib -lpangomm-1.4 -LC:\devlibs/lib -lgdk-win32-2.0 -LC:\devlibs/lib -lgdk_pixbuf-2.0 -LC:\devlibs/lib -lpangowin32-1.0 -lgdi32 -LC:\devlibs/lib -lpango-1.0 -LC:\devlibs/lib -lpangocairo-1.0 -LC:\devlibs/lib -lcairo -LC:\devlibs/lib -lcairomm-1.0 -LC:\devlibs/lib -latkmm-1.6 -LC:\devlibs/lib -latk-1.0 -LC:\devlibs/lib -lgtk-win32-2.0 -LC:\devlibs/lib -lgdk-win32-2.0 -LC:\devlibs/lib -lpangoft2-1.0 -LC:\devlibs/lib -lpango-1.0 -LC:\devlibs/lib -lglib-2.0 -lintl -LC:\devlibs/lib -lfreetype -LC:\devlibs/lib -lfontconfig -LC:\devlibs/lib -lgthread-2.0 -LC:\devlibs/lib -lglib-2.0 -lintl C:\devlibs/bin/libxml2.dll C:\devlibs/bin/libxslt.dll -LC:\devlibs/lib -lcairo -LC:\devlibs/lib -lcairomm-1.0 -LC:\devlibs/lib -lcairo -LC:\devlibs/lib -lwpg-0.1 -LC:\devlibs/lib -lwpd-0.8 -LC:\devlibs/lib -lwpg-stream-0.1 -LC:\devlibs/lib -lwpd-0.8 -liconv -LC:\devlibs/lib -lMagick++ -LC:\devlibs/lib -lMagickCore -LC:\devlibs/lib -lfontconfig -LC:\devlibs/lib -lfreetype -LC:\devlibs/lib -llcms -LC:\devlibs/lib -lgsl -lgslcblas -lm -lpng -ljpeg -ltiff -lpopt -lz -lgc -lws2_32 -lintl -lgdi32 -lcomdlg32 -lm -lgomp -lpthreadGC2 -laspell -lmscms ============================= Make error line 479: LINK problem: c:/mingw/bin/../lib/gcc/mingw32/4.5.0/../../../../mingw32/bin/ld.exe: ne peut trouver -lgomp collect2: ld returned 1 exit status following is my build.bat set DEVLIBS_PATH=C:\devlibs set MINGW_PATH=C:\MinGW set PKG_CONFIG_PATH=C:\devlibs\lib\pkgconfig btool Any idea ?

3 3

Bug #569238 “[dbus] get_desktop_new returns nothing”
by ~suv 18 Aug '10

18 Aug '10

a) Has anyone using the dbus API since it was merged with trunk noticed a regression with "desktop_new"? According to bug #569238 [1] "desktop_new no longer returns nil, it now times out. light testing with rectangle crashes inkscape (...)" (reported with current trunk built on fedora 13, dbusapi enabled) b) Related to the dbus API docs - would it be possible to make the documentation available on the Inkscape Wiki? Not every platform has the tools installed to build it using 'dbus/builddocs.sh' (e.g. on osx the list of (otherwise unneeded) dependencies in order to install 'xmlto' via MacPorts is huge) - yet users might be interested to read more about it. ~suv [1] https://bugs.launchpad.net/bugs/569238

2 1

Inkscape 0.48 tagged and rolled -- Please don't announce
by Ted Gould 16 Aug '10

16 Aug '10

Howdy, So I've tagged and rolled the 0.48 release. Just as a reminder, please don't announce this widely as we want to let binary packagers get a chance to have binaries ready when people start rushing to pull down a copy. == Downloads == https://sourceforge.net/projects/inkscape/files/inkscape/0.48/ == SHA1 Sums == a2ab9b34937cc4f2b482c9b3720d8fd4dc7b12e8 inkscape-0.48.0.tar.bz2 220ade981069a91d3afab9cbff75f65c75119da2 inkscape-0.48.0.tar.gz df32c39dfdb2072bf32ff71e7293c6bb84a53e26 inkscape-0.48.0.zip == MD5 Sums == fd8b17a3f06668603807176a77167bb9 inkscape-0.48.0.tar.bz2 bb94543b813157d83281657a89465d46 inkscape-0.48.0.tar.gz 26318c26b056be7813e3ea06a8244b88 inkscape-0.48.0.zip This is a pretty cool release, I'm excited about it. Thanks to everyone who contributed! --Ted

3 4

status of git repository at <http://git.inkscape.org>?
by ~suv 15 Aug '10

15 Aug '10

During the last year several people asked on #inkscape (irc) about the git repository <git://git.inkscape.org/projects/inkscape.git> and its current state (the git-daemon seems to be down, the archive a mirror of an old SVN revision from sf.net). Are there plans to revive this repository or shouldn't it be taken off-line to avoid confusion? ~suv

1 0

UniConvertor update for 0.48 on Windows
by Krzysztof Kosiński 13 Aug '10

13 Aug '10

Hello After some cowboy patching and hacking MinGW includes I managed to update UniConvertor to version 1.1.5 in the Windows devlibs (r18). The attached fix is required for the 0.48 branch in order to work properly with the updated UniConvertor; I have committed it to trunk already. I guess this was the last blocker issue for 0.48, so let's get on with releasing! Regards, Krzysztof

4 4

Fwd: Re : Inskape 0.48pre1 - Error message when saving as wmf
by Igor Novikov 13 Aug '10

13 Aug '10

On Thu, Jul 8, 2010 at 6:14 PM, bulia byak <buliabyak@...400...> wrote: > 2010/7/8 Nicolas Dufour <nicoduf@...48...>: > > 1. Removing the Uniconvertor scripts from the devlibs. UniConvertor > import or export scripts warn users to install UniConvertor manually (and > give the site address) when the libs are missing. (Note to self: fix the > gettext import bug in uniconv_output.py...). > > I think that will be perceived as a regression. Lots of formats that > used to work will suddenly stop working. We had a lot of pain with > displaying messages like this - most people simply perceive any such > message as an error and complain or give up without reading. Those who > read it and act on it will be a minority. > >From other side a lot of win32 users ask us "Why you announce XXX feature but i have not this in Inkscape?". We cannot synchronize our project development cycles, it's normally. But we could provide for user a way updating UniConvertor. External UniConvertor installation is a best solution because current bundle updating is a task rather for programmer than for conventional user/designer. > What's such a big problem with including a new UC into devlibs? > Actually there are not impossible tasks. It's just a subject of additional development time and resulted bundle size. Latest version has several new native extensions and more complex structure. And in next versions we will add new native resources because users ask for more and more complex features. As a simple solution we can provide for users an Inkscape-0.48-with-UniConvertor.zip archive with Inkscape installer, UniConvertor MSI and small REAME file inside. To simplify UniConvertor download the best way is not a message "You need downloading from bla-bla-bla site..." but just a button "Download" which opened browser on required page. Last option is for those users who download Inkscape exe installer only. Another valuable reason is planned preferences for translation. We are going provide a lot of translation options (we already have the code but we still not expose it as a command line options) and naturally such preferences could be managed better from GUI than command line. So we will add preferences dialogs for each format into UniConvertor. It's not an easy task so for Inkscape team will be better utilizing ready dialogs from UniConvertor than creating the same but on Inkscape side. And as I have wrote UniConvertor translation progress dialog would be also a good additional feature for Inkscape. Regards, Igor Novikov sK1 Project http://sk1project.org

7 19

Inkscape 0.48 status
by Joshua A. Andler 13 Aug '10

13 Aug '10

Hey All, 0.48 is wrapped up now code-wise... we got that Save As dialog issue on win32 fixed, uniconvertor on win32 is up to date, we also got 3 last minute Connector Tool crash fixes. I've requested that Ted cut the tarball, so once we have that the packagers can begin their work. I will only be available through next Sunday (22nd) to work on the release due to the upcoming surgery, and from the sound of things, probably won't be back anytime soon. I think we have more than enough time to get this done. Jon: Please update your stuff in the release notes. Cheers, Josh

1 0

svg open 2010, again
by Alexandre Prokoudine 12 Aug '10

12 Aug '10

Hi, Is anybody apart from Tav going to SVG Open 2010? :) Alexandre Prokoudine http://libregraphicsworld.org

1 0

Re: [Inkscape-devel] more UI mockups :)
by Valerie 12 Aug '10

12 Aug '10

> > This time UI mockups come from Pablo Lizardo: > > > > http://www.flickr.com/photos/pablolizardo/4845828488/in/photostream/ > > http://www.flickr.com/photos/pablolizardo/4845888941/in/photostream/ > > Apart from it being a clear Photoshop rip-off, it's not very much > different from our current interface. Except that Fill&Stroke is all > dumped into a single pane, losing many options along the way. > > Curiously, Photoshop had acquired a horizontal top panel with tool > options much later than other software, and I think even later than > Inkscape had it. And now we are urged to imitate Photoshop even in > that element. Familiarity so utterly trumps usability that it's not > even funny. Well, it seems you're looking more at the top panels while some of us are more focused on other parts. :) I didn't pay attention to the top panel until you mentioned it. Every mock-up will likely have its good parts and bad parts. Here's what I do like in these mock-ups: 1. The layer panel I like the arrangement, it makes efficient use of space but gives you information about a layer at just a glance. It just needs a slider to pop up besides the numerical value when clicked to adjust opacity more easily. I think the view button could be moved to the far left though to avoid accidentally clicking on the lock button. 2. Parts of the fill and stroke panel Of course, options will have to be restored, but there are elements I do think are interesting: a. The stroke/fill button I suppose when you click on the hollow square, the hollow square is brought to the forefont and you're basically editing your stroke color now, and vice-versa? I think this kind of preview is kind of neat. Of course, the options he removed will have to be brought back in. b. I like the more compact view for caps and markers, though some options are missing now. I wouldn't mind seeing something like this at the bottom: http://j.imagehost.org/view/0548/stroke For those who absolutely Need the names, the name could always pop up when you hover over it. I'm not so sure about the other proposed changes, but I did find these to be nice ideas. Right now I avoid using the fill and stroke panel whenever I can because it's a pain to navigate (too many tabs), something more compact may be nicer.

2 1

SpamBlacklist not working
by unknown＠example.com 12 Aug '10

12 Aug '10

I tried to revert the last edit to http://wiki.inkscape.org/wiki/index.php/MicrosoftVisio and the wiki responded to the Save page with: Warning: file(/var/www/wiki.inkscape.org/htdocs/extensions/SpamBlacklist/wikimedia_b… [function.file]: failed to open stream: No such file or directory in /var/www/wiki.inkscape.org/htdocs/extensions/SpamBlacklist/SpamBlacklist_body.php on line 97 Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /var/www/wiki.inkscape.org/htdocs/extensions/SpamBlacklist/SpamBlacklist_body.php on line 97 Warning: array_map() [function.array-map]: Argument #2 should be an array in /var/www/wiki.inkscape.org/htdocs/extensions/SpamBlacklist/SpamBlacklist_body.php on line 102 Warning: array_filter() [function.array-filter]: The first argument should be an array in /var/www/wiki.inkscape.org/htdocs/extensions/SpamBlacklist/SpamBlacklist_body.php on line 102

1 0

more UI mockups :)
by Alexandre Prokoudine 11 Aug '10

11 Aug '10

Hi, This time UI mockups come from Pablo Lizardo: http://www.flickr.com/photos/pablolizardo/4845828488/in/photostream/ http://www.flickr.com/photos/pablolizardo/4845888941/in/photostream/ Alexandre Prokoudine http://libregraphicsworld.org

4 4

Crashes
by Joshua A. Andler 11 Aug '10

11 Aug '10

Hey All, It seems like a decent number of tweets and complaints I've seen around the community (understandably) are about inkscape crashing. Doing basic searches for bugs tagged w/ crash gives the following info: All statuses is over 200 bugs and Confirmed or In Progress have 84. 84 crash bugs that can be reproduced seems unreasonably high for something intended for production work and code-wise there's a chance that some are caused by shared underlying issues. If anyone is interested in taking a look into these to see if there are any you might be able to fix, that would be awesome. http://bit.ly/InkCrash Cheers, Josh

4 12

Release Notes for 0.48: Connectors and Swatches
by Tavmjong Bah 09 Aug '10

09 Aug '10

Hi, There appears to be nothing in the release notes about the new Connector Tool additions. The Swatches section needs to be expanded with an explanation of how to use them. Why is a linear gradient created when clicking on the Swatches icon in the Fill and Stroke dialog? Tav

4 3

3D Box and 0.49
by Krzysztof Kosiński 08 Aug '10

08 Aug '10

Hello 3D Box is the main thing that prevents us from fixing the coordinate system bug. (The second thing are guides, but they're much easier to fix.) The reason is that it has a design fault - it stores perspectives and faces in desktop coordinates. A simple Y inversion does not fix the problem, because some code (e.g. default face coloring) is dependent on the chirality of the 3D coordinate system, and flipping the Y axis inverts the chirality. There's also a slew of other bugs related to 3D box in our bug tracker. What do we do with it in 0.49? I would really like to see the coordinate system bug fixed in 0.49, even if it means rewriting the 3D box from scratch, or even disabling it. Fancy features aren't very useful if we don't get the basics right. The issue of supporting legacy documents with 3D boxes is separate and I think it can be done if the 3D box gets rewritten first. We would just need to fix the document at load time. Initially I wanted to do this by direct XML manipulation before creating the SP tree, but now I see this has limitations - compatibility code at SP level is probably a better idea. Regards, Krzysztof.

2 1

inkscape aqua new build (-: PPC only )-:
by Drechsel Wolf 08 Aug '10

08 Aug '10

Hi everybody, as I upgraded my system to Mac OS X 10.5 "Leopard", I tried a new build of inkscape for native Mac OS X - called "aqua". Building didnt cause a lot of trouble, daring fellows can get it here: http:// verkehrsplanung.com/Inkscape-r9689-10.5+-PPC.dmg Attn.: It ist PPC only - dont waste your time, if you have an Intel machine. I couldnt do a lot of testing - but it looks as if it works quite nicely, but most of the well-known aqua bugs are maintained. To my feeling, it should not be so much work to get a really useable inkscape aqua - and I assume that many mac people would be happy with it. Sorry - I cannot do any coding - but will be happy to build and test everything. If somebody happens to have some spare time, he could have a look at: http://gtk-osx.sourceforge.net/ ige-mac-integration/GtkOSXApplication could be one topic to begin with. Else: Here is my bug-list - most of them are aqua-related: https://bugs.launchpad.net/~drechsel I'll continue praying every bedtime for a mac developer to care for inkscape aqua … (-; Greetings, Wolf Yours, Wolf

1 0

How to manage hundreds of bugs found by static analysis of Inkscape source?
by Vaughn Spurlin 05 Aug '10

05 Aug '10

I've used Coverity's static source code analysis tools to identify hundreds of bugs in Inkscape source. I'd like some guidance on the best way to contribute bug report details and proposed fixes to Inkscape. I'm a relatively new Coverity employee getting up to speed with our static analysis tools for identifying defects. Inkscape was recommended as an open source project with C/C++ source that I could use to satisfy my educational needs while contributing to an open source project. I want to contribute code fixes along with bug details. I suggest a first pass to report as many bugs as I can to the Inkscape Bug Tracker, followed by a second pass to add suggested fixes. Then Inkscape developers with commit privileges can review my code fix suggestions and apply the fixes as they see fit. Once the first pass is done and bug details are visible to the community, anyone else is welcome to contribute fixes also. What process should we follow to make the best use of everyone's efforts by avoiding several people working on the same bug? What I'm requesting at this point is a discussion about my suggestions, and some decisions about how best to proceed. As an example, here's one defect found by Coverity analysis, with my proposed code fix. CONSTANT_EXPRESSION_RESULT in /inkbugs/inkscape/src/main.cpp In sp_do_export_png(SPDocument *...): An operation with non-constant operands that computes a result with constant value (CWE-569). 1345 if (sp_export_area) { 1346 /* Try to parse area (given in SVG pixels) */ 1347 gdouble x0,y0,x1,y1; !sscanf(sp_export_area, &"%lg:%lg:%lg:%lg", &x0, &y0, &x1, &y1) == 4 is always false regardless of the values of its operands (logical operand of if). 1348 if (!sscanf(sp_export_area, "%lg:%lg:%lg:%lg", &x0, &y0, &x1, &y1) == 4) { 1349 g_warning("Cannot parse export area '%s'; use 'x0:y0:x1:y1'. Nothing exported.", sp_export_area); 1350 return; 1351 } fix noted 2010-07-25: 1348 if (sscanf(sp_export_area, "%lg:%lg:%lg:%lg", &x0, &y0, &x1, &y1) != 4) { fix reason: sscanf returns the number of strings successfully scanned. The intent here is to ensure that all 4 input strings were scanned successfully. Vaughn Spurlin Coverity Technical Support

9 11

problem mit linien
by Christoph Grün 04 Aug '10

04 Aug '10

Hallo! Ich verwende Inkscape 0.47. Bei Inkscape 0.47 habe ich Probleme mit Linien. Sobald ich eine Linie dupliziere und mit der Maus/Pfeiltasten positionieren möchte, springt die Linie zu einer beliebigen XY Position auf dem Zeichenfenster. Es ist hierauf nicht mehr möglich, diese zu positionieren, auch bei Neustart von Inkscape ist das Problem vorhanden. Hat jemand dasselbe Probleme bzw. einen Lösungsvorschlag? Danke, Christoph

4 3

Problem compiling rev.9683
by LucaDC 04 Aug '10

04 Aug '10

On Windows XP SP3 I get this error while compiling: 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*)' Of course, changing the definition: > myEnhMetaFileProc(HDC /*hDC*/, HANDLETABLE * /*lpHTable*/, ENHMETARECORD > const *lpEMFR, int /*nObj*/, LPARAM lpData) into > myEnhMetaFileProc(HDC /*hDC*/, HANDLETABLE * /*lpHTable*/, ENHMETARECORD > *lpEMFR, int /*nObj*/, LPARAM lpData) (taking away the 'const') fixed the problem but I'm not sure this is what was intended. Regards Luca -- View this message in context: http://old.nabble.com/Problem-compiling-rev.9683-tp29342879p29342879.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.

4 5

FW: [cairo] EPS target: force boundingbox
by unknown＠example.com 04 Aug '10

04 Aug '10

Hi all, I sent a mail to Cairo's maillist about this issue: https://bugs.launchpad.net/inkscape/+bug/380501 Adrian Johnson provided a patch for Cairo that seems to solve our problem. How to proceed? Thanks, Johan > -----Original Message----- > From: Adrian Johnson [mailto:ajohnson@...1679...] > Sent: Tuesday, August 03, 2010 06:52 > To: Engelen, J.B.C. (Johan) > Cc: cairo@...278... > Subject: Re: [cairo] EPS target: force boundingbox > > On 16/07/10 21:47, J.B.C.Engelen@...1578... wrote: > >> -----Original Message----- > >> From: Adrian Johnson [mailto:ajohnson@...1679...] > >> Sent: 16 July 2010 14:00 > >> To: Engelen, J.B.C. (Johan) > >> Cc: cairo@...278... > >> Subject: Re: [cairo] EPS target: force boundingbox > >> > >> Cairo does not provide any means to override the automatically > >> generated BoundingBox comment. > > > > In that case, I want to file a feature request to either disable > > automatic calculation of boundingbox, or to provide a means to > > override it. > > Where should I file our request? > > > > Thanks, > > Johan > > The attached patch allows the cairo generated %%BoundingBox > and %%PageBoundingBox comments to be overridden using the > cairo_ps_surface_dsc_comment() API. > > eg > > surface = cairo_ps_surface_create() > cairo_ps_surface_dsc_comment(surface, %%BoundingBox: 100 100 > 200 200"); cairo_ps_dsc_begin_page(surface); > cairo_ps_surface_dsc_comment(surface, %%PageBoundingBox: 100 > 100 200 200"); > > Please test to see if this meets your requirements. >

4 4

New feature: Exchange position of selected objects
by Nicolas Dufour 03 Aug '10

03 Aug '10

Hi all, The patch provided in Bug #171944 "Exchange position of selected objects" (https://bugs.edge.launchpad.net/inkscape/+bug/171944) by Roland Meub is now in the trunk (committed revision 9681). It adds three buttons in the Align and Distribute dialog (rearrange group) that exchange the selected objects position: 1. according to the selection order, 2. according to the stacking order, and 3. clockwise. Please test and comment. Regards, -- Nicolas

1 0

About Documentation
by Ivan Moreno 02 Aug '10

02 Aug '10

Hello, I downloaded the source code some time ago, and after some time reading, I still don't understand how it works from a general POV. Is a ".txt" with some paragraphs ( the last date of update from which is unknown i think) enough for such a large software? Wouldn't be better if some better explanation about it's structure, more than "there are two trees somewhere, one of them agnostic", was written, so more people could get into developing? Or is it just me, that i'm so noob, because the program is quite trivial? Thanks

3 2

After the dbus api merge, trunk (9614) fails to build on osx
by ~suv 31 Jul '10

31 Jul '10

1) make error due to hardcoded 'libtoolize' in autogen.sh > $ make > CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /Volumes/blue/src/Inkscape/src/inkscape-repo/mp-x11/missing --run aclocal-1.11 > cd . && /bin/sh /Volumes/blue/src/Inkscape/src/inkscape-repo/mp-x11/missing --run automake-1.11 --foreign > configure.ac:33: required file `./ltmain.sh' not found > make: *** [Makefile.in] Error 1 On OS X libtool and libtoolize are installed as 'glibtool' and 'glibtoolize'. autogen.sh should either test for it or maybe use the environment variables ($LIBTOOL, $LIBTOOLIZE) which could be set in the packaging script (packaging/macosx/osx-build.sh). After editing autogen.sh (replace "libtoolize" with "glibtoolize") to test the fix, autogen.sh and configure ran through: > Configuration: > > Source code location: . > Destination path prefix: /Volumes/blue/src/Inkscape/src/inkscape-repo/mp-x11/packaging/macosx/../../Build > Compiler: ccache g++ > CPPFLAGS: -Wall -Wformat -Wformat-security -W -D_FORTIFY_SOURCE=2 -I/Volumes/blue/mp-inkscape/with-a-long-long-long-directory-name/include > CXXFLAGS: -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -O3 -Wall -Wno-strict-aliasing > CFLAGS: -Wno-pointer-sign -O3 -Wall > LDFLAGS: -L/Volumes/blue/mp-inkscape/with-a-long-long-long-directory-name/lib > > Use Xft font database: yes > Use gnome-vfs: yes > Use openoffice files: yes > Use relocation support: no > Internal Python: skipped > Internal Perl: skipped > Enable LittleCms: yes > Enable DBUS no > Enable Poppler-Cairo: yes > ImageMagick Magick++: yes > Libwpg: yes > Doing Local Install: no but make failed later on with: 2) link error for 'libinkdbus.la' > CCLD libinkdbus.la > Undefined symbols: ... > ld: symbol(s) not found > collect2: ld returned 1 exit status > make[3]: *** [libinkdbus.la] Error 1 > make[2]: *** [all] Error 2 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 Any hints on how one can really disable DBUS in Inkscape for now or how to investigate if this is a problem with my local build environment (dbus, dbus-glib dependencies are installed [2]) or why this error happens on osx would be highly appreciated. ~suv [1] from the console log building bzr trunk 9614: > LeWitt:mp-x11 suv$ make > make all-recursive > Making all in src > dbus-binding-tool --mode=glib-server --output=extension/dbus/application-server-glue.h --prefix=application_interface extension/dbus/application-interface.xml > dbus-binding-tool --mode=glib-server --output=extension/dbus/document-server-glue.h --prefix=document_interface extension/dbus/document-interface.xml > dbus-binding-tool --mode=glib-client --output=extension/dbus/document-client-glue.h --prefix=document_interface extension/dbus/document-interface.xml > make all-am > CXX arc-context.o > ... > > CXX extension/print.o > CXX extension/dbus/dbus-init.o > extension/dbus/dbus-init.cpp:71: warning: unused parameter ‘proxy’ > extension/dbus/dbus-init.cpp: In function ‘void Inkscape::Extension::Dbus::init()’: > extension/dbus/dbus-init.cpp:87: warning: unused variable ‘obj’ > extension/dbus/dbus-init.cpp: In function ‘gchar* Inkscape::Extension::Dbus::init_document()’: > extension/dbus/dbus-init.cpp:103: warning: unused variable ‘result’ > extension/dbus/dbus-init.cpp:104: warning: unused variable ‘error’ > CXX extension/dbus/application-interface.o > extension/dbus/application-interface.cpp:40: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:57: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:57: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:63: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:70: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:70: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:78: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:78: warning: unused parameter ‘document_name’ > extension/dbus/application-interface.cpp:78: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:85: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:85: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:91: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:91: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:101: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:101: warning: unused parameter ‘error’ > extension/dbus/application-interface.cpp:107: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:114: warning: unused parameter ‘object’ > extension/dbus/application-interface.cpp:114: warning: unused parameter ‘error’ > CXX extension/dbus/document-interface.o > extension/dbus/document-interface.cpp:205: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:341: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:486: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:521: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:555: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:563: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:573: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:807: warning: unused parameter ‘object’ > extension/dbus/document-interface.cpp:807: warning: unused parameter ‘shape’ > extension/dbus/document-interface.cpp:841: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:853: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:877: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:933: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:944: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:958: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:975: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1019: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1040: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1055: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘object’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘x’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘y’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘x2’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘y2’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘replace’ > extension/dbus/document-interface.cpp:1079: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1141: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1153: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1160: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1277: warning: unused parameter ‘error’ > extension/dbus/document-interface.cpp:1299: warning: unused parameter ‘object’ > CXX extension/implementation/implementation.o > extension/implementation/implementation.cpp:100: warning: unused parameter ‘docCache’ > CXX extension/implementation/script.o > ... > > CXX inkscape-version.o > AR libinkversion.a > CC extension/dbus/wrapper/libinkdbus_la-inkscape-dbus-wrapper.lo > CCLD libinkdbus.la > Undefined symbols: > "_dbus_g_bus_get", referenced from: > _dbus_get_connection in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_desktop_init_dbus in libinkdbus_la-inkscape-dbus-wrapper.o > "_dbus_g_proxy_call", referenced from: > _inkscape_delete_all in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_call_verb in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_rectangle in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_ellipse in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_polygon in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_star in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_spiral in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_line in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_text in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_image in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_node in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_get_width in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_get_height in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_get_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_set_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_merge_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_document_resize_to_fit_selection in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_set_attribute in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_set_int_attribute in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_set_double_attribute in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_get_attribute in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_move in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_move_to in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_object_to_path in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_get_path in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_transform in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_get_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_modify_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_merge_css in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_set_color in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_move_to_layer in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_get_node_coordinates in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_save in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_save_as in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_load in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_mark_as_unmodified in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_close in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_inkscape_exit in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_undo in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_redo in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_pause_updates in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_resume_updates in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_update in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_get in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_add in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_add_list in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_set in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_set_list in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_rotate in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_delete in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_clear in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_select_all in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_select_all_in_all_layers in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_box in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_invert in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_group in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_ungroup in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_cut in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_copy in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_paste in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_scale in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_move in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_move_to in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_move_to_layer in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_get_center in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_to_path in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_combine in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_divide in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_change_level in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_new in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_set in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_get_all in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_change_level in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_next in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_layer_previous in libinkdbus_la-inkscape-dbus-wrapper.o > "_dbus_g_proxy_new_for_name", referenced from: > _dbus_get_proxy in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_desktop_init_dbus in libinkdbus_la-inkscape-dbus-wrapper.o > "_dbus_g_type_get_collection", referenced from: > _inkscape_get_node_coordinates in libinkdbus_la-inkscape-dbus-wrapper.o > _inkscape_selection_get_center in libinkdbus_la-inkscape-dbus-wrapper.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > make[3]: *** [libinkdbus.la] Error 1 > make[2]: *** [all] Error 2 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > LeWitt:mp-x11 suv$ [2] installed (dbus) dependencies (via MacPorts): dbus @1.2.24_0+no_root+no_startupitem dbus-glib @0.86_1 glib2 @2.24.1_0+darwin

11 22