- Inkscape Devel - Inkscape Mailman

SWF Export - Supporting static library
by Brian 21 May '06

21 May '06

I was able to take the .swf export patch on the Sourceforge page and update it so it compiles with the current Inkscape/ming codebase. Now comes the fun of linking libming in as a static library. Out of the box, ming ships with a make target that builds a static version of the lib. I added the following entry into src/Makefile.am noinst_LIBRARIES = \ extension/internal/ming/libming.a \ But this wants to build libming. What do I need to do to simply link the libming lib in statically? Or would it be best to set up a Makefile_insert that builds a custom version of the Ming library? Brian

3 2

license and attribution
by Aaron Spike 21 May '06

21 May '06

I'm a chronic code copier, I know. But I just realized that I have made a few mistakes moving code around in our codebase. I moved PointToCurvilignPosition from libnrtext/Layout-TNG-OutIter.cpp to livarot/Path.cpp as was indicated in the orignial comment, "this function really belongs to Path. I'll probably move it there eventually, hence the Path-esque coding style." In doing this I forgot to copy the original copyright in the code. But much worse, I just realised that the files that I moved this code between are under different licenses. I moved a GPLed function into a PD file. This cannot happen. The possibility for other accidents in our codebase seems huge. I don't think PD and GPL can coexist well in a codebase that desires so much refactoring. Can we and should we place the PD files under the GPL? As for attribution, what is proper and customary? I suppose I need to chase down the orignial author through the commit logs any time I want to move a function or copy code. Very often people alter code without adding a copyright notice. I haven't added a notice to any of the files I have edited. Am I endangering people of doing the same copying without attribution to me? When should I attribute myself? Right now the act of adding my name to a source file seems rather proud to me. And right now I can't imagine ill will tward someone copying my code without attribution, but as I put more and more sweat and tears into the code that may become possible. Aaron Spike

5 4

object snapping (bug?), related RFEs
by Khiraly 20 May '06

20 May '06

Hi! Is object snapping supposed to work? Im talking about the recent svn version, and File->Document properties->[Snap] The options: [ ] Snap bounding boxes to objects [ ] Snap nodes to objects [ ] Snap to object paths [ ] Snap to object nodes Snap sensitivity: [-|-------------] [ ] Always Snap It took some time the figure out how it is working. 1. So If I want to snap one object node to an another object node I must check the following options: [ ] Snap bounding boxes to objects [X] Snap nodes to objects [ ] Snap to object paths [X] Snap to object nodes Snap sensitivity: [-|-------------] [ ] Always Snap 2. If I want to snap one object node to an another object path I must check the following options: [ ] Snap bounding boxes to objects [X] Snap nodes to objects [X] Snap to object paths [ ] Snap to object nodes Snap sensitivity: [-|-------------] [ ] Always Snap 3. If I check the above two cases it work a little buggy way. Particulary on a curved path. So I pull the mousepointer and sometimeworks sometime just jumping a little distance. Around the node is really hard to place the node. 4. If I check the following to options, it does snapping, but Im not able to figure out its snapping to what. [X] Snap bounding boxes to objects [ ] Snap nodes to objects [ ] Snap to object paths [X] Snap to object nodes Snap sensitivity: [-|-------------] [ ] Always Snap It does snapping, because the Snap sensitivity have its behaviour. 5. If I want to snap the bounding box around an object paths, I must check the following options: [X] Snap bounding boxes to objects [ ] Snap nodes to objects [X] Snap to object paths [ ] Snap to object nodes Snap sensitivity: [-|-------------] [ ] Always Snap ------------------ The problems: The bigger problem is the not clear UI design, its not marked anywhere what I must check If I want some behavoiour. And it does not marked, that one checkbox *depends* an another checkbox. 'Always snap' button does not seems to work. What is supposed to do? Its not clear that the 'Snap sensitivity' GtkHScale element affects ALL the other checkboxes. I was thinking yesterday, that the snappings are not implemented, because I was unable to figure out what checkbox must I checked. So I think it must seriously reconsider this ui design, because this EXCELLENT feature is really a MUSTHAVE. I have found and figured out accidently, and I have already written my feature request for this feature, which is already implemented! (just figured out a Snapping title in the recent changelog) ---------------- Question/rfe about the snapping issues: There is an option (like the new show/hide bezier handles option) to show the nodes of all the objects? It would be easier to snapping. And more speedy to create nice diagrams, flowcharts, etc. ---------------- This feature CLOSE the following RFE (I think): [1014477]Snap (is already closed, but now is fully implemented): https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1326224] Snap to curve and snap to node: https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [907478] Snap to (nodes of) existing objects: https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1252641] Snap objects to nodes of other objects (DUP of #907478): https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1108238] snap bounding boxes to each other: https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1306873] In node tool, nodes/handles must always snap w/ grid on https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [903432] Snap selection to grid command: https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1424653] Snap behavior instability (This is not implemented, but it can easily achieve with the recent snapping possibilities): https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1418315] Grid: option to snap to upper left corner only (DUP of #1424653) https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… ----------------- Related RFEs, which is NOT IMPLEMENTED, but depends on the above implementation: [1104630] Special fixing points to allow objects to snap together (Its like in Microsoft Visio, or DIA, where one object can snap some autogenerated fixing points. It can workaround by adding additional nodes, but there arent any more elegant way?): https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1421855] Snap to Grid (There should be an option to active/deactivate the Snap to Grid without going to Document Preferences): https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1328200] snap icons in toolbar (DUP of #1421855) https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [863737] Snap indicator+ snap/guides dialog/palette (DUP of #1421855) https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1213890] Guides to Snap to Grid (almost everything can be snapping except GUIDES to GRID/BOUNDING BOX/NODE): https://sourceforge.net/tracker/?func=detail&atid=604309&aid=1213890&group_… [1328174] snap guides to nodes (DUP of #1213890, we can merge the two rfe) https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1213890] Guides to Snap to Grid (DUP of #1213890): https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [928027] advanced snap features (missing features, but it can easily workaround by adding some nodes to the object): Snap to Endpoint, Snap to Midpoint, Snap to Intersection): https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1390687] snap to path imprecise in some cases: https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… ------------- RFEs what is related, but I cant decide is it resolved or not. [1215241] snap to guides with screen pixels (I cant understand what is the difference between screen and document pixels) https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1119020] snap only to visible gridlines, snap distance in screen px (DUP of #1215241): https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… [1390676] On-screen-pixel distance as snap to... unit (DUP of #1215241) https://sourceforge.net/tracker/?group_id=93438&atid=604309&func=detail&aid… -------------- Proposal: Can we consider to close ALL the feature request about snapping? And create one new feature request, where we summarize what snapping feautres was implemented, and what needs to be implemented. So we can close the feature request what is implemented, and mark as DUPLICATE of the above RFE all the other feature requests. However with this RFE, we can track all the snapping issues and roadmap. Sorry for my english, and thanks if you have read all my email;) Best regards, Khiraly

7 26

Gradient ids change between 0.43 and SVN in my files
by Jean-François Lemaire 20 May '06

20 May '06

Hello, I've got a serious problem regarding gradients with last days' Inkscape SVN. Something changed that screws up the gradients ids of files I created with previous SVN builds. To make things clearer: If I create today an object with gradient fill with, say, Inkscape 0.43 stable and open it in Inkscape SVN, the gradient is correctly displayed. If on the other hand I open the files I created and worked on earlier with Inkscape 0.43 in Inkscape SVN, *all* the gradients are mis-attributed and do not display. They are present in the gradients drop down menu, but their ids no longer correspond to what is specified in <defs>. If I vacuum the defs, the gradients are deleted since they are not used by any object. Here's a link to a file that contains 24 objects, almost all of them with gradients: http://users.skynet.be/jflemaire/files/gradients_issue.svg (Incidentally, this file displays correctly in Konqueror.) I hope someone with more knowledge of SVG/Inkscape will be able to help, because I dread the moment I'll have to reassign all gradients to each objects manually! Cheers, JFL -- Jean-François Lemaire

5 5

Inkscape UI
by Kevin Cannon 20 May '06

20 May '06

Hi all, I've been following Inkscape's development for some time, and it's always looked like it had quite a lot of promise. I was looking for an open source vector tool to recommend to someone today and thought I'd download it to see how it's coming along. I'm happy to say that it's improved a lot since I last used it. I've very impressed. The one thing I'm concerned about is the UI. I'm a web designer by trade and while Inkscape is quite full featured, the UI is a bit of a leap to what I'm used to, which makes transition very hard. I read your wiki, and I understand wanting an Inkscape specific UI is important and I agree that just aiming to be an Illustrator clone wouldn't be a worthy goal. However, I think you could win a lot of hearts and minds by conforming to general UI elements that are used in graphics packages. During Firefox's early development, they made the conscious decision to match some of IE's shortcuts (alt+d, backspace for example) and some of it's conventions. The aim was to reduce the barrier to entry, and to make it feel more familiar, and it was one of the factors in it's success. I would strongly suggest you make designers feel more at home when they give Inkscape a try. Things like pressing spacebar to pan around a page is a de facto standard amongst image editing tools. I'd say it would be trivial to make Inkscape work in the same manner. Similarly, your path nodes/handles tool are the same as the 'white arrow' tool in other apps. Changing that so it matches would again dramatically increase the accessibility of the software, and I believe seriously increase your usage figures. These are some small examples of what I'm talking about. As a designer, I'm designing interfaces every day, and creating a low barrier to entry is crucial for my clients. I innovate in certain areas, but know that some things need to stick to conventions or else people will never use the sites I build. Inkscape is a great tool, but it's broken some of those conventions, and that will frustrate and annoy users when they try to apply their current knowledge to this application, and that is a waste. You needn't lose potential users when Inkscape is so very good, just because they're confused. I would strongly suggest that you make efforts to remove those barriers while staying true to your goals. I'm not a coder so I cannot offer my services in that regard, but if you want to change some things to make the UI more friendly to new users, then I will happily offer my services in identifying issues. I sincerely hope you'll take me up on my offer, Kind Regards, - Kevin Cannon

11 27

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

Love is a canvas furnished by Nature and embroidered by imagination
by malena rhonda 18 May '06

18 May '06

1 0

Re: covermount cd-rom distribution request
by Bryce Harrington 18 May '06

18 May '06

Hi Johan, yes this is fine, as long as you also mention that it is Open Source, and that they can get the source code at http://inkscape.org. Thanks, Bryce On Wed, May 17, 2006 at 05:04:02PM +0200, Johan Vandecasteele wrote: > Hello, > > I'm Johan Vandecasteele, marketingmanager of Belgium's leading computer consumer magazines Clickx Magazine and PC Magazine. We are including a free covermount cd with our Clickx Magazine n? 122 (June 27 2006), and we would like to include Inkscape on that cd. > > Can you please tell us if we can have your permission to do so. Please visit our website www.clickxmagazine.be for information on our magazine. The download link to our mediakit is http://sales.minoc.com/newsletter/MediakitFull_Minoc_2006_ENG.pdf - it will give you some idea of our company and portfolio. > > Hope to hear from you soon, > > Kind regards, > > Johan Vandecasteele > > -------------------- > Johan Vandecasteele > marketingmanager Minoc Business Press > > Clickx Magazine | FWD | PC Magazine | Smart Business Strategies | ZDNet.be | GameSpot.be > www.clickxmagazine.be | www.fwdmagazine.be | www.pcmagazine.be | www.zdnet.be | www.gamespot.be > > Tel: 0032 14 44 20 61 | Fax: 0032 14 44 20 66 > Minoc Business Press NV | Everdongenlaan 15 bus 1 | 2300 Turnhout | Belgium

3 3

RE: Inkscape-devel digest, Vol 1 #1878 - 12 msgs
by Joc 18 May '06

18 May '06

>Message: 12 >Subject: Re: [Inkscape-devel] NEW: node sculpting >From: Tavmjong Bah <tavmjong@...8...> >To: bulia byak <buliabyak@...400...> >Cc: Inkscape Devel List <inkscape-devel(a)lists.sourceforge.net>, >Inkscape Users List <inkscape-user(a)lists.sourceforge.net> >Date: Wed, 17 May 2006 12:07:26 +0200 > > >> I'm not sure I understand this, can you draw an illustration? > >See the attached illustration of attempting to put text on a can. The attachment did not get decoded properly at my end, but the image can be seen by copying the base64 data (without the MIME info) to: http://www.toastedspam.com/decode64 Joc

1 0

NEW: node sculpting
by bulia byak 18 May '06

18 May '06

http://www.inkscape.org/screenshots/gallery/inkscape-0.44-nodesculpting.png An entirely new way of manipulating paths in Node tool is added in this version: Node sculpting. Normally, when you have several nodes selected and you drag one of them, all selected nodes move by the same amount. Now, if you Alt-drag one of the selected nodes, only that node is fully displaced; other selected nodes are moved less than the full amount, so that those farthest from the drag point remain stationary. So, for example, if you select several nodes on a straight line and Alt+drag the middle selected node, the path will bend into a smooth bell-like curve. Nodes' handles are also adjusted correspondingly to keep the overall shape smooth and natural. (If you don't have enough nodes on a path fragment that you want to reshape in this way, just select the end nodes of that fragment and press Ins a few times to populate it with nodes.) Moreover, node sculpting is sensitive to pressure of your tablet pen. If you press slightly, your curve will have a narrow sharp tip (i.e. the nearest neighbors of your dragged node will move only a bit); if you press hard, the curve's tip will be wide and blunt (i.e. the nearest neighbors will move almost as much as the dragged node). (Hint: to stop dragging without losing your shape, first release Alt and then lift the tip of the pen.) There are many possible applications of the sculpting technique. To take a simple example, selecting all nodes of an ellipse-like shape and Alt+dragging one of them will smoothly and naturally stretch and skew the entire shape in any direction. Doing the same to a complex path, such as star or spiral, will twist and punch it without destroying its intricate structure - this is the way to get squashed or self-intersecting stars, eccentric spirals and other shapes not easily doable before. Selecting only part of all nodes allows you to smoothly reshape parts of the figure without disturbing the rest. Especially useful node sculpting is for complex natural paths, such as calligraphic strokes or bitmap traces, where you often want to do large-scale pushes and bends without destroying the small-scale features. Things like making a calligraphic stroke narrower in one place and wider in another, or extending the ear or flattening the nose of a head, or any other reshaping of complex paths - all this is now much faster and more natural to do using sculpting. Starting from en ellipse with added nodes, it takes just a few Alt+drags to tweak it into a silhouette of a head, or a map of Australia, or an Inkscape logo! -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

15 37

Re: [Inkscape-user] layer icons
by Jon A. Cruz 17 May '06

17 May '06

On May 16, 2006, at 10:23 AM, Jakub Steiner wrote: > I suggest simplifying those icons to the core of what they are > trying to > say. Use distinguishable silhouettes, color. An image is worth more > than > my poor writing: > > http://jimmac.musichall.cz/stuff/visual-noise.png That does make things look much prettier... ... however, do you have an idea how that can tie into the logical work being done with Tango and the ArtLibre stuff? http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec- latest.html http://tango-project.org/ArtLibreSet The latter does have some names for layer raise, lower, etc. Basically, would you suggest to use the base "go-*" names/icons in the dialog, and the layer ones elsewhere (e.g. menus and toolbars)?

3 2

dxf import
by Alexandre Prokoudine 17 May '06

17 May '06

Greetings, In release notes for 0.43 it is mentioned that there is a standalone utility to import DXF files that was developed by Matt Squires. This code has moved to Inkscape's trunk since then (three months ago). I'm curious if it should be mentioned in release notes for 0.44, since Inkscape has only DXF export for desktop plotters officially now ;-) Alexandre

2 2

Minor bug on layer dialog
by Khiraly 17 May '06

17 May '06

Hi! I use inkscape-20060517-0200.tar.bz2 tarball. So the most annoying layer bugs are corrected (or it seams at least;). I have found one minor problem and a minor weakness: * when you click multiple time on the 'Raise current layer' icon (or the 'lower current layer'), only the first click seems to working. The second click does not move the current layer above an another one layer. However I you click on an another icon and reclick the 'Raise current layer' it works again. I hope its clear;) * double clicking on layer does not popup a dialog to rename it. You are forced to use the menu. It's really a minor weakness, normally rarely rename the layer;) Khiraly

1 0

Re: [Inkscape-user] layer icons
by Bryce Harrington 17 May '06

17 May '06

On Tue, May 16, 2006 at 07:23:00PM +0200, Jakub Steiner wrote: > Howdy. > I'm very pleased by the introduction of a layer window. Will help > greatly to manage more complex artwork. [Setting Reply-to to inkscape-devel@] > I noticed however the button icons are quite poor in doing what they > should - being easier to distinguish than text labels. They all include > the rectangle signifying "layer". But the fact that this element appears > on evey single one of them makes it nothing but visual noise. > > I suggest simplifying those icons to the core of what they are trying to > say. Use distinguishable silhouettes, color. An image is worth more than > my poor writing: > > http://jimmac.musichall.cz/stuff/visual-noise.png That does look quite a bit clearer. > Having said all that, I don't think the metaphor for delete you see on > the mockup is particularly strong. Could you explain what might be better? Bryce

3 2

build problem
by Khiraly 17 May '06

17 May '06

Hi! I have downloaded this source snapshot: http://inkscape.modevia.com/svn-snap/inkscape-20060516-0400.tar.bz2 I have debian sid, what I did: tar -xjvf inkscape-20060516-0400.tar.bz2 cd inkscape-20060516-0400 cat debian/control |grep -i build # install all the dependencies chmod +x debian/rules dpkg-buildpackage -rfakeroot -uc -b It fails with the following compile error: if i486-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../src -I.. -I/usr/include/freetype2 -pthread -DORBIT2=1 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/bonobo-activation-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/gconf/2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/freetype2 -DPOTRACE=\"potrace\" -pthread -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/atk-1.0 -I/usr/include/libxml2 -I/usr/include/gtkspell-2.0 -I../../cxxtest -Wall -W -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -g -O2 -MT dialogs/layer-properties.o -MD -MP -MF "dialogs/.deps/layer-properties.Tpo" \ -c -o dialogs/layer-properties.o `test -f 'dialogs/layer-properties.cpp' || echo '../../src/'`dialogs/layer-properties.cpp; \ then mv -f "dialogs/.deps/layer-properties.Tpo" "dialogs/.deps/layer-properties.Po"; \ else rm -f "dialogs/.deps/layer-properties.Tpo"; exit 1; \ fi /usr/include/gtkmm-2.4/gtkmm/treeview.h: In member function 'int Gtk::TreeView::append_column_editable(const Glib::ustring&, const Gtk::TreeModelColumn<ColumnType>&)': /usr/include/gtkmm-2.4/gtkmm/treeview.h:1424: warning: statement has no effect /usr/include/gtkmm-2.4/gtkmm/treeview.h: In function 'void Gtk::TreeView_Private::_connect_auto_store_editable_signal_handler(Gtk::TreeView*, Gtk::CellRenderer*, const Gtk::TreeModelColumn<ColumnType>&)': /usr/include/gtkmm-2.4/gtkmm/treeview.h:1681: warning: statement has no effect if i486-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../src -I.. -I/usr/include/freetype2 -pthread -DORBIT2=1 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/bonobo-activation-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/gconf/2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/freetype2 -DPOTRACE=\"potrace\" -pthread -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/atk-1.0 -I/usr/include/libxml2 -I/usr/include/gtkspell-2.0 -I../../cxxtest -Wall -W -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -g -O2 -MT dialogs/layers-panel.o -MD -MP -MF "dialogs/.deps/layers-panel.Tpo" \ -c -o dialogs/layers-panel.o `test -f 'dialogs/layers-panel.cpp' || echo '../../src/'`dialogs/layers-panel.cpp; \ then mv -f "dialogs/.deps/layers-panel.Tpo" "dialogs/.deps/layers-panel.Po"; \ else rm -f "dialogs/.deps/layers-panel.Tpo"; exit 1; \ fi ../../src/dialogs/layers-panel.cpp:27:30: error: src/widgets/icon.h: No such file or directory /usr/include/gtkmm-2.4/gtkmm/treeview.h: In member function 'int Gtk::TreeView::append_column_editable(const Glib::ustring&, const Gtk::TreeModelColumn<ColumnType>&)': /usr/include/gtkmm-2.4/gtkmm/treeview.h:1424: warning: statement has no effect /usr/include/gtkmm-2.4/gtkmm/treeview.h: In function 'void Gtk::TreeView_Private::_connect_auto_store_editable_signal_handler(Gtk::TreeView*, Gtk::CellRenderer*, const Gtk::TreeModelColumn<ColumnType>&)': /usr/include/gtkmm-2.4/gtkmm/treeview.h:1681: warning: statement has no effect ../../src/dialogs/layers-panel.cpp: In member function 'void Inkscape::UI::Dialogs::LayersPanel::_styleButton(Gtk::Button&, SPDesktop*, unsigned int, const char*)': ../../src/dialogs/layers-panel.cpp:70: error: 'sp_icon_new' was not declared in this scope make[3]: *** [dialogs/layers-panel.o] Error 1 make[3]: Leaving directory `/home/lama/Desktop/down/inkscape-20060516-0400/builddir/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/lama/Desktop/down/inkscape-20060516-0400/builddir' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/lama/Desktop/down/inkscape-20060516-0400/builddir' make: *** [build] Error 2 Can somebody help me what is wrong? For the record the simple ./configure && make success, without error. What information should I provide for further help? Best regards, Khiraly

4 4

Re: [Inkscape-user] layer icons
by Jon A. Cruz 17 May '06

17 May '06

On May 16, 2006, at 8:40 PM, Never you mind wrote: > go-up > go-top > go-down > go-bottom > edit-delete Updated in SVN with revision 11815

1 0