- Inkscape Devel - Inkscape Mailman

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

回复： Inkscape-devel Digest, Vol 50, Issue 46
by 海斌 30 Jul '10

30 Jul '10

error infromation: ============================= Make error line 299: problem compiling: In file included from src/2geom/d2.h:36: 0, from src/2geom/rect.h:40, from src/libnr/nr-rect.h:28, from src/sp-item.h:25, from src/sp-lpe-item.h:17, from src/sp-shape.h:18, from src/sp-path.h:16, from src/extension/internal/emf-win32-inout.cpp:29: src/2geom/interval.h: In member function 'bool Geom::OptInterval::isEmpty()': src/2geom/interval.h:241:46: warning: converting 'false' to pointer type for arg ument 2 of 'bool boost::operator==(const boost::optional<T>&, void (*)(boost::de tail::none_helper)) [with T = Geom::Interval, void (*)(boost::detail::none_helpe r) = void (*)(boost::detail::none_helper)]' In file included from src/2geom/d2.h:429:0, from src/2geom/rect.h:40, from src/libnr/nr-rect.h:28, from src/sp-item.h:25, from src/sp-lpe-item.h:17, from src/sp-shape.h:18, from src/sp-path.h:16, from src/extension/internal/emf-win32-inout.cpp:29: src/2geom/rect.h: In member function 'bool Geom::OptRect::isEmpty() const': src/2geom/rect.h:218:52: warning: converting 'false' to pointer type for argumen t 2 of 'bool boost::operator==(const boost::optional<T>&, void (*)(boost::detail ::none_helper)) [with T = Geom::D2<Geom::Interval>, void (*)(boost::detail::none _helper) = void (*)(boost::detail::none_helper)]' src/extension/internal/emf-win32-inout.cpp: In member function 'virtual SPDocume nt* Inkscape::Extension::Internal::EmfWin32::open(Inkscape::Extension::Input*, c onst gchar*)': src/extension/internal/emf-win32-inout.cpp:2356:73: error: invalid conversion fr om 'int (*)(HDC__*, HANDLETABLE*, ENHMETARECORD*, int, LPARAM)' to 'int (*)(HDC_ _*, HANDLETABLE*, const ENHMETARECORD*, int, LPARAM)' src/extension/internal/emf-win32-inout.cpp:2356:73: error: initializing argume nt 3 of 'BOOL EnumEnhMetaFile(HDC__*, HENHMETAFILE__*, int (*)(HDC__*, HANDLETAB LE*, const ENHMETARECORD*, int, LPARAM), void*, const RECT*)' ------------------ 原始邮件 ------------------ 发件人: "Krzysztof Kosiński"<tweenk.pl@...400...>; 发送时间: 2010年7月28日(星期三) 晚上11:30 收件人: "海斌"<itxyga@...400...>; 抄送: "inkscape-devel"<inkscape-devel(a)lists.sourceforge.net>; 主题: Re: [Inkscape-devel] Inkscape-devel Digest, Vol 50, Issue 46 2010/7/28 海斌 <itxyga@...400...> Andfoundnothingwrongduringinkscape,butinnoinkscapeexecutabledirectorygeneratedneededtosubscription-based. btool does best-effort compilation - in other words, if some file generates an error, it doesn't stop the compilation but compiles the rest of files. You are seeing no error for the last compiled file but there were errors earlier in the build process. Run btool again, it should show the errors. Regards, Krzysztof

2 1

call for marketing team
by Alexandre Prokoudine 29 Jul '10

29 Jul '10

Hi, http://wiki.inkscape.org/wiki/index.php/AnnouncePlanning048 is now in place, admittedly, mostly copy/pasted from AnnouncePlanning047. There is also a first shot at community announcement text there, plus adjusted tables (who announces what and where). I didn't touch most things there, just put myself where I could do things and adjust numbers from 047 to 048. Since we are somewhat shorthanded this time, how about getting organized with marketing? :) What's ultimately has to be done is: 1. Make sure the press-release sparkles. It merely shines through patina where it can right now. 2. Finish release notes: fill in missing information (Jon A. Cruz, I'm looking at you :)) and improve Highlights section. 3. Find more people to do announcements, and more places to announce at. 4. Actually announce. You don't have to take too much responsibility. All you need to do is a) tell us where you will announce, so we don't try to do things twice and b) be able to send announcement in a timely manner from the last approved edition of the text. I'm not sure where we are with actually releasing the final 0.48, so some kind of a clue would be helpful. Alexandre Prokoudine http://libregraphicsworld.org

1 0

Fill and Stroke Panel Layout
by Thorsten Wilms 29 Jul '10

29 Jul '10

Hi! Please have a look at 2 mockups about tightening up the Fill and Stroke Panel: http://thorwil.wordpress.com/2010/07/27/inkscape-fill-and-stroke-panel/ -- Thorsten Wilms thorwil's design for free software: http://thorwil.wordpress.com/

7 13

Multiple issues with the filter dialog
by Krzysztof Kosiński 28 Jul '10

28 Jul '10

Hello I noticed there are several issues with the filter effects dialog: 1. Wrong initial value for the "Type" combo box of feColorMatrix when adding a new filter effect or loading an existing one (patch snippet attached, please apply to 0.48 as well). 2. Undo does not work correctly: when modifying a parameter using a slider, undo does not restore the slider to its value at the start of the drag, but to intermediate positions during the drag. (Fixing this likely requires a substantial rewrite.) 3. It says feComponentTransfer is not implemented in Inkscape, but in fact it is. 4. Some sliders have completely bogus ranges. For example the surface scale slider on feDiffuseLighting operates in the absurd range [-1000, 1000] with a step of 0.1, whereas 90% of the useful values lie in the range [-1, 1]. [-5, 5] is a more appropriate choice. (I'll follow up with a ptach that fixes some of the more outrageous ranges.) Issues 2 and 3 could be worked on in the 0.49 dev cycle. Regards, Krzysztof

7 20

Re: [Inkscape-devel] Inkscape-devel Digest, Vol 50, Issue 46
by 海斌 28 Jul '10

28 Jul '10

I btool input commands in XP, under the compiler to as follows: cc : compile of build/obj/xml/subtree.o required by source: src/xml/subtree. cpp ============ cmd ============ mingw32-g++ -c -Wall -Wformat -Werror=format-security -W -Wpointer-arith -Wcast- align -Wsign-compare -Woverloaded-virtual -Wswitch -O2 -mms-bitfields -fopenmp - DVERSION=\"0.48+devel\" -DHAVE_CONFIG_H -D_INTL_REDIRECT_INLINE -DHAVE_SSL -DREL AYTOOL_SSL="static const int libssl_is_present=1; static int __attribute__((unus ed)) libssl_symbol_is_present(char *s){ return 1; }" -DPOPPLER_NEW_GFXFONT -I. - IH:\devlibs/include -IH:\devlibs/include/gtkmm-2.4 -IH:\devlibs/lib/gtkmm-2.4/in clude -IH:\devlibs/include/glibmm-2.4 -IH:\devlibs/lib/glibmm-2.4/include -IH:\ devlibs/include/glib-2.0 -IH:\devlibs/lib/glib-2.0/include -mms-bitfields -IH:\d evlibs/include/sigc++-2.0 -IH:\devlibs/lib/sigc++-2.0/include -IH:\devlibs/inclu de/giomm-2.4 -IH:\devlibs/lib/giomm-2.4/include -IH:\devlibs/include/gdkmm-2.4 -IH:\devlibs/lib/gdkmm-2.4/include -IH:\devlibs/include/pangomm-1.4 -IH:\devlib s/lib/pangomm-1.4/include -IH:\devlibs/include/gtk-2.0 -IH:\devlibs/lib/gtk-2.0/ include -IH:\devlibs/include/gtk-2.0 -IH:\devlibs/include/pango-1.0 -IH:\devlibs /include/pango-1.0 -IH:\devlibs/include/pango-1.0 -IH:\devlibs/include/cairo -IH :\devlibs/include/cairomm-1.0 -IH:\devlibs/lib/cairomm-1.0/include -IH:\devlibs/ include/atkmm-1.6 -IH:\devlibs/include/atk-1.0 -IH:\devlibs/include/gtk-2.0 -mms -bitfields -IH:\devlibs/include/gtk-2.0 -IH:\devlibs/lib/gtk-2.0/include -IH:\de vlibs/include/ImageMagick -IH:\devlibs/include/ImageMagick -fopenmp -D_MAGICKDLL _ -IH:\devlibs/include/libxml2 -IH:\devlibs/include/freetype2 -IH:\devlibs/inclu de -IH:\devlibs/include/cairo -IH:\devlibs/include/poppler -IH:\devlibs/include/ gc -IH:\devlibs/include/libwpg-0.1 -IH:\devlibs/include/libwpd-0.8 -IH:\devlibs/ include/libwpg-0.1 -IH:\devlibs/include/libwpd-0.8 -Icxxtest -IH:\devlibs/python /include -Isrc/bind/javainc -Isrc/bind/javainc/win32 -Isrc -Isrc/2geom -Isrc/2 geom/numeric -Isrc/application -Isrc/bind -Isrc/debug -Isrc/dialogs -Isrc/displa y -Isrc/dom -Isrc/dom/io -Isrc/dom/odf -Isrc/dom/util -Isrc/extension -Isrc/exte nsion/implementation -Isrc/extension/internal -Isrc/extension/internal/bitmap -I src/extension/internal/filter -Isrc/extension/internal/pdfinput -Isrc/extension/ script -Isrc/filters -Isrc/helper -Isrc/io -Isrc/jabber_whiteboard -Isrc/jabber_ whiteboard/dialog -Isrc/libavoid -Isrc/libcola -Isrc/libcroco -Isrc/libgdl -Isrc /libnr -Isrc/libnrtype -Isrc/libvpsc -Isrc/libvpsc/pairingheap -Isrc/livarot -Is rc/live_effects -Isrc/live_effects/parameter -Isrc/pedro -Isrc/svg -Isrc/trace - Isrc/trace/potrace -Isrc/ui -Isrc/ui/cache -Isrc/ui/dialog -Isrc/ui/tool -Isrc/u i/view -Isrc/ui/widget -Isrc/util -Isrc/widgets -Isrc/xml src/xml/subtree.cpp -o build/obj/xml/subtree.o ============================= I:\Inkscape\Src> And found nothing wrong during inkscape, but in no inkscape executable directory generated needed to subscription-based. ------------------ Original ------------------ From: "inkscape-devel-request"<inkscape-devel-request(a)lists.sourceforge.net>; Date: 2010年7月28日(星期三) 凌晨0:45 To: "inkscape-devel"<inkscape-devel(a)lists.sourceforge.net>; Subject: Inkscape-devel Digest, Vol 50, Issue 46 Send Inkscape-devel mailing list submissions to inkscape-devel(a)lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/inkscape-devel or, via email, send a message with subject or body 'help' to inkscape-devel-request(a)lists.sourceforge.net You can reach the person managing the list at inkscape-devel-owner(a)lists.sourceforge.net When replying, please edit your Subject line so it is more specific than "Re: Contents of Inkscape-devel digest..." Today's Topics: 1. Re: Avoiding opening new instances (Alexandre Prokoudine) 2. Re: Inkscape fund (Jasper van de Gronde) 3. Re: Inkscape fund (Alexandre Prokoudine) 4. Re: Multiple issues with the filter dialog (Krzysztof Kosi?ski) 5. Re: Inkscape fund (Joshua A. Andler) 6. Re: Avoiding opening new instances (Krzysztof Kosi?ski) 7. Re: Inkscape fund (Alexandre Prokoudine) 8. Re: Multiple issues with the filter dialog (Alexandre Prokoudine) 9. Re: Multiple issues with the filter dialog (Jon Cruz) ---------------------------------------------------------------------- Message: 1 Date: Tue, 27 Jul 2010 17:35:07 +0400 From: Alexandre Prokoudine <alexandre.prokoudine@...400...> Subject: Re: [Inkscape-devel] Avoiding opening new instances To: inkscape-devel(a)lists.sourceforge.net Message-ID: <AANLkTi=NqGsbxjUC26uP+a6H+bg3qX-bo__ROJT3Gv4+(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On 7/27/10, Martin Sucha wrote: > One possible approach would be to use IPC D-BUS :) Alexandre Prokoudine http://libregraphicsworld.org ------------------------------ Message: 2 Date: Tue, 27 Jul 2010 16:27:00 +0200 From: Jasper van de Gronde <th.v.d.gronde@...528...> Subject: Re: [Inkscape-devel] Inkscape fund To: Alexandre Prokoudine <alexandre.prokoudine@...400...> Cc: inkscape <inkscape-devel(a)lists.sourceforge.net> Message-ID: <4C4EECB4.1050002@...528...> Content-Type: text/plain; charset=UTF-8; format=flowed Alexandre Prokoudine wrote: > On 7/27/10, Jasper van de Gronde wrote: >> I noticed on the site that there is something called the Inkscape fund >> and I was wondering whether we actually use it or not. And in either >> case, who manages it and is there any information on how many donations >> we have received? > > There is no Inkscape fund. You misread it :) The following clearly says "Inkscape Fund": http://inkscape.org/donate.php > What does exist is http://linuxfund.org/ that we used to collect money > to pay Tav for his work on Text tool. The above does not seem to be (directly) related to linuxfund.org. ------------------------------ Message: 3 Date: Tue, 27 Jul 2010 18:52:46 +0400 From: Alexandre Prokoudine <alexandre.prokoudine@...400...> Subject: Re: [Inkscape-devel] Inkscape fund To: inkscape <inkscape-devel(a)lists.sourceforge.net> Message-ID: <AANLkTi=CbSwBRC42Ec928YcO-YG7vvv48HtBUo3eTMeZ@...401...> Content-Type: text/plain; charset=ISO-8859-1 On 7/27/10, Jasper van de Gronde wrote: >> There is no Inkscape fund. You misread it :) > > The following clearly says "Inkscape Fund": > http://inkscape.org/donate.php Oh, thanks for pointing out. That's the first time I hear about it. I cannot help you there other than saying that the page was last updated in August 2008 in SVN, so it looks like Ted or Bryce might have the answer for you. Alexandre Prokoudine http://libregraphicsworld.org ------------------------------ Message: 4 Date: Tue, 27 Jul 2010 17:00:21 +0200 From: Krzysztof Kosi?ski <tweenk.pl@...400...> Subject: Re: [Inkscape-devel] Multiple issues with the filter dialog To: Tavmjong Bah <tavmjong@...8...> Cc: inkscape-devel <inkscape-devel(a)lists.sourceforge.net> Message-ID: <AANLkTinKyRVGz5TNTLWxAmoiFdyNhGAmM19WJX2BPWYW@...401...> Content-Type: text/plain; charset=UTF-8 W dniu 27 lipca 2010 10:32 u?ytkownik Tavmjong Bah <tavmjong@...8...> napisa?: > It is a problem with our current interface that you cannot allow all > reasonable values and have the slider cover the potentially most used > range. Currently, the only way you can set values outside the > slider/entry box range is to use the XML editor so it is better to error > on the side of too large ranges than too small. It would be best if the slider had a limited range, but you could input an arbitrary value (or a value from a much larger range) using the spinbox. > 579932 Too much states saved for undo/redo when using sliders > <https://bugs.launchpad.net/inkscape/+bug/579932> The easiest fix is to set the sliders to Gtk::UPDATE_DISCONTINUOUS update policy, but this will prevent the display from updating during the drag. Apparently there is no way in GTK right now to get the correct behavior! Regards, Krzysztof ------------------------------ Message: 5 Date: Tue, 27 Jul 2010 08:05:59 -0700 From: "Joshua A. Andler" <scislac@...400...> Subject: Re: [Inkscape-devel] Inkscape fund To: Alexandre Prokoudine <alexandre.prokoudine@...400...> Cc: inkscape <inkscape-devel(a)lists.sourceforge.net> Message-ID: <1280243159.19496.32.camel@...2139...> Content-Type: text/plain; charset="UTF-8" On Tue, 2010-07-27 at 18:52 +0400, Alexandre Prokoudine wrote: > On 7/27/10, Jasper van de Gronde wrote: > > >> There is no Inkscape fund. You misread it :) > > > > The following clearly says "Inkscape Fund": > > http://inkscape.org/donate.php > > Oh, thanks for pointing out. That's the first time I hear about it. I > cannot help you there other than saying that the page was last updated > in August 2008 in SVN, so it looks like Ted or Bryce might have the > answer for you. It was created to collect donations and also for Mentors from GSoC who would rather the payments go to the project to have a place to defer them to. It's primarily used to assist with developer's travel needs to get to conferences and such. Cheers, Josh ------------------------------ Message: 6 Date: Tue, 27 Jul 2010 18:06:36 +0200 From: Krzysztof Kosi?ski <tweenk.pl@...400...> Subject: Re: [Inkscape-devel] Avoiding opening new instances To: Martin Sucha <martin.sucha-ml@...2313...> Cc: inkscape-devel(a)lists.sourceforge.net Message-ID: <AANLkTin=4DfW62o3tR0yadmD0u_VA04+=Q2MBEbRPn1M@...401...> Content-Type: text/plain; charset=UTF-8 2010/7/27 Martin Sucha <martin.sucha-ml@...2313...>: > One possible approach would be to use IPC to instruct a fully loaded inkscape > instance to fork and open the other document (which should be faster than > starting and fully loading completely new instance and allows OS to share > memory for us in a copy-on-write manner). This should reduce loading times > while maintaining a separate instance for a document (at the cost that any bad > state caused by a bug will be copied to the new instance), at least for > systems with reasonable fork implementation, I don't know how forks are > emulated on Windows in ported unix applications. I didn't think about it. It looks like a promising idea. Windows has ZwCreateProcess, which is an undocumented NT function that works like fork() including copy-on-write shared memory between the parent and child processes, so in principle this is possible. It would be wise to push the Win32 fork() implementation to Glib before using this. We could have one "master" instance that does all the initialization, handles preferences file writes, registers itself on DBus, and forks the "slave" window processes. The code executed in master after initialization should be reduced to minimum, so that a bug is unlikely. > One such factor that comes into my mind is command line execution in scripts > (with or without gui), the environment, user session, UUID, executable file > path are not different between uses, while a new instance should probably still > be used. We should do the following: if the option parsing bit decides that we are being run in non-GUI mode, we should not contact any other processes. If it decides we are being run in GUI mode, we should submit the results of option parsing to the master process, which will take care of performing all the work described in the command line. Forking a process from master when in command-line mode could sometimes be desirable, as it would speed up the execution of many Inkscape commands in quick succession. I also have to admit that it gets really complicated with forks, the master process, etc. so going for the simpler but less stable single-instance solution might be better for now. Once there is a fork() implementation in Glib, and the D-Bus binding and GSettings get merged into GIO (which should happen soon), we could start working towards a multi-process architecture. Regards, Krzysztof ------------------------------ Message: 7 Date: Tue, 27 Jul 2010 20:07:31 +0400 From: Alexandre Prokoudine <alexandre.prokoudine@...400...> Subject: Re: [Inkscape-devel] Inkscape fund To: Inkscape Devel List <inkscape-devel(a)lists.sourceforge.net> Message-ID: <AANLkTin+jgc-Cru_fSRP-VaHc=KY32zcSKkCMR9Gwbvm@...401...> Content-Type: text/plain; charset=ISO-8859-1 On 7/27/10, Joshua A. Andler wrote: > It was created to collect donations and also for Mentors from GSoC who > would rather the payments go to the project to have a place to defer > them to. It's primarily used to assist with developer's travel needs to > get to conferences and such. Oh well, I've just added the link to menu in includes/navigation.php and populated the translatable message over includes/localized-cs.inc includes/localized-de.inc includes/localized-en.inc includes/localized-es.inc includes/localized-fr.inc includes/localized-it.inc includes/localized-ja.inc includes/localized-ru.inc includes/localized.inc With luck the fund will be more evident now. Truly yours, Captain Obvious :) ------------------------------ Message: 8 Date: Tue, 27 Jul 2010 20:26:25 +0400 From: Alexandre Prokoudine <alexandre.prokoudine@...400...> Subject: Re: [Inkscape-devel] Multiple issues with the filter dialog To: inkscape-devel <inkscape-devel(a)lists.sourceforge.net> Message-ID: <AANLkTimF2VptZHrEpOFpDybqyvV=4edTOzgEP3Wd6KKo@...401...> Content-Type: text/plain; charset=ISO-8859-1 On 7/27/10, Tavmjong Bah wrote: > It is a problem with our current interface that you cannot allow all > reasonable values and have the slider cover the potentially most used > range. The other problem, as many times pointed out before, is that we do not tell users what some particular options mean (e.g. most of Turbulence or "Kernel Unit Length") and what units are used. Some tooltips are absolutely unhelpful, e.g. the one for Constant says "This constant affects Phong lighting model". This could be solved in part if we had a GIMP-style context sensitive on-line reference. But that's another story. Alexandre Prokoudine http://libregraphicsworld.org ------------------------------ Message: 9 Date: Tue, 27 Jul 2010 09:44:52 -0700 From: Jon Cruz <jon@...18...> Subject: Re: [Inkscape-devel] Multiple issues with the filter dialog To: inkscape-devel <inkscape-devel(a)lists.sourceforge.net> Cc: Tavmjong Bah <tavmjong@...8...> Message-ID: <37F02AEA-1B61-489F-AF3B-895D53A59DFC@...18...> Content-Type: text/plain; charset=utf-8 On Jul 27, 2010, at 8:00 AM, Krzysztof Kosi?ski wrote: >> 579932 Too much states saved for undo/redo when using sliders >> <https://bugs.launchpad.net/inkscape/+bug/579932> > > The easiest fix is to set the sliders to Gtk::UPDATE_DISCONTINUOUS > update policy, but this will prevent the display from updating during > the drag. Apparently there is no way in GTK right now to get the > correct behavior! There are a few ways to get good behavior. Some of these have come up for the color sliders. For this area the two big things to look at are using the might-be-more calls for undo and also to "debounce" the input from the slider so as to not trigger as many changes as the user moves things quickly. While the former will probably give some of the best 'fix' for this bug, the latter has potential to significantly improve the user experience. When I applied this to the color sliders it technically became slower, but to the users it felt much faster. It trades of raw numeric crunching speed for improved responsiveness to the user. But again, the root cause of the bug report appears to be from not using our proper under system calls. This may be direct or indirect. If it is the latter (function triggers events that calls functions that in turn register undo changes, etc.) then it might take a bit of cleanup to fix without breaking other cases. ------------------------------ ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ ------------------------------ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel End of Inkscape-devel Digest, Vol 50, Issue 46 **********************************************

2 1

Re: [Inkscape-devel] Avoiding opening new instances
by Martin Sucha 28 Jul '10

28 Jul '10

On Sunday 25 July 2010 01:40:13 Jon Cruz wrote: > On Jul 24, 2010, at 3:46 PM, Krzysztof Kosiński wrote: > > There are only two sane approaches: > > 1. Open every document in the existing instance. > > 2. Open each document in a separate instance. > [SNIP] > > Disadvantages of #2: > > - slower start > > - higher memory use - no data can be shared; if we use shared memory, > > the crashed instance could have corrupted it and the stability > > guarantee goes away; possible solution: read-only shared memory, but > > hard to implement in a portable manner One possible approach would be to use IPC to instruct a fully loaded inkscape instance to fork and open the other document (which should be faster than starting and fully loading completely new instance and allows OS to share memory for us in a copy-on-write manner). This should reduce loading times while maintaining a separate instance for a document (at the cost that any bad state caused by a bug will be copied to the new instance), at least for systems with reasonable fork implementation, I don't know how forks are emulated on Windows in ported unix applications. > > On each build we can generate an UUID to be stored in > > inkscape-version.cpp and start a new instance if there's no instance > > with this UUID already running. There's a little more complexity in > > it, because we need to generate a different exclusion ID for every > > user session, so if you log in locally, start Inkscape, then lock the > > screen and log in remotely via SSH, you can start a distinct instance > > of Inkscape. > > We also would need to tie things to different environment variables, etc. > If one launches an instance of inkscape with different XDG variables from > a current instance of the same version, things still should treat that as > 'different'. And there are a few other such factors to consider. So it > does look as if UUID itself does not solve the problem. > One such factor that comes into my mind is command line execution in scripts (with or without gui), the environment, user session, UUID, executable file path are not different between uses, while a new instance should probably still be used. Regards, Martin Sucha

5 6

Inkscape fund
by Jasper van de Gronde 27 Jul '10

27 Jul '10

I noticed on the site that there is something called the Inkscape fund and I was wondering whether we actually use it or not. And in either case, who manages it and is there any information on how many donations we have received?

3 5

Rev. 9657 missing file
by Krzysztof Kosiński 27 Jul '10

27 Jul '10

Hello Revision 9657 does not build because live_effects/parameter/powerstrokepointarray.cpp (and the associated header file) is missing. Johan, please add the missing file. Regards, Krzysztof

2 1