- Inkscape Devel - Inkscape Mailman

LJ Editor's Choice 2005
by unknown＠example.com 02 Jul '05

02 Jul '05

I just flipped to page 82 of the August 2005 issue of Linux Journal. Congratulations to all you devs for the Editor's Choice Award for Graphics Software. Aaron Spike

5 4

object.cpp build failure on Solaris
by Christopher Wiedel 02 Jul '05

02 Jul '05

I've been trying to build Inkscape 0.41 on sparc-sun-solaris2.8, and have run into a bit of a problem. It configures fine, and when I start 'make' it initially goes well, occasionally popping out warnings like: node-context.cpp: In function `void nodepath_event_attr_changed(SPRepr*, const gchar*, const gchar*, const gchar*, bool, void*)': node-context.cpp:313: warning: cast from `GTypeInstance*' to `SPItem*' increases required alignment of target type node-context.cpp:322: warning: cast from `GTypeInstance*' to `SPItem*' increases required alignment of target type However, it blows up when it hits src/object-edit.cpp. Or more accurately, something inside it. It throws out a great many of the same type of warnings as the ones above. This doesn't appear to be the problem, since other files had the same warnings, but were able to compile. It winds up with this: object-edit.cpp: In function `void sp_offset_offset_set(SPItem*, const NR::Point&, const NR::Point&, unsigned int)': object-edit.cpp:897: warning: cast from `GTypeInstance*' to `SPOffset*' increases required alignment of target type object-edit.cpp: In function `NR::Point sp_offset_offset_get(SPItem*)': object-edit.cpp:909: warning: cast from `GTypeInstance*' to `SPOffset*' increases required alignment of target type make[2]: *** [object-edit.o] Error 1 make[2]: Leaving directory `/usr/foo/inkscape/0.41/inkscape-0.41/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/foo/inkscape/0.41/inkscape-0.41' make: *** [all] Error 2 This is using gcc 3.3.2. It doesn't appear to have any actual error message that I can find. I would appreciate any pointers. Thanks. -- Christopher Wiedel

2 1

Fwd: Re: [Inkscape-devel] Inkboard CVS updates
by David Yip 01 Jul '05

01 Jul '05

On Friday 01 July 2005 01:04 pm, mental@...3... wrote: > I suspect the element and its sodipodi:type attribute might be > getting transmitted separately. > > i.e. the remote client ends up getting a bare <svg:path>, and > immediately creates an SPPath object. The sodipodi:type attribute > which would have instructed it to create an SPEllipse or whatever > might not arrive until it's too late. Actually, it seems like that's exactly what's going on, judging from the way Inkboard processes messages: the new object message arrives, so Inkboard creates a new object. However, only _then_ does it actually parse the type attribute and set it. I'm reworking received_new_object_helper to extract and set the type attribute before it creates the new object. Hopefully, this'll fix the problem. -- David

1 0

Inkboard CVS updates
by David Yip 01 Jul '05

01 Jul '05

I have committed a number of fixes to the Inkboard CVS <http://sourceforge.net/projects/inkboard> that address crashes related to buffer overflows. Instructions for building and running Inkboard can be found in my request for Inkboard testers that was posted to this list. Inkboard should now be much more stable than it previously was, sans conditions like invalid Jabber usernames or passwords. (I haven't gotten around to debugging those yet; I've been chasing down another bug, which is described below.) In a session between two peers Alice and Bob, if Alice sends a star, spiral, or ellipse, it will show up correctly on Bob's canvas, and (almost) any manipulations that Alice makes will be correctly replicated on Bob's canvas. However, if Bob manipulates the star, spiral, or ellipse in any way, the changes will not be correctly replicated on Alice's canvas. Additionally, Bob will not see the object as a star, spiral, or ellipse -- he will only see it as a path. I think these two problems are related, and since I'm not sure where to start with addressing the first problem, I've been focusing on the second, in the hope that it will cure the first :) I don't think this is a case of missing information: if Bob saves the document, exits, and then reopens it, any star, spiral, or ellipse will be correctly recognized as such, and not just a path. I think there's just something that Inkboard is just not triggering correctly. If anyone has any ideas on where to look or what to look for, I'd greatly appreciate them. Another, smaller bug: gradient editing is not replicated properly. Pressing "add" will replicate the changes, but the gradient objects themselves fall out of sync. Finally, just some thoughts about the near-future integration with Inkscape: Ideally, I'd like to begin merging Inkscape with Inkboard only when all of the bugs have been ironed out of the Inkboard code. That's rather unrealistic, though, especially since the act of merging may expose new bugs anyway! :) So it may be a good idea to create a new branch in the Inkscape codebase specifically for integration with Inkboard, and then merge branches when an acceptable level of robustness is achieved. -- David

3 3

object-edit.cpp:842: error: `isfinite' undeclared in namespace `std'
by Jeremy C. Reed 01 Jul '05

01 Jul '05

Building inkscape-0.41 on NetBSD 1.6.2_STABLE with GCC 3.3.3. I receive this error: if c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/pkg/include/freetype2 -I/usr/pkg/include -I/usr/pkg/include -I/usr/X11R6/include -I/usr/X11R6/include/freetype2 -DPOTRACE=\"potrace\" -I/usr/pkg/include/gtk-2.0 -I/usr/pkg/lib/gtk-2.0/include -I/usr/pkg/include -I/usr/X11R6/include -I/usr/pkg/include/atk-1.0 -I/usr/pkg/include/pango-1.0 -I/usr/X11R6/include/freetype2 -I/usr/pkg/include/glib/glib-2.0 -I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/include/libxml2 -I/usr/pkg/include/sigc++-2.0 -I/usr/pkg/lib/sigc++-2.0/include -I/usr/pkg/include/gtkmm-2.4 -I/usr/pkg/lib/gtkmm-2.4/include -I/usr/pkg/include/glibmm-2.4 -I/usr/pkg/lib/glibmm-2.4/include -I/usr/pkg/include/gdkmm-2.4 -I/usr/pkg/lib/gdkmm-2.4/include -I/usr/pkg/include/pangomm-1.4 -I/usr/pkg/include/atkmm-1.6 -I/usr/pkg/include/gtkspell-2.0 -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -Wall -W -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -O2 -s -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -MT object-edit.o -MD -MP -MF ".deps/object-edit.Tpo" -c -o object-edit.o object-edit.cpp; \ then mv -f ".deps/object-edit.Tpo" ".deps/object-edit.Po"; else rm -f ".deps/object-edit.Tpo"; exit 1; fi object-edit.cpp: In function `void sp_spiral_outer_set(SPItem*, const NR::Point&, const NR::Point&, unsigned int)': object-edit.cpp:842: error: `isfinite' undeclared in namespace `std' gmake[2]: *** [object-edit.o] Error 1 Any ideas? (Please carbon-copy me on replies.) Jeremy C. Reed BSD News, BSD tutorials, BSD links http://www.bsdnewsletter.com/

3 2

current cvs - problems compiling win32
by Adib Taraben 01 Jul '05

01 Jul '05

Hello, I checked out a fresh copy from the cvs. This does not compile with mingw because a used define is commented out in the makefile. See below. I also compiled a win32 installer for the 0.42pre0. This is 18meg, where should I put this? My webspace on geocities is only 10meg. Ciao, Adib. --- cvs diff -u3 -- Makefile.mingw.common (in directory D:\projekte\inkscape\) Index: Makefile.mingw.common =================================================================== RCS file: /cvsroot/inkscape/inkscape/Makefile.mingw.common,v retrieving revision 1.52 diff -u -3 -r1.52 Makefile.mingw.common --- Makefile.mingw.common 29 Jun 2005 07:07:29 -0000 1.52 +++ Makefile.mingw.common 30 Jun 2005 16:31:54 -0000 @@ -111,7 +111,7 @@ MSGFMT = $(GTKDOS)$(S)bin$(S)msgfmt ####### change me!! -DTG := 20050626 +DTG := 20050630 endif ########################################################################## @@ -120,10 +120,10 @@ ###### VERSION NUMBER -VERSION_NR = 0.41+devel +VERSION_NR = 0.42pre0 # VERSION_NR = 0.42+cvs -# VERSION = \"$(VERSION_NR)-${DTG}\" +VERSION = \"$(VERSION_NR)-${DTG}\" ####### the XP_WIN def is necessary for libjs.a CFLAGS = -O3 -Wall -mms-bitfields -DVERSION=$(VERSION) \ ***** CVS exited normally with code 1 *****

5 7

terminology proposal
by Jakub Steiner 01 Jul '05

01 Jul '05

Hi folks, Until yesterday I haven't had a chance to play with what you call effects. Because I believe this is a misleading terminology I want to propose an alternative: Scripts ------- Scripts are little programs, written in interpreted language, that supply extended Inkscape functionality. They can work on objects, or even drav new objects on the canvas. Both Blender and GIMP projects eventually came to a conclusion that it makes no sense to separate scripts form the core functionality in terms of interface. A script should be free to register anywhere in the menus, based on its functionality. Grouping them, creating yet another menu structure, just because they are written in a particular language is not helpful to the user. Yes, it is pretty much what you call effects now. Filters ------- Filters are operations on selected objects, on their bitmap renderings even. The result of the filter replaces the original object and cannot be easily changed in future. The resulting image is stored in the file upon save. Effects ------- Effects are similar to filters, yet they are "dynamically" applied on a bitmap copy of the object at the target resolution. Only effect settings are stored in the file on save, and the effect needs to be recalculated (possibly some caching/preview voodoo needs to be applied to speed up preview). cheers -- Jakub Steiner <jimmac@...659...> Novell, Inc.

11 17

Re: [Inkscape-user] center alignment about guidelines
by MenTaLguY 01 Jul '05

01 Jul '05

Incidentally, do you know what would be required to increase the default snap distance? It's currently quite small. -mental

3 2

guide lines: desktop vs document coordinate system
by Peter Moulder 30 Jun '05

30 Jun '05

Someone has bug #1222819: “guides have different orgin than objects”: horizontal guideline positions are currently stored as distance up from the bottom of the document (i.e. desktop coordinate system), whereas shape positions’ y coordinates are represented as distance from the top of the document. The result is that if you snap a shape’s position to a horizontal guideline and then resize the document (File>Document preferences, Custom page size, then change the page height), then the shape and the guideline will no longer appear to be at the same position. In my local copy I've mostly fixed this so that the guideline's position from the top of the document is preserved (as for shapes) rather than from the bottom. However, this does raise a user interface issue of how to report to the user what the guide line's position is: /* * For dialog boxes and status bar, should we report positions in the * document coordinate system or in the desktop coordinate system? * * The argument for reporting document coordinate system is that this is * the one that we honour when the document is resized, so in some sense * it is the true (or at least robust) position of the guide. OTOH, * resizing a document is rare. * * The argument for reporting desktop coordinate system is that this is * what's used by the rulers and "current position" indication. This is * the coordinate system that we usually report to users, so is less * confusing to users. * * ... * * (Hopefully, future versions of inkscape will get rid of the separate * desktop coordinate system, to remove this problem.) */ Comments? pjrm. -- bbyak: swatches, rich text, gradient on canvas... JonCruz: The answer to the ultimate question of life, the universe, and everything... JonCruz: Inkscape 0.42!!!!!!!

1 0

Fwd: [cairo] redesigning the arguments for svg2png
by unknown＠example.com 30 Jun '05

30 Jun '05

Just FYI in case you had anything to add.. ----- Forwarded message from Jason Dorje Short <jdorje@...859...> ----- Date: Wed, 29 Jun 2005 21:37:27 -0400 From: Jason Dorje Short <jdorje@...859...> Reply-To: Jason Dorje Short <jdorje@...859...> Subject: [cairo] redesigning the arguments for svg2png To: "Cairo Mail List (E-mail)" <cairo@...278...> Current arguments for svg2png: -w $WIDTH -h $HEIGHT -s $SCALE -x, --flipx -y, --flipy input.svg and output.png are taken directly as parameters This is all explained in `man svg2png`. The problem is it's incomplete. ---------- For instance if you give -w and -h svg2png makes an image with the given $WIDTH and $HEIGHT and puts the SVG file inside it with preserved aspect ratio. Thus there is no distortion and there is padding. One thing I need to do is to change the aspect ratio. I want to give a width and height and have the SVG "stretch" to take up this whole area. Thus the xscale and yscale are different. Thus there is distortion and there's no padding. This is what rsvg, sodipodi, and inkscape command-line renderers do. A third thing one would want to do is preserve the aspect ratio but without any padding. Thus the $WIDTH and $HEIGHT provide the max dimensions, just like svg2png does now, but without any padding. Thus there is no distortion and there is no padding. IIRC this is what the librsvg rsvg_pixbuf_from_file_at_max_size function does (which I've found very useful in the past). Yet another thing you might want to do is specify the xscale and yscale independently. I can't recall ever needing to do this, but rsvg allows it. Finally, one might wish to specify things in DPI. If the SVG image is given in real-world dimensions (e.g., inches) giving a DPI to render at will allow you to make the PNG image show up at the right size when rendered at that DPI (to a monitor or a printer). Aspect ratio is preserved; this is just a (possibly) convenient way of setting the --scale. Inkscape provides a -d $DPI parameter allowing this. Note that this will not work with all SVG files. ---------- Of course svg2png should be able to do all of the above tasks. It would also be nice to keep command-line compatibility with rsvg, inkscape, sodipodi. The trick is to do all this without having confusingly many options or giving unexpected default behavior. Thus I suggest: --width=$WIDTH (-w) --height=$HEIGHT (-h) --xscale=$X_SCALE (-x) --yscale=$Y_SCALE (-y) --flipx (-X maybe?) --flipy (-Y maybe?) --scale=$SCALE (-s) --dpi=$DPI (-d) --pad [1] --stretch You may pad or stretch or neither but not both. The default should be to do neither (same as rsvg, inkscape, and sodipodi), this changes the current behavior which is to pad. (--pad and --stretch were suggested by Carl.) Supporting -d will require new functions to libsvg and libsvg-cairo to set the DPI. -x and -y are changed from flipx and flipy to xscale and yscale. This matches the rsvg args (they call it --x-zoom, --y-zoom). In case of conflicting options (--width and --xscale both given) the one higher up in the list is given priority (this is obviously arbitrary and can be tweaked a bit). Care should be taken to give a sensible output no matter what combination of args are given (rsvg is pretty bad at this). ---------- For full compatibility with inkscape and rsvg it would be necessary to add more "long argument" aliases. This would be convenient but would also add clutter to the interface. Inkscape also has some additional parameters that might be useful, either for new features or compatibility. See -a, -f, -e, -i, -j, -t, -b, -y from `man inkscape`. I don't understand all of these but some of them are probably desirable. In a related note xsvg should probably support a similar set of options. Seems there could be a lot of overlap here. -jason _______________________________________________ cairo mailing list cairo@...278... http://lists.freedesktop.org/mailman/listinfo/cairo ----- End forwarded message -----

3 2