- Inkscape Devel - Inkscape Mailman

Port to SGI IRIX 6.5
by Jeremy Y. Meng 12 Nov '05

12 Nov '05

Dear Inkscape developers, Thank you all for this wonderful program. I love it and have been trying to port it to SGI IRIX 6.5 platform. My workstation is an Octane2 V6 running 6.5.28. My goal is to build Inkscape-20051109-0840 using SGI MIPSpro compiler. I managed to get an executable by patching the source (many many "#ifdef (__sgi) ..."). However it crashed every time shortly after startup, with the following error: > inkscape event_scan: got unknown client message ALERT: Process [inkscape] 775729 generated trap, but has signal 10 held or ignored epc 0xfa46a14 ra 0xfa46244 badvaddr 0xffffffffff396d98 process has been terminated to prevent infinite loop Bus error The interesting part is that I could run inkscape remotely from a windows machine via Cygwin/X server and play with it for a while (until it randomly crashed). Does this have anything to do with the X visuals? The Octane V6 has a highest 30-bit visual. Then I tried again using gcc 3.4. This time I only need to modify a few #define's regarding isFinite() and round(). But the disaster was when making the inkscape binary. There are tons of errors like a few listed below. I don't know too much C++. I am hoping my patch didn't introduce any bugs into Inkscape. Anyone interested please take a look at my patch and maybe give some insights? --- begin pasting error msg --- gmake all-recursive gmake[1]: Entering directory `/usr/people/voidfoo/devel/inkscape/inkscape_gcc/build_gcc' Making all in src gmake[2]: Entering directory `/usr/people/voidfoo/devel/inkscape/inkscape_gcc/build_gcc/src' /bin/sh ../libtool --mode=link g++ -Wall -W -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -g -O2 -Wa,-xgot -L/usr/nekoware/lib -o inkscape --export-dynamic main.o libinkpre.a application/libinkapp.a ui/dialog/libuidialog.a dialogs/libspdialogs.a dom/libdom.a jabber_whiteboard/libjabber_whiteboard.a trace/libtrace.a svg/libspsvg.a widgets/libspwidgets.a display/libspdisplay.a helper/libspchelp.a libcroco/libcroco.a libnrtype/libnrtype.a libnr/libnr.a libavoid/libavoid.a livarot/libvarot.a ui/view/libuiview.a ui/libui.a ui/widget/libuiwidget.a extension/libextension.a extension/implementation/libimplementation.a extension/internal/libinternal.a extension/script/libscript.a xml/libspxml.a util/libinkutil.a io/libio.a inkjar/libinkjar.a libinkpost.a debug/libinkdebug.a -L/usr/nekoware/lib -L/usr/nekoware//lib -lgtkmm-2.4 -lgdkmm-2.4 -latkmm-1.6 -lpangomm-1.4 -lglibmm-2.4 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -lxslt -lxml2 -lz -liconv -lm -lsigc-2.0 -lgthread-2.0 -lpthread -lglib-2.0 -lintl -lpng -lz -lpopt -L/usr/nekoware/lib -lgnomevfs-2 -lbonobo-2 -lgconf-2 -lbonobo-activation -lORBit-2 -lm -lgmodule-2.0 -lgthread-2.0 -lpthread -lglib-2.0 -lintl -rpath /usr/nekoware/lib -L/usr/nekoware/lib -lXft -lfreetype -lz -lXrender -lX11 -lfontconfig -L/usr/nekoware/lib -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl -L/usr/nekoware/lib -rpath /usr/nekoware/lib -lfreetype -lz -lgc g++ -Wall -W -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -g -O2 -Wa,-xgot -o inkscape --export-dynamic main.o -L/usr/nekoware/lib libinkpre.a application/libinkapp.a ui/dialog/libuidialog.a dialogs/libspdialogs.a dom/libdom.a jabber_whiteboard/libjabber_whiteboard.a trace/libtrace.a svg/libspsvg.a widgets/libspwidgets.a display/libspdisplay.a helper/libspchelp.a libcroco/libcroco.a libnrtype/libnrtype.a libnr/libnr.a libavoid/libavoid.a livarot/libvarot.a ui/view/libuiview.a ui/libui.a ui/widget/libuiwidget.a extension/libextension.a extension/implementation/libimplementation.a extension/internal/libinternal.a extension/script/libscript.a xml/libspxml.a util/libinkutil.a io/libio.a inkjar/libinkjar.a libinkpost.a debug/libinkdebug.a -L/usr/nekoware//lib /usr/nekoware/lib/libgtkmm-2.4.so -L/usr/lib32 /usr/nekoware/lib/libgdkmm-2.4.so /usr/nekoware/lib/libatkmm-1.6.so /usr/nekoware/lib/libpangomm-1.4.so /usr/nekoware/lib/libglibmm-2.4.so /usr/nekoware/lib/libgtk-x11-2.0.so /usr/nekoware/lib/libgdk-x11-2.0.so /usr/nekoware//lib/libatk-1.0.so /usr/nekoware/lib/libgdk_pixbuf-2.0.so /usr/nekoware/lib/libpangocairo-1.0.so /usr/nekoware/lib/libcairo.so -lpng12 /usr/nekoware/lib/libglitz.so /usr/nekoware/lib/libxslt.so /usr/nekoware/lib/libsigc-2.0.so -lpng /usr/nekoware/lib/libgnomevfs-2.so -L/usr/local/lib -L/usr/local2/lib /usr/nekoware/lib/libxml2.so -lssl -lcrypto -lgen /usr/nekoware/lib/libbonobo-2.so /usr/nekoware/lib/libgconf-2.so /usr/nekoware/lib/libbonobo-activation.so /usr/nekoware/lib/libORBitCosNaming-2.so -lfastm /usr/nekoware/lib/libORBit-2.so /usr/nekoware/lib/libpopt.so /usr/nekoware/lib/libgthread-2.0.so -lpthread /usr/nekoware/lib/libXft.so /usr/nekoware/lib/libXrender.so -lX11 /usr/nekoware/lib/libfontconfig.so /usr/nekoware/lib/libexpat.so /usr/nekoware/lib/libpangoft2-1.0.so /usr/nekoware/lib/libpango-1.0.so -lm /usr/nekoware/lib/libgobject-2.0.so /usr/nekoware/lib/libgmodule-2.0.so /usr/nekoware/lib/libglib-2.0.so /usr/nekoware/lib/libintl.so /usr/nekoware/lib/libiconv.so -lc /usr/nekoware/lib/libfreetype.so -lz /usr/nekoware/lib/libgc.so -ldl -Wl,-rpath -Wl,/usr/nekoware/lib:/usr/nekoware//lib ld32: WARNING 84 : dom/libdom.a is not used for resolving any symbol. ld32: WARNING 84 : jabber_whiteboard/libjabber_whiteboard.a is not used for resolving any symbol. ld32: WARNING 84 : inkjar/libinkjar.a is not used for resolving any symbol. ld32: WARNING 84 : /usr/nekoware/lib/libgtkmm-2.4.so is not used for resolving any symbol. ld32: WARNING 84 : /usr/nekoware/lib/libxslt.so is not used for resolving any symbol. ld32: WARNING 84 : /usr/lib32/libgen.so is not used for resolving any symbol. ld32: WARNING 84 : /usr/nekoware/lib/libXft.so is not used for resolving any symbol. ld32: WARNING 84 : /usr/lib32/libdl.so is not used for resolving any symbol. ld32: ERROR 33 : Unresolved text symbol "Gtk::Main::Main(int*, char***, bool)" -- 1st referenced by main.o. Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved text symbol "Gtk::Main::run()" -- 1st referenced by main.o. Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved text symbol "Gtk::Main::~Main()" -- 1st referenced by main.o. Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved text symbol "Glib::ustring::ustring()" -- 1st referenced by libinkpre.a(file.o). Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved text symbol "Glib::ustring::operator=(char const*)" -- 1st referenced by libinkpre.a(file.o). Use linker option -v to see when and which objects, archives and dsos are loaded. [many many lines skipped] ld32: ERROR 33 : Unresolved text symbol "virtual thunk to Gtk::Adjustment::~Adjustment()" -- 1st referenced by extension/libextension.a(parameter.o). Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: INFO 152: Output file removed because of error. collect2: ld returned 2 exit status gmake[2]: *** [inkscape] Error 1 gmake[2]: Leaving directory `/usr/people/voidfoo/devel/inkscape/inkscape_gcc/build_gcc/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/people/voidfoo/devel/inkscape/inkscape_gcc/build_gcc' gmake: *** [all] Error 2 --- end pasting error msg --- Thank you very much! -- Jeremy Meng ---------------------------------------------------------------------------

4 5

NEW: Selected style indicator, statusbar redesign
by bulia byak 12 Nov '05

12 Nov '05

A new control in the left end of the statusbar lets you quickly view and change the fill and stroke of the selected object(s). * The two indicators, labelled "F:" (top) and "S:" (bottom), display fill and stroke of the selected object(s) correspondingly. * Each indicator can display either a color/opacity swatch (the opacity shown here is the fill opacity or stroke opacity, not the master opacity) or a label specifying "N/A" (nothing selected), "None" (no fill/stroke), "Unset" (unset fill/stroke), "L Gradient", "R Gradient", "Pattern" (corresponding fill/stroke types), or "Different" (selected objects have different stroke types). * Additionally, each indicator may be accompanied by one of two flags, "M" ("multiple", meaning there are two or more objects all with the _same_ fill/stroke) or "A" ("averaged", meaning there are two or more objects with flat color fill/stroke whose colors are averaged). * Just as the Fill&Stroke dialog, the new control correctly displays the fill/stroke of the selected gradient handle or selected text fragment in the corresponding tools. * Left-click on an indicator opens or activates the Fill&Stroke dialog with the corresponding tab selected. * Right-click on an indicator opens a popup menu with the following commands: ** "Remove fill/stroke": Removes fill or stroke from the selected objects. ** "Last set color": Applies to the selected objects the fill/stroke color that was last applied to anything. ** "Last selected color": Applies to the selected objects the fill/stroke color that was last displayed in this indicator. (To easily copy fill/stroke color between objects: select source, select destination, apply "last selected color".) ** "Unset fill/stroke": Unsets fill or stroke from selected objects (useful for clone originals). ** "Edit fill/stroke...": Opens or activates the Fill&Stroke dialog with the corresponding tab selected. * Middle-click on an indicator removes fill/stroke from selected objects; if it is already removed (i.e. if the indicator displays "None"), it does the same as the "Last set color" command from the popup menu. (In other words, it toggles between "None" and the last set color.) The zoom field and the cursor coordinates indicator have been rearranged for compactness and moved to the right end of the statusbar. == Implementation notes: == * There's no fixed pixel sizes for fonts used anywhere. Instead, the control uses a font size 70% of the current gtk default. I hope this works for most people, but I know there will be those who will find this font size too small, and others for whom it will be too large and pushing the vertical size of the statusbar. I want to hear your feedback on this. * The new control is itself done in gtkmm, yet it uses an old GTK color preview widget, and fits nicely into the old GTK desktop widget. The Glibmm::wrap() and gobj() are all you need to combine GTK and gtkmm stuff freely. So, I may be missing something, but I really don't understand why you gtkmm guys do this --new-gui thing instead of just converting the existing desktop widget-by-widget. * Despite lots of functionality, the new control is quite small in the code. That's because it reuses all the architectural concepts I've been slowly pushing in the last two years: desktop's current color, set and query style signals. With that in place, coding this entire control took just a couple days. It should also be easy to change or extend it. * TODO: I also plan to add a master opacity spinbutton to this control. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

6 14

Re: [Inkscape-devel] Port to SGI IRIX 6.5
by Jeremy Y. Meng 11 Nov '05

11 Nov '05

On Sat, Nov 12, 2005 at 04:19:24AM +1100, Peter Moulder wrote: > >> >> +++ inkscape_irix/src/libavoid/makepath.cpp 2005-11-09 14:19:52.346046320 -0800 > >I'll add #include <algorithm> and `using' statements for make_heap, >push_heap, pop_heap. > No, please do not #include <algorithm>. It was my mistake to introduce it. std::-prefixing *_heap() would be enough. -- Jeremy Meng ---------------------------------------------------------------------------

2 2

0.43pre3: Everything is perfect
by Ted Gould 11 Nov '05

11 Nov '05

And, if it's not, now is a good time to mention it. http://sourceforge.net/project/showfiles.php?group_id=93438&package_id=9911… MD5 Sums: 3514904d0044f3670c5977d232f5ab87 inkscape-0.42+0.43pre3.tar.bz2 72fb0075f2465f990d36c08ee9fd29ad inkscape-0.42+0.43pre3.tar.bz2.sig d6140b948cc918773a4b414bdbdaf041 inkscape-0.42+0.43pre3.tar.gz 0d0d75c4f02eb01e71645c0f20f3ba03 inkscape-0.42+0.43pre3.tar.gz.sig --Ted

6 7

CVS
by Joshua A. Andler 11 Nov '05

11 Nov '05

Uhm... at least three hours now SF devel CVS has been borked. This is one of the longest outages I've seen and was wondering if we should file a trouble ticked with SF or what. -Josh

2 1

Re: Have you ever thought about security issues?
by unknown＠example.com 11 Nov '05

11 Nov '05

Quoting Maxim Shemanarev <mcseem@...1076...>: > > Well, at least the version I have (v4.1) just gets into an > > infinite loop anddoesn't respond. I don't think it's correct. (assuming you mean 0.41) Hmm, you're right. It catches trivial circular references (e.g. to self or ancestor), but not more complex ones. > Anyway, there's a choice if you control the level of recursion > (and it's a must IMO). You can report an error and stop, or you > can keep rendering until some level of recursion is exceeded. For a circular reference, the standard requires that you do not render the erroneous element or any following elements at all (a naive implementation might have to throw out some intermediate rendering product to do this). I do not believe the standard requires any particular action for references that are deep but not recursive, but stopping rendering at some point is sensible even if not strictly conforming. > I don't see any other elegant way of detecting the loops, because > they can have any level of indirection (a pattern refers to > another pattern that refers to another pattern, etc... and > the first pattern refers to the first one). It's also worth noting that the circularity can happen along several "axes"; for example: ... <style type="text/css">.foo { fill: url(#blah); }</style> ... <pattern id="blah" ...> <rect class="foo" ... /> </pattern> ... > BTW, is that legal to have *nested* patterns/markers at all in > SVG? Yes. See sections 13.3 and 11.6.2 of SVG 1.1: <!ENTITY % SVG.marker.content "( %SVG.Description.class; | %SVG.Animation.class; %SVG.Structure.class; %SVG.Conditional.class; %SVG.Image.class; %SVG.Style.class; %SVG.Shape.class; %SVG.Text.class; %SVG.Marker.class; <== %SVG.ColorProfile.class; %SVG.Gradient.class; %SVG.Pattern.class; %SVG.Clip.class; %SVG.Mask.class; %SVG.Filter.class; %SVG.Cursor.class; %SVG.Hyperlink.class; %SVG.View.class; %SVG.Script.class; %SVG.Font.class; %SVG.marker.extra.content; )*" > <!ENTITY % SVG.pattern.content "( %SVG.Description.class; | %SVG.Animation.class; %SVG.Structure.class; %SVG.Conditional.class; %SVG.Image.class; %SVG.Style.class; %SVG.Shape.class; %SVG.Text.class; %SVG.Marker.class; %SVG.ColorProfile.class; %SVG.Gradient.class; %SVG.Pattern.class; <== %SVG.Clip.class; %SVG.Mask.class; %SVG.Filter.class; %SVG.Cursor.class; %SVG.Hyperlink.class; %SVG.View.class; %SVG.Script.class; %SVG.Font.class; %SVG.pattern.extra.content; )*" > -mental

2 1

Re: Have you ever thought about security issues?
by unknown＠example.com 11 Nov '05

11 Nov '05

Quoting Maxim Shemanarev <mcseem@...1076...>: > I'm afraid nobody has ever thought of it. Are there any > recommendations from W3C? According to SVG 1.1, circular references are an error and should be treated as such -- see the appendix on implementation requirements (F.2 Error processing). It's also referenced in the sections on <use> (5.6, just after the examples) and in the overview section of "References and the 'defs' element" (5.3.1). Any problems with SVG implementations due to circular references is an issue of non-conformance to that normative appendix. Inkscape gets that part of the standard partly right: it at least refuses to render circular references; in general they do not cause harm (if you can find some cases where it does, please let us know). -mental

1 0

WEBFORM inkscape on pocket pc
by Miguel Ozonas 11 Nov '05

11 Nov '05

Message from Inkscape submission form Please note, that the submitter may not read this list. CC your answer to the submitter name: Miguel Ozonas email: miguelozonas@...1075... submitted the following: Enter your message or news here. Hi, i just have downloaded your software and play it, and i have a question. Are you thinking to convert te software for pocket pc?

1 0

inkscape windows icon refab
by Bob Jamison 11 Nov '05

11 Nov '05

Hi, all... Hey, we talked about this a year ago, but nothing happened. The inkscapexxxx.ico file that we use for the Inkscape "Application" icon (resource #300), is a fix of the crappy old .ico that I made myself when we first started working on a 'standard' Windows build. I am in no way an artist, and the thing looks utilitarian and boring. So I ask the question again: is there some guy who can make a new icon which is DIB-like (various sizes) and yet pretty at the same time? Of course there are lots of people who can make nice 48x48 or 32x32 images, but we need a Windows guy who knows and can cope with the constraints of a .ico (limited colors, etc) bob

6 6

NEW: shortcuts, misc
by bulia byak 11 Nov '05

11 Nov '05

- Now you can use Shift+middle button drag in any tool to zoom into an area. This works the same as simple drag in Zoom tool, but is faster because it does not require switching away from your current tool. Together with middle button drag (panning), middle button click (zoom in) and Shift+middle button click (zoom out), this completes the set of canvas navigation shortcuts available in any tool. - In Gradient tool, Shift+R reverses the gradient definition (i.e. mirrors the stop positions) without moving the gradient handles. For example, an elliptic gradient with blue center and red periphery becomes red in the center and blue in the periphery. This works on the gradient(s) of the currently selected gradient handle or, if no handle is selected, on all selected objects' gradients. (Compare with the Node tool where Shift+R reverses the direction of the selected path.) This is especially convenient for radial gradients which, unlike linear, you cannot simply rotate by 180 degrees for the same result. - When toggling one of the "transform with object" buttons (for stroke width, rounded rectangle corners, gradients, or patterns), a message is displayed in the statusbar explaining what has changed in the program's behavior. - Zoom commands in the View menu are moved to a submenu; the Zoom In and Zoom Out commands are added to that submenu. - The contents of the statusbar message are now duplicated as a tooltip that is shown when you hover the mouse over the statusbar. [TODO: need to strip <b></b> from the tooltips.] - Whole thousands above 2000 in the rulers are now displayed as 2k, 3k, 4k etc. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

NEW: Transform dialog redesign
by bulia byak 11 Nov '05

11 Nov '05

Fixes and improvements in the Transform dialog (Ctrl+Shift+M): - The "Apply to each object separately" checkbox is added, allowing you to scale/rotate/skew each selected object by the same amount, around that object's center. When off (by default), the selection is transformed as a whole. The status of this checkbox is remembered across sessions. (It has no effect on Move and Matrix tabs). - The new Clear button resets the values on the current tab to defaults. - The Scale tab now allows you to specify horizontal or vertical size increments in percentage or absolute units. Also there's a "Scale proportionally" checkbox which ensures that scaling preserves the width/height ratio. (If you are scaling several objects proportionally with "Apply to each object separately", you can only use the % unit to specify the scaling; otherwise each object's scale increments will have the width/height ratio of the entire selection, not of that specific object.) - The Skew tab can now specify the skew as an absolute displacement (e.g. for horizontal skewing of a rectangle, that means the shift of the top rectangle side relative to the bottom), as percentage displacement (e.g. a 1% horizontal skew of a rectangle means shifting the top side by 1% of the rectangle height), or as an angle (e.g. horizontal skew by 15 degrees results in the sides of a rectangle being rotated to that angle, while the top and bottom remain horizontal). - The Matrix tab (previously called "Transform") can either edit the current transform= matrix of an object, or post-multiply the transform= with the matrix you specify, depending on the "Edit current matrix" checkbox. As it is now redundant, the matrix in the Object Properties dialog is removed. - The dialog now correctly watches selection changes in the active document window and updates its values accordingly. - The layout of the dialog is simplified, tooltips and mnemonics added for better usability. - Many bugs are fixed, especially in value conversions between units. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

[root@...1070...: [Inkscape-tester] inkscape build report]
by Bryce Harrington 11 Nov '05

11 Nov '05

Some different build warnings than normal... ----- Forwarded message from root <root@...1070...> ----- Date: Thu, 10 Nov 2005 22:50:40 -0800 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Thu Nov 10 17:37:54 2005 (Run 734) Snapshot: inkscape-20051110-0700.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 6 0 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == none == Warnings == style.cpp:1254: warning: enumeral and non-enumeral type in conditional expression style.cpp:1261: warning: enumeral and non-enumeral type in conditional expression display/canvas-arena.cpp:87: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:87: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:133: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:133: warning: (perhaps the `offsetof' macro was used incorrectly) == Environment Summary == ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

[cworth@...573...: [cairo] Slipping 1.2.0 out to 2005-12-15, and help needed]
by Bryce Harrington 11 Nov '05

11 Nov '05

----- Forwarded message from Carl Worth <cworth@...573...> ----- Date: Thu, 10 Nov 2005 16:47:09 -0800 From: Carl Worth <cworth@...573...> To: cairo@...278... Subject: [cairo] Slipping 1.2.0 out to 2005-12-15, and help needed Shortly after cairo 1.0.0 was released, I picked an out-of-the-hat date of 2005-11-01 for cairo 1.2.0. That date has now come and gone, so so much for my powers of prognostication. I recently looked over the 1.2.0 roadmap [*] and saw that there's quite a bit still left to do. Personally, I've been focusing on the PS and PDF output quality issues. The hard parts of that are done now, but there's probably at least a week or two of work still to be done there. I had considered finishing those things up to get a 1.2.0 release out as soon as possible (in the next week or two) and letting everything else on the roadmap slip. But it looks like that's not going to be possible. I probably won't have much time to dedicate to this work until the beginning of December. So 1.2.0 won't be happening before 2005-12-15. This does provide more time for other interested people to jump in and fill the gaps for the remaining pieces of 1.2.0. If any of the following sound important to you, please consider getting involved: * win32 backend We basically just need to get it plugged into the test suite. For a long time, the issue here was missing support in the test suite for RGB24 output and for backend-specific reference images. But thanks to Keith's efforts with getting the PS backend into the test suite these two problems are fixed. So, is there a cairo-win32 developer that could fill in the two stubs in cairo/test/cairo-test.c: cairo_surface_t * create_win32_surface (int width, int height, void **closure); static void cleanup_win32 (void *closure); If so, that would be a great help and would definitely contribute a lot toward making sure that cairo-win32 remains stable in the future. * cairo_begin_group/cairo_end_group I sent a half-started patch for this to the list sometime ago. I feel good about the API, (though maybe the patch was before the addition of the current CONTENT support, and if so it should be updated to that). But the real work here is to make the intermediate surface auto-growable, which might require a tweak in the pattern code to get the offset right when the intermediate surface is finally painted. I really like this API, and I'm looking forward to having it available. I'd be glad to help anyone interested in working on this piece. * Performance fixes There's always more to be done here. I'm going to make that a big focus of my efforts post-1.2.0 by working on a performance regression suite and tackling some long-standing issues. We probably don't need much here before 1.2.0 since people are claiming that cairo 1.1.1 is already performing much better than 1.0.2. (Of course, there's still a lot of room for improvement, but this isn't something that should slow down 1.2.0 I think). * SVG backend The roadmap has this as experimental, so I think it can be thrown in at pretty much any point. It just needs someone to look at it first. I will do this after the PS and PDF stuff is done if nobody else has by then. * Bug fixes There are a couple of fairly serious bugs listed in ROADMAP already that I think really need to be fixed. A couple of the XFAILs obviously need to be fixed as well, (such as the *ahem* segfault from extend-reflect). Meanwhile, there have been a bunch of little bug reports, (slight build problems on various platforms for example), that should be pretty easy picking for almost any willing volunteer. As usual, there's almost no end of fun work to be done. I appreciate everything that so many of you are already doing. And this is also a great chance for some new faces to jump in and make some contribution. I'm glad to provide more details and guidance on any of the above as needed. -Carl [*] http://cairographics.org/ROADMAP _______________________________________________ cairo mailing list cairo@...278... http://cairographics.org/cgi-bin/mailman/listinfo/cairo ----- End forwarded message -----

1 0

newest gtkmm-dev necessary to compile HEAD
by Ralf Stephan 11 Nov '05

11 Nov '05

Hello, So it appears one needs the newest gtkmm libs to compile HEAD. I did not foresee this when using some features of the library, and, now that people have upgraded, it's nonsense to revert ;) What's unclear to me is which version is fine, here it is libgtkmm-2.4-dev 2.8.0-0ubuntu1, can others add info? thanks for your patience, ralf

9 15

Plugins translation
by Cédric GEMY 10 Nov '05

10 Nov '05

I would like to know how to translate plugins Dialog options ? it appears to me that they are not inside de *.po files. Should we have a look at *.inx or *.py files ? Cedric

4 3

Inkscape 0.43pre2
by Ted Gould 10 Nov '05

10 Nov '05

https://sourceforge.net/project/showfiles.php?group_id=93438&package_id=991… It is likely that this will be the last prerelease for Inkscape 0.43. If packagers can make packages to ensure the completeness of the package, and if users could make sure it is stable, we'll hopefully be ready to release 0.43! Please submit comments quickly, this prerelease will be a short lived one. MD5 Sums: daa81da8ca152d809aa39ee2c9cd5d04 inkscape-0.42+0.43pre2.tar.bz2 af42797a6b9d3e4d443b3f33717394ba inkscape-0.42+0.43pre2.tar.bz2.sig e46a04eb78ea53876f1fd77c34e5d7d6 inkscape-0.42+0.43pre2.tar.gz 82038ffc49dfb8ba7c9a309cf54046f1 inkscape-0.42+0.43pre2.tar.gz.sig --Ted

5 16

How do we deal with unnamed root layers?
by Wolfram Quester 10 Nov '05

10 Nov '05

Hi alltogether, some time ago I got a bugreport[1] against the debian package of inkscape 0.42.2. The user has problems with editing old drawings containing a "root" layer in the new inkscape version, where the layer is called "Layer 1". Don't we have a compatibility option somewhere? I quote two of his mails further down for details. With best wishes, Wolfi [1] 333779@...499... Ambrose Li wrote: If I edit a drawing with several layers and the root layer contains artwork: After selecting a non-root layer, the "(root)" in the layer selection menu (the one along the bottom edge of the window) disappears. For example, if the drawing has three layers: root, "layer 1" and "layer 2", after selecting "layer 1", only "layer 1" and "layer 2" will remain in the layer selection menu. (If I now click an object that is on the root layer, the "(root)" reappears in the layer selection menu. So the bug is not exactly serious, provided that I can select some object that is in the root layer.) ... I found that new drawings do not have a root layer, but a "Layer 1". So, I cannot reproduce the bug with new drawings, only old drawings with root layers. Perhaps the bug is caused by lack of backward compatibility. (I.e., the developers might have changed the default layer name, and then forgot that old drawings have an unnamed root layer.)

3 5

Printing in A5 Size
by herve couvelard 10 Nov '05

10 Nov '05

Hello : Just one question, where can i look to resolve that prob. : When we choose size document 15x21 when we choose printer size paper A5 On debian sarge, printer epson the result is a croped A5 of a A4 printed. That is to say the all document is not completely printed but 'scaled up' to an A4 and the printed part is on the A5 part of that page. where can we 'go ans see' ? Hervé

1 0

Updated fr.po
by Gazal, Geraud (GE Healthcare) 10 Nov '05

10 Nov '05

Hi all, After correction of some strings in the code (blah(s) replaced by blahs) I've updated fr.po and attached it in the patch tracker (for 0.43?) Regards, matiphas

1 0

[CharlesM@...1042...: [XaraXtreme-dev] Xara LX status]
by Bryce Harrington 10 Nov '05

10 Nov '05

----- Forwarded message from Charles Moir <CharlesM@...1042...> ----- Date: Thu, 10 Nov 2005 10:24:22 -0000 From: Charles Moir <CharlesM@...1042...> To: xara-dev <dev@...1048...> Subject: [XaraXtreme-dev] Xara LX status I know some people are frustrated that not a lot appears to be happening on the Xara open-source release, so this is just an update so you know what's going on. The Xara LX download has been updated again to 0.1c. This has the following changes - Soft Shadows now render (mostly) - Plasma fractal fill types now complete. All Xara fill types now supported. An included example document FillTypes.xar shows all fill types working. - Background rendering - Caching sub-system (switched off by default as it's not very stable yet) This build does have a few known problems, such as the key short cuts appear to have stopped working. But these minor issues are unlikely to get fixed before we start releasing the source code. Most effort is going into preparing the source code and documentation in readiness for the open-source release. We're hoping (but can't be sure) that this is the last update of the viewer before we start releasing source code. There are a few places where we've got third party licensed code, for example some MFC code, and we also use a Snowbound image library for bitmap import / export support. None of these are important aspects of the product and should be easily replaceable with open-source equivalents, but of course we have to be sure any and all such code is removed before we can release anything. Some of the other areas we've been working on: - Eliminated all GCC compiler warnings - We now use AutoConf build system to streamline builds on Linux - 64-bit support. We're also working on some type changes so we can compile it on 64-bit systems. This will be a lot easier for us to do before we release, than after. Finally we're also working on preparing things like a public bugzilla, and various website and documentation updates to provide as much information as we can. Finally, and I'm not sure whether this is a good thing or not, it looks like the first code release will be more than a million lines. That's a substantial part of Camelot codebase (oh and you'll start seeing that name being used - it's the internal codename we've used for this project from the beginning 12 years ago or more). That will give everyone something to get their teeth into, but we hope not too intimidating (and you can see why it's taking us a long time to make sure it's all reasonably clean). Charles ----- End forwarded message -----

1 0

OS X's X11
by Jon A. Cruz 10 Nov '05

10 Nov '05

It appears that Apple fixed the "need to click twice to bring things forward" problem in the latest OS X update. 10.4.3 seems to be happy-happy now. (My X11 is showing "X11 1.1 - XFree86 4.4.0 if anyone cares)

1 0

[root@...1070...: [Inkscape-tester] inkscape build report]
by Bryce Harrington 10 Nov '05

10 Nov '05

Build issues have resolved. :-) Bryce ----- Forwarded message from root <root@...1070...> ----- Date: Wed, 09 Nov 2005 17:21:18 -0800 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report pkgpath=/testing/packages/inkscape/inkscape-20051109-1120.tar.bz2 = Analysis Report for inkscape = Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 5 0 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == none == Warnings == display/canvas-arena.cpp:87: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:87: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:133: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:133: warning: (perhaps the `offsetof' macro was used incorrectly) libnrtype/Layout-TNG-Output.cpp:226: warning: enumeration value `PANGO_WEIGHT_SEMIBOLD' not handled in switch == Environment Summary == ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

release status: pre3 or 0.43 ?
by Peter Moulder 10 Nov '05

10 Nov '05

On Wed, Nov 09, 2005 at 08:36:13PM -0400, bulia byak wrote: > BTW what are the plans for the release? Ted & I were just discussing whether to have a pre3 or 0.43. One issue with pre2 was that it was impossible to build inkboard from source from the tarball. There have also been some packaging changes (and the Effects menu should now be disabled). I suggested that whatever version number we use (pre3 or 0.43), we should announce it on inkscape.org front page and not elsewhere. Comments? pjrm.

2 1

merged CXXIFICATION_VIEW_AND_WIDGET
by Ralf Stephan 09 Nov '05

09 Nov '05

Hello, as Peter has now branched 0.43, I have merged HEAD with my branch, so please expect some recompilation. The Changelog: merged with branch CXXIFICATION_VIEW_AND_WIDGET * src/arc-context.cpp, src/dyna-draw-context.cpp, src/event-context.cpp, src/file.cpp, gradient-context.cpp, src/inkscape.cpp, src/interface.cpp, src/rect-context.cpp, src/select-context.cpp, src/seltrans.cpp, src/sp-namedview.cpp, src/spiral-context.cpp, src/star-context.cpp, src/verbs.cpp, dialogs/dialog-events.cpp, src/dialogs/layer-properties.cpp, src/ui/dialog/dialog.cpp, src/widgets/desktop-widget.cpp, src/widgets/desktop-widget.h: move gtk code into desktop-widget.cpp, called via desktop * src/ui/view/Makefile_insert: added files edit-widget-interface.h, edit-widget.cpp, edit-widget.h the EditWidget is the Gtkmm version of the SPDesktopWidget * src/ui/widget/Makefile_insert: added files ruler.cpp, ruler.h, svg-canvas.cpp, svg-canvas.h, zoom-status.cpp, zoom-status.h these are widgets part of the EditWidget * src/file.cpp, src/inkscape.cpp, src/ui/dialog/dialog.cpp, src/ui/dialog/dialog.h, src/application/application.h, src/application/application.cpp: divide code /wrt Application::getNewGui(): if true, it's called by the Gtkmm application and the inkscape object is meaningless * src/application/app-prototype.h: replace UI specific return value of getWindow() with void* * src/application/editor.cpp, src/application/editor.h: made Editor a singleton, collect global UI code here that (for Gtk+) lives in inkscape.cpp and elsewhere * src/desktop-events.cpp, src/desktop.cpp, src/event-context.cpp, src/nodepath.cpp, src/seltrans.cpp: simplify calls to desktop->set_coordinate_status * src/desktop-handles.cpp, src/desktop-handles.h, src/extension/internal/ps.cpp, src/widgets/gradient-toolbar.cpp, src/widgets/toolbox.cpp: widget is no longer available through desktop * src/Makefile_insert: added files preferences.h preferences.cpp src/inkscape.h, src/inkscape.cpp, src/application/editor.cpp: move preferences handling into preferences.cpp/h * src/desktop.cpp, src/desktop.h: use EditWidgetInterface, more cosmetics * src/desktop.cpp, src/inkview.cpp, src/slideshow.cpp, src/svg-view-widget.cpp, src/svg-view.cpp, src/svg-view.h, src/ui/view/view.cpp, src/ui/view/view.h: streamline setDoc()/setDocument() logic * src/inkview.cpp: include empty func bodies to make linker happy BTW, I get bad markup with cvs in nl.po. Regards, ralf

5 22

train wreck...
by bulia byak 09 Nov '05

09 Nov '05

...predicted by Mental seems to have happened: ui/view/edit-widget.cpp: In member function `void Inkscape::UI::View::EditWidget::initStatusbar()': ui/view/edit-widget.cpp:1153: error: 'class Gtk::Label' has no member named 'property_ellipsize' ui/view/edit-widget.cpp:1153: error: `ELLIPSIZE_END' is not a member of `Pango' with latest HEAD. I haven't yet committed any of my stuff, as I can't compile. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

5 7