May 2006 - Inkscape Devel - Inkscape Mailman

Testing the effects, and a crash report
by Khiraly 20 May '06

20 May '06

Hi! I think it would be a great idea, to have in the Effects menu a testing effects option. If someone click on this menuitem it will execute a simple python AND perl script, which test all the dependencies required for launching the effects, and it report OK/problem form. SO it would be easy for the users, if the effects is right installed or not. Im writing this idea, because there are many effects which require an external file, or an object to work on, or simply it does not seems to make anything (function plotter). So it would be nice to test, if the system right installed or not. There is a crash related to this issue. There is a View->Scripts menuitem, what launched thereis a simple python script, what can be executed. If I launch it, inkscape crash immediatly. Here is the gdb output: View->Scripts, File->launch python program gdb: (gdb) run Starting program: /usr/bin/inkscape [Thread debugging using libthread_db enabled] [New Thread -1228080768 (LWP 12929)] (inkscape:12929): Pango-WARNING **: Error loading GPOS table 4097 ** ERROR **: interpretScript: error starting Language '(null)' aborting... Program received signal SIGABRT, Aborted. [Switching to Thread -1228080768 (LWP 12929)] 0xb6e707c7 in raise () from /lib/tls/libc.so.6 (gdb) bt #0 0xb6e707c7 in raise () from /lib/tls/libc.so.6 #1 0xb6e7206b in abort () from /lib/tls/libc.so.6 #2 0xb7182240 in g_logv () from /usr/lib/libglib-2.0.so.0 #3 0xb7182279 in g_log () from /usr/lib/libglib-2.0.so.0 #4 0x084be1dc in Inkscape::Extension::Script::InkscapeScript::interpretScript ( this=0xbff0609b, script=@0xbff060a4, output=@0xbff060a0, error=@0xbff0609c, language=Inkscape::Extension::Script::InkscapeScript::PYTHON) at ../../src/extension/script/InkscapeScript.cpp:87 #5 0x081e7444 in Inkscape::UI::Dialog::ScriptDialogImpl::execute ( this=0xa6f6000, lang=Inkscape::Extension::Script::InkscapeScript::PYTHON) at ../../src/ui/dialog/scriptdialog.cpp:149 #6 0x081e75a9 in Inkscape::UI::Dialog::ScriptDialogImpl::executePython ( this=0xa6f6000) at ../../src/ui/dialog/scriptdialog.cpp:159 #7 0x081ea221 in sigc::bound_mem_functor0<void, Inkscape::UI::Dialog::ScriptDialogImpl>::operator() (this=0x980deec) at mem_fun.h:1787 #8 0x081ea238 in sigc::adaptor_functor<sigc::bound_mem_functor0<void, Inkscape::UI::Dialog::ScriptDialogImpl> >::operator() (this=0x980dee8) at adaptor_trait.h:251 #9 0x081ea254 in sigc::internal::slot_call0<sigc::bound_mem_functor0<void, Inkscape::UI::Dialog::ScriptDialogImpl>, void>::call_it (rep=0x980ded0) at slot.h:103 #10 0xb7b7db5a in Glib::SignalProxyNormal::slot0_void_callback () from /usr/lib/libglibmm-2.4.so.1 #11 0xb71fba2b in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #12 0xb71eecb9 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #13 0xb71ff134 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #14 0xb7200490 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #15 0xb72007f9 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #16 0xb78671c2 in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0 #17 0xb7785a1b in gtk_menu_shell_activate_item () from /usr/lib/libgtk-x11-2.0.so.0 #18 0xb7785d38 in gtk_menu_shell_activate_item () from /usr/lib/libgtk-x11-2.0.so.0 #19 0xb777b99f in gtk_menu_reorder_child () from /usr/lib/libgtk-x11-2.0.so.0 #20 0xb7e237ce in Gtk::Widget_Class::button_release_event_callback () from /usr/lib/libgtkmm-2.4.so.1 #21 0xb7775900 in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0 #22 0xb71ee5f9 in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #23 0xb71eecb9 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #24 0xb71ff315 in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #25 0xb72001fe in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #26 0xb72007f9 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #27 0xb78673e4 in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0 #28 0xb7773d2d in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 #29 0xb77741a3 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #30 0xb7607bfa in _gdk_events_queue () from /usr/lib/libgdk-x11-2.0.so.0 #31 0xb71791ac in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #32 0xb717c63b in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #33 0xb717c997 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #34 0xb7773341 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #35 0xb7dc1377 in Gtk::Main::run_impl () from /usr/lib/libgtkmm-2.4.so.1 #36 0xb7dc1222 in Gtk::Main::run () from /usr/lib/libgtkmm-2.4.so.1 #37 0x08071f8b in sp_main_gui (argc=1, argv=0xbff07094) at ../../src/main.cpp:642 #38 0x0819e3c5 in Inkscape::NSApplication::Application::run (this=0xbff06ff0) at ../../src/application/application.cpp:117 #39 0x08070aea in main (argc=1, argv=0xbff07094) at ../../src/main.cpp:477 (gdb) Best regards, Khiraly

2 1

Minor bugs/lacks
by Khiraly 19 May '06

19 May '06

Hi! Im collecting some minor bugs what I was observing, hope there will some of them, which can easily fix for the release. # Alpha value does not work on page border and background The alpha value for the document border and document background does not work. If the alpha is 255, we have border, if the alpha is 1-254 wi dont have it. Document properties->Page->[Border]->Border color Document properties->Page->[General]->Background # Swatches Since there is lot of discussion about default enabling swatch in this release, I have collecting some lack of feature/bug. 1. swatch colors is not saved between inkscape session. So if I relaunch inkscape I must reset my palette to be used 2. palettes (in swatch) does not saved with inkscape .svg. Same as above 3. DnD does not work everywhere. For example in the stroke and fill dialog the DnD work only in the RGBA text input, and only in a limited way: a/ delete the active color from it (ex: a40000e1) b/ DnD the color from swatch c/ delete the '#' first character # minor tweaks needed on the command bars dialog buttons On the command bars, there are few dialog buttons (fill and stroke, text and font, xml editor, align and distribute, inkscape preferences, document properties). The first click show the dialog windows but the second click does not hide it. I think it would be the right behaviour. Best regards, Khiraly

2 3

[noreply@...34...: SourceForge.net Support: Over-quota notice for project: inkscape]
by Bryce Harrington 19 May '06

19 May '06

(I still haven't gotten a resolution on the previous quota request.) ----- Forwarded message from noreply@...34... ----- Date: Thu, 18 May 2006 04:06:22 -0700 From: noreply@...34... To: joncruz@...58..., buliabyak@...58..., mental@...58..., bryce@...58... Subject: SourceForge.net Support: Over-quota notice for project: inkscape Greetings, This is an automated quota-overage notice. Do not respond to this email, instead follow the instructions below if you have questions or concerns regarding this mailing. You are receiving this message as your SourceForge.net project, inkscape, is currently over its quota in its project group directory located on the SourceForge.net shell server. Your project has a 100000 k soft quota and your project is currently using 565324 k of disk. This new quota system allows us to track quotas granted to projects. Follow the instructions below to request a quota increase for your project to stop future mailings like this one from being sent to your project. The following command can be run at any time on the project shell server to check your project's disk usage: du -skx /home/groups/i/in/inkscape/ Please take action to reduce your project's disk usage as soon as reasonably possible, but no later than 2006-05-25. For your quick reference, you may access your user home directory using any SSH client: Host: shell.sourceforge.net Home Directory: /home/groups/i/in/inkscape/ Should you have problems accessing your user account, please refer to the site document "Coping with User Account Problems": https://www.sf.net/docs/C02 For further details on the usage and access of the project shell server, refer to the site document "Project Shell, Web and Database Services": https://www.sf.net/docs/E07 If you wish to request an increased quota for your project, or have further questions or concerns regarding this matter, submit a Support Request to the Alexandria project on SourceForge.net. However, please review your project's current disk usage, and prune out unneeded data now, before requesting the increased quota. https://sourceforge.net/tracker/?func=add&group_id=1&atid=200001 Thank you, SourceForge.net Support ----- End forwarded message -----

2 1

Crash while undoing pasted texts
by Mathieu Dimanche 19 May '06

19 May '06

I got a crash when doing the following : 1) open inkscape 2) select the text tool, click on canvas and type some text 3) do it once again in another part of the document 4) switch to select mode and select both texts 5) ctrl-C ctrl-V the selection 6) hit Ctrl-Z Crash with : ** ERROR **: file ../../inkscape/src/document-undo.cpp: line 128 (void sp_docume nt_maybe_done(SPDocument*, const gchar*)): assertion failed: (doc->priv->sensiti ve) aborting... Emergency save activated! am I the only one ? I'll look at that in a few hours I think mtou

4 3

"${datarootdir}" not expanded correctly
by Wolfram Quester 19 May '06

19 May '06

Hi, I tried to build a new svn-version of inkscape yesterday and while compilation is fine, I get into some runtime trouble. When I run inkscape, it says: > ** (inkscape:6598): CRITICAL **: Inkscape::XML::Document* sp_repr_read_file(const gchar*, const gchar*): assertion `Inkscape::IO::file_test( filename, G_FILE_TEST_EXISTS )' failed > > ** (inkscape:6598): WARNING **: Unable to read keys file ${datarootdir}/inkscape/keys/default.xml > > ** (inkscape:6598): WARNING **: failed to load icon 'file_import' > > .... lots of faile to load icon... As indicated by the warning it seems the ${datarootdir} variable ist not expanded correctly during ./configure. Indeed, 'strings inkscape' shows a lot of occurrences of ${datarootdir} and config.h contains the lines > #define INKSCAPE_DATADIR "${datarootdir}" > #define PACKAGE_LOCALE_DIR "${datarootdir}/locale" To compile, I did the following: make distclean ./autogen.sh ./configure --prefix=/tmp DESTDIR=/tmp make make install A few days ago this worked flawlessly. Does someone have a clue what's going wrong here? BTW, not using --prefix and DESTDIR doesn't change anything. Thanks for your help, Wolfi PS: output from ./autogen.sh: --1. distribution------------------------------------------------------------ Debian GNU/Linux testing/unstable (etch/sid) --2. tools------------------------------------------------------------------- /usr/bin/m4: /usr/bin/autoconf: autoconf (GNU Autoconf) 2.59d /usr/bin/autoheader: autoheader (GNU Autoconf) 2.59d /usr/bin/automake: automake (GNU automake) 1.9.6 /usr/bin/automake-1.7: automake (GNU automake) 1.7.9 automake-1.8: not found /usr/bin/automake-1.9: automake (GNU automake) 1.9.6 /usr/bin/aclocal: aclocal (GNU automake) 1.9.6 /usr/bin/aclocal-1.7: aclocal (GNU automake) 1.7.9 aclocal-1.8: not found /usr/bin/aclocal-1.9: aclocal (GNU automake) 1.9.6 /usr/bin/intltoolize: intltoolize (GNU intltool) 0.34.2 /usr/bin/gettextize: /usr/bin/gettextize (GNU gettext-tools) 0.14.5 /usr/bin/libtoolize: libtoolize (GNU libtool) 1.5.22 --3. environment variables--------------------------------------------------- PATH=/home/wolfi/src/XCrySDen/:/home/wolfi/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/usr/X11R6/bin:/home/wolfi/src/XCrySDen//scripts:/home/wolfi/src/XCrySDen//util LANG=en_US.UTF-8 PYTHONPATH=:/home/wolfi/python:

1 0

Re: [gnu.org #288440] Inkscape frustrations?
by Bryce Harrington 18 May '06

18 May '06

On Thu, May 18, 2006 at 10:32:15AM -0400, Tony Wieczorek via RT wrote: > Hu Bryce. First, let me say that I love Inkscape! One of the sysadmins > in our office was blown back by all the funtionality it has. I use it > quite often these days, to design stickers and posters. Cool. :-) > My frustrations were with exporting the sign in a format that Kinkos > would understand. Perhaps I should have made it clearer that my > frustrations weren't with using Inkscape so much as they were with > dealing with all the various file formats. The format choices were > confusing - especially since I didn't know that Kinkos couldn't open the > Inkscape SVG, but seemed to be able to open the regular SVG format. It > might have been helpful to get a rough estimate of how large the files > would be once I saved them - certain Aha, yes this was my guess. The file format frustrations are very, very common. These are tough to solve because as you can imagine they're a tad outside our core scope, but you'll be happy to hear we've been speaking with others in the free software community (especially Cairo and Scribus) with more experience than us, and hope to have PDF and EPS working much more solidly in the future. Meantime, it's actually quite exciting to hear that Kinko's supports any variant of SVG at all - I would have guessed SVG to be too "niche" still for them. Note that the "plain SVG" format is stripped down form of SVG; Inkscape's SVG adheres 100% to the SVG standard. The "plain SVG" option avoids using otherwise valid SVG syntax that we have found that other programs have trouble with. Thus, it's there for exactly the situation you were in, and it's good to hear that it worked! > I appreciate you taking the time to write in and see if you've addressed > the problems I had. I certainly love the work you all do and the > progress you are making on an excellent project. Thanks so much. Sure thing, hope you don't mind if I cc the team. And thank you from us for all the important work the FSF does, to help ensure the rest of us can keep doing what we're doing. Bryce > > Someone pointed me at your 4/26 article, which mentioned some > > frustrations using Inkscape to create a sign. Would you mind > > elaborating on what those issues were? I'm one of the Inkscape > > developers, and since we're preparing a new release soon, would like a > > chance to see if we've addressed those problems. > > > > Thanks, > > Bryce > > > > > > > -- > Tony Wieczorek > Program Assistant > (617) 542-5942 > > Free Software Foundation > 51 Franklin St. Fifth Floor > Boston, MA 02110 USA

1 0

Re: [Inkscape-devel] Re: covermount cd-rom distribution request
by Nicu Buculei (OCAL) 18 May '06

18 May '06

Derek Hinchliffe wrote: > On 5/18/06, Nicu Buculei <nicu@...398...> wrote: >> >> Could the meaning of (3b) be stretched and the mention of the >> availability of the source code at http://inkscape.org be understood as >> a written offer to provide the source code? >> > > http://www.gnu.org/licenses/gpl-faq.html#TOCDistributeWithSourceOnInternet > > That FAQ specifically addresses CD via mail order vs FTP, but I think > the same would apply to a CD distributed on a magazine. Indeed, this is the letter of the FAQ, but it really shows the age of the 2.0 version of the GPL, not only we now use other protocols for downloading files (HTTP or p2p instead of FTP), but today downloading is much more convenient compared with mailing a physical disc. I work also with OpenOffice.org where the *official* redistribution policy is "include the source code *or* tell the users where it is (http://www.openoffice.org)" (emphasis mine), and this policy generated a huge redistribution network (and, arguably, a large number of users) -- nicu Open Clip Art Library: http://www.openclipart.org my cool Fedora wallpapers: http://fedora.nicubunu.ro/wallpapers/

3 2

Not about node sculpting, but UI...
by Vladimir Savić 18 May '06

18 May '06

In the spirit of node sculpting debate, I felt free to say something about Inkscape's UI in general. :) Just my observations (from user's perspective). 1) I would make Freehand drawing tool an option of Pen tool. Pen tool - Bezier curves and straight line (default) - Freehand drawing (top toolbar option and configurable auto-turning-on option when "stylus" or "eraser" input device is enabled and Pen tool selected) For about year and a half of using Inkscape this tool has been picked only 10-20 times. :) 2) Rename Star and polygon tool to Figure tool(?) Figure tool - Polygon - Star (- Comic book balloon - will be requested more of these in the future, I'm sure...) 3) On canvas gradient tool - if object has no gradient fill/stroke - should be able to detect if selected object has fill or stroke activated and edit existing one. In case of both activated do top toolbar selected editing. Current default adds unnecessary fill/stroke to an object. 4) Selector tool First LMB click - Scale Second LMB click - Rotation/skew Third LMB click - Perspective I see all of these as overall object editings. This way perspective should be relatively easy to find, I think. First thing I do when I try new graphic application is to click on some object few times to see if something's happening. Don't know about others... 5) Snap to... Would like to see snapping options in that top toolbar always easy accessible. Tools that will benefit: Node, Rectangle, Circle, Shape, Spiral, Pen, Bezier, Text and Gradient. Again, all written here are my aloud thinkings. I don't expect positive feedback on any but would like to hear comments. I think that adding more tools in toolbox will just make things worse and will clutter the desktop. And that's already happening. Cheers, Vlada

6 9

Building Mac OS X .dmg packages
by Arjan Molenaar 18 May '06

18 May '06

Hi, I'm Arjan Molenaar, maintainer of the Gaphor (http://gaphor.sourceforge.net), a GTK+ based UML modeling tool. I'm getting several requests for an easy to install package (.dmg) for OS X. Since Inkscpae is also a pure GTK+ based application having a OSX package, I was wondering if one could tell me how to build such a package. I have an iBook at my disposal and have Gaphor up and running on OSX. Could you give me some pointers/examples/whatever on how to create a nice packages application for Gaphor? Thanks in advance, Regards, Arjan Molenaar

3 4

Short Delay in Feature Freeze
by Bryce Harrington 18 May '06

18 May '06

Hi all, After checking into the status of the layer dialog and text toolbar, it looks like significant benefits will be had by delaying the Feature Freeze a few more days. So let's push it back to the 20th. It probably seems like we're being awfully tentative in pushing into freeze, but my feeling is that minimizing the length of time we are in feature freeze, the less painful the release process will be in general. So I would rather delay Feature Freeze to let things finish ripening, than to push into bug fixing mode, and end up needing to continually delay the Hard Freeze date or the release date. It's also been quite inspiring to see the team coming together and focusing on the major features - like the layer dialog and text toolbar - that we know users are really looking forward to in this release. Anyway, to reiterate: Currently, please refrain from adding new features in the main codebase (use branches instead), but keep putting time into polishing existing features. Plan to wrap up by Saturday the 20th. Bryce

1 0