- Inkscape Devel - Inkscape Mailman

"COMPUTERBILD"?
by Bryce Harrington 15 Apr '05

15 Apr '05

Hi all, I've been emailed by someone from a magazine called "ComputerBild", that is said to be popular in Europe. Could someone confirm for me that it exists? Bryce

2 1

Errors and warnings
by Jon A. Cruz 15 Apr '05

15 Apr '05

"The time has come," the Walrus said, "To talk of many things: Of shoes--and ships--and sealing-wax-- Of cabbages--and kings-- And why the sea is boiling hot-- And whether pigs have wings." so... we do have many things to deal with. g_log... g_warning... fprintf(stderr... magic dialog output... What's the plan for a grand unification of this all? First, there are a few classes getting setup that would appear to deal with this. When should each be used, and where. Second, what should the messages be? What are the rules for the types, contents, internationalization, etc. Not sure if this best starts here on the list, or on the Wiki. I've setup a stub page to get filled in eventually. http://www.inkscape.org/cgi-bin/wiki.pl?ErrorsAndWarnings

4 5

Pssssst
by Jon A. Cruz 14 Apr '05

14 Apr '05

Pssssssst... shhhh... Try dragging off of color swatches now. :-)

2 3

Re: [Inkscape-devel] inx files
by unknown＠example.com 13 Apr '05

13 Apr '05

On Thu, 7 Apr 2005 aaron@...749... wrote: > Perhaps I will have to learn to read C++ sooner than I had wanted to. :) > Is there a DTD? Well, there isn't. This is partially for two reasons: 1) I'm lazy 2) I don't know how to (see 1) If you'd write one, I'd maintain it as I make changes to the format (should be pretty stable at this point though). I think that I've heard XSchema is better, but I don't know enough about them. > > As far as passing to scripts, how do you want it? We've discussed it in > > the past, but it never got implemented. I was thinking something like > > "./myscript --name=value" > > That is exactly what I would expect. Okay, I'll get on to adding that. > > but as the most active script developer, how > > ever you'd like would be germane in my eyes. > > A very sad commentary on the state of the art, don't you think? :) Yes, but I don't blame people. It is still a black art without enough functionality to do really cool things. That is starting to change though. --Ted

4 9

Re: [Inkscape-devel] Effects on Win32
by unknown＠example.com 13 Apr '05

13 Apr '05

Sending this again because I never saw it come through on the list. ted@...11... wrote: > On Tue, 12 Apr 2005 aaron@...749... wrote: > >>Ok. I spent a little more time on this. In script.inx file, this works >>on Linux: >> >><command reldir="extensions">script.py</command> >> >>And this works on Windows: >> >><command reldir="path">python "C:\Path\To\Script\script.py"</command> >> >>What is the proper syntax for a write once run anywhere *.inx file? > > Well, I think that the problem is that we don't have one. I'm open to > suggestions. Does that mean that Windows won't execute the #! at the top > of files? Windows uses an association between file extension and applications that is stored in the registry. I have a bunch of random thoughts/questions: -with option one can Inkscape be taught to call the script in such a way that windows can choose the interpreter properly (and function with pipes)? -what other platforms will have special nuances that need to be delt with? -with option two could the inkscape extensions directories be added to a search path environment variable (like java classpath) that is used by the interpreter to avoid absolute paths? -Could inkscape be given a more flexible way to construct the command line? eg. <interpreter reldir="path">python</interpreter> <scriptfile reldir="extensions">script.py</scriptfile> would yeild 'python "path to script/script.py" params...' -Could scripts run on the embedded interpreter? Aaron Spike

3 3

Effects on Win32
by unknown＠example.com 12 Apr '05

12 Apr '05

Has anyone tried to use effects on Win32. I tried it at work today and failed. When I try to run a script I get: ** (inkscape.exe:2648): CRITICAL **: file extension/implementation/script.cpp: line 586 (virtual void Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension::Effect*, SPView*)): assertion 'mydoc != NULL' failed I'm having great difficulty diagnosing whether it fails before or after running the script. Is it supposed to work? Aaron Spike

3 7

Donation
by Bryce Harrington 12 Apr '05

12 Apr '05

FYI, another donation came in yesterday, in the amount of $92.50. ($100 - $2.50 (PayPal) - $5 (SourceForge)) The message was: "In support of continued development of the wonderful program Inkscape!" This brings the current total to: $ 3.54 $ 8.48 $ 92.50 ------- $104.52 Bryce

1 0

Crash at Startup
by unknown＠example.com 12 Apr '05

12 Apr '05

I saw Ted's commit in ChangeLog, so I was excited to try the latest CVS. But after building it I found that it crashes immediately on startup. Starting program: /usr/local/bin/inkscape [Thread debugging using libthread_db enabled] [New Thread -1223991168 (LWP 9511)] ** (inkscape:9511): CRITICAL **: Inkscape::XML::Document* sp_repr_read_file(const gchar*, const gchar*): assertion `Inkscape::IO::file_test( filename, G_FILE_TEST_EXISTS )' failed ** (inkscape:9511): CRITICAL **: Inkscape::Extension::Extension* Inkscape::Extension::build_from_reprdoc(Inkscape::XML::Document*, Inkscape::Extension::Implementation::Implementation*): assertion `doc != NULL' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1223991168 (LWP 9511)] release<Inkscape::XML::Document> (r=0x0) at gc-anchored.h:57 57 if (!--_anchor->refcount) { Aaron Spike

1 3

Inkscape nightly builds now weak link against gtkspell
by Mike Hearn 11 Apr '05

11 Apr '05

Hi, I've written a patch, enclosed below, which uses relaytool to make gtkspell weak linked. In English, that means Inkscape will use it if it's available at runtime, but otherwise won't. It's like using dlopen, except that fewer code changes are required and it's generally a lot more convenient. This exposed some issue that I am still trying to track down, of a crash deep inside aspell. I am not sure why this occurs, but I see the same problem with AbiWord. I am starting to wonder if this is another C++ ABI issue, because whilst the GCC documentation explicitly states that mixing two libstdc++ versions in the same image will work fine, in practice it apparently does not (or at least, I cannot see any other reason for the failure). If anybody starts seeing crashes inside aspell with the current nightly builds, please let me know and maybe we can track this down. The patch currently defines the relaytool macro in configure.ac directly, but it should be in acinclude.m4 - I'll fix this stuff before submitting it officially. thanks -mike Index: configure.ac =================================================================== RCS file: /cvsroot/inkscape/inkscape/configure.ac,v retrieving revision 1.40 diff -u -p -r1.40 configure.ac --- configure.ac 3 Apr 2005 05:39:59 -0000 1.40 +++ configure.ac 11 Apr 2005 12:37:16 -0000 @@ -384,7 +387,34 @@ dnl ****************************** dnl Unconditional dependencies dnl ****************************** PKG_CHECK_MODULES(INKSCAPE, gtk+-2.0 >= 2.4.0 libxml-2.0 >= 2.6.0 libxslt >= 1.0.15 sigc++-2.0 >= 2.0.3 gtkmm-2.4 $ink_spell_pkg) + +dnl define the relaytool macro +dnl RELAYTOOL("gtkspell", GTKSPELL_LIBS, GTKSPELL_CFLAGS, gtkspell_weak=yes) +dnl Will modify GTKSPELL_LIBS to include a call to relaytool if available +dnl or if not, will modify GTKSPELL_CFLAGS to include -D switches to define +dnl libgtkspell_is_present=1 and libgtkspell_symbol_is_present=1 + +AC_DEFUN([RELAYTOOL], [ + if test -z "$RELAYTOOL_PROG"; then + AC_PATH_PROG(RELAYTOOL_PROG, relaytool, no) + fi + + AC_MSG_CHECKING(whether we can weak link $1) + + if test "$RELAYTOOL_PROG" = "no"; then + AC_MSG_RESULT(no) + $3="-Dlib$1_is_present -D\"lib$1_symbol_is_present(sym)=1\" $$3" + else + AC_MSG_RESULT(yes) + $2="\`relaytool --relay $1 $$2\`" + $4 + fi +]) + +if test "x$ink_spell_pkg" != "x"; then + RELAYTOOL(gtkspell, INKSCAPE_LIBS, INKSCAPE_CFLAGS, ) +fi dnl Shouldn't we test for libpng and libz? INKSCAPE_LIBS="$INKSCAPE_LIBS -lpng -lz" Index: src/dialogs/text-edit.cpp =================================================================== RCS file: /cvsroot/inkscape/inkscape/src/dialogs/text-edit.cpp,v retrieving revision 1.47 diff -u -p -r1.47 text-edit.cpp --- src/dialogs/text-edit.cpp 25 Mar 2005 01:55:24 -0000 1.47 +++ src/dialogs/text-edit.cpp 11 Apr 2005 12:37:16 -0000 @@ -362,17 +362,25 @@ sp_text_edit_dialog (void) GtkTextBuffer *tb = gtk_text_buffer_new (NULL); GtkWidget *txt = gtk_text_view_new_with_buffer (tb); #ifdef WITH_GTKSPELL - GError *error = NULL; - char *errortext = NULL; - /* todo: Use computed xml:lang attribute of relevant element, if present, to specify the - language (either as 2nd arg of gtkspell_new_attach, or with explicit - gtkspell_set_language call in; see advanced.c example in gtkspell docs). - sp_text_edit_dialog_read_selection looks like a suitable place. */ - if (gtkspell_new_attach(GTK_TEXT_VIEW(txt), NULL, &error) == NULL) { - g_print("gtkspell error: %s\n", error->message); - errortext = g_strdup_printf("GtkSpell was unable to initialize.\n" - "%s", error->message); - g_error_free(error); + +#ifndef libgtkspell_is_present + extern int libgtkspell_is_present; +#endif + g_print("one\n"); + if (libgtkspell_is_present) { + g_print("two\n"); + GError *error = NULL; + char *errortext = NULL; + /* todo: Use computed xml:lang attribute of relevant element, if present, to specify the + language (either as 2nd arg of gtkspell_new_attach, or with explicit + gtkspell_set_language call in; see advanced.c example in gtkspell docs). + sp_text_edit_dialog_read_selection looks like a suitable place. */ + if (gtkspell_new_attach(GTK_TEXT_VIEW(txt), NULL, &error) == NULL) { + g_print("gtkspell error: %s\n", error->message); + errortext = g_strdup_printf("GtkSpell was unable to initialize.\n" + "%s", error->message); + g_error_free(error); + } } #endif gtk_widget_set_size_request (txt, -1, 64);

1 0

gcc 4.0 rc1 available
by Bob Jamison 11 Apr '05

11 Apr '05

I saw this morning that the Gcc project has made a pre-release cut, announced here: http://gcc.gnu.org/ml/gcc/2005-04/msg00479.html It is very easy to install this version: 1) tar jxf gcc-4.0.0-20050410.tar.bz2 2) cd gcc-4.0.0-20050410 3) mkdir objdir 4) cd objdir 5) ../configure --disable-shared --enable-languages=c,c++ 6) make > /dev/null 7) (su) 8) make install The '--disable-shared' flag will build libstdc++ statically, so that we can deliver binaries to others without adding a dependency on the latest version. Bob

1 0