- Inkscape Devel - Inkscape Mailman

Path stroke position...
by Iuriatan Muniz 01 Nov '05

01 Nov '05

Hello guys... I'm new in the subject so please forgive any stupid thing I might say and, if possible, intruct me towards the path of glory !!! heheh =) I was thinking about the path stroke. Like when you draw an arc or sth... It would be nice if the stroke could be localized inside, centralized or outside the fill, like for applying alpha gradients on the stroke to get a (inner or outter) shadow effect... Of course it can be done describing 2 paths in the SVG file (I don't know if it is more like a technique or a feat we could implement), but isn't there a simpler way to do that under SVG specs ??? like a stroke parameter to set (it'd mean almost no overhead for who processes it) ??? Is it possible to suggest it for the 1.2 (or greater) comming W3C's specifications ??? Thats it... Thank you, Iuri

2 1

[Fwd: November 2005 of TUX, Issue 8]
by Jon Phillips 01 Nov '05

01 Nov '05

Yes, I've been AWOL, but have managed to get a column going in TUX (see FWD) and soon in Linux Magazine out of the UK. I'll be back online soon. Also, FYI, I work for Creative Commons now as an Open Source developer, so if there are any things I can field in that direction, you are in SF and want to come in and eat with me here (and get a free cc shirt), please ping me. ;) Jon -------- Forwarded Message -------- > From: no-reply@...851... > To: phillipsjd@...400... > Subject: November 2005 of TUX, Issue 8 > Date: Tue, 01 Nov 2005 13:42:44 -0600 > > Dear TUX Subscriber, > > Your November issue of TUX is now available for you to download, https://www.ssc.com/tx/issues/StartDownloadTUX.php?issue=8&month=November&y… . > > This issue features: > > *From the Publisher: Linux on Hardware > *From the Editor: Civil Disobedience and Linux > *Letters to the Editor > *Q&A with Mango Parfait > *TUX Explains: Inkscape: the Elements of Design, Part II > *TUX Explains: Lightweight Desktops: Xfce > *TUX Explains: BasKet Tutorial > *TUX Explains: Wireless Networking with ndiswrapper > *TUX Explains: Give Multiple Distros the Boot > *Review: Evermore Integrated Office Kicks Keister > *Review: Gadget Guy - Microsoft Natural Ergonomic Keyboard 4000 and the > Logitech MX 3000 Laser > *Review: Capsul Reviews - Evince, NVU, and Novell Evolution > > Once you download and open your magazine, the PDF WILL AUTOMATICALLY LAUNCH IN FULL SCREEN VIEW. You can reduce the size of the PDF to window view mode at any time by simply pressing 'esc'. > > For easier navigation of the magazine you may wish to turn on Bookmarks. You may do so by pressing 'F5' or using the menu across the top of the Adobe Acrobat Reader window and selecting 'Window' > 'Bookmarks'. > > Sincerely, > > > Carlie Fairchild > info@...851... > > TUX magazine > www.tuxmagazine.com > > > > NOTE: If you would like to be removed from this mailing, you may do so by simply changing your subscription delivery method or completely deleting your subscription. Please visit https://www.ssc.com/tx/subs/DigitalSub.php , enter your e-mail address, and select "Change my subscription" or "Delete my subscription" depending on your desire. -- Jon Phillips San Francisco, CA USA PH 510.499.0894 jon@...235... http://www.rejon.org MSN, AIM, Yahoo Chat: kidproto Jabber Chat: rejon@...896... IRC: rejon@...897... Inkscape (http://inkscape.org) Open Clip Art Library (www.openclipart.org)

1 0

patch for typos
by Mason Thomas 01 Nov '05

01 Nov '05

Hi, I am looking through the inkscape codebase trying to understand how things work, and I thought it would be good to do some "janitorial" work. Below are patches for the files in the src/application directory that mainly clean up some very minor typos. In addition, I have changed the vim modelines to have filetype of "cpp" rather than "c++" because the default install of vim uses cpp. If there is a standard inkscape policy to use "c++" instead, I can remove this. If there is not such a policy, then really all the cpp files should have a vim modeline using the cpp filetype. I could also submit a diff for this. I have also stripped a declaration for the Inkscape::XML namespace that does not appear to be used in application.cpp, but I am less sure about this. Thanks for your consideration, -Mason Thomas Index: application.cpp =================================================================== RCS file: /cvsroot/inkscape/inkscape/src/application/application.cpp,v retrieving revision 1.9 diff -u -p -r1.9 application.cpp --- application.cpp 9 May 2005 04:44:55 -0000 1.9 +++ application.cpp 1 Nov 2005 06:17:27 -0000 @@ -10,7 +10,7 @@ */ #ifdef HAVE_CONFIG_H -# include <config.h> +#include <config.h> #endif #include <gtkmm/main.h> @@ -26,12 +26,6 @@ int sp_main_console(int argc, char const namespace Inkscape { namespace NSApplication { -namespace Inkscape { -namespace XML { -class Document; -} -} - class GSList; Application::Application(int argc, char **argv, bool use_gui, bool new_gui) @@ -169,4 +163,4 @@ Application::exit() fill-column:75 End: */ -// vim: filetype=c++:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : +// vim: filetype=cpp:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : Index: application.h =================================================================== RCS file: /cvsroot/inkscape/inkscape/src/application/application.h,v retrieving revision 1.4 diff -u -p -r1.4 application.h --- application.h 9 May 2005 04:44:55 -0000 1.4 +++ application.h 1 Nov 2005 06:17:38 -0000 @@ -59,7 +59,7 @@ protected: } // namespace NSApplication } // namespace Inkscape -#endif // INKSCAPE_APPLICATION_EDITOR_H +#endif // INKSCAPE_APPLICATION_APPLICATION_H /* Local Variables: @@ -70,4 +70,4 @@ protected: fill-column:99 End: */ -// vim: filetype=c++:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : +// vim: filetype=cpp:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : Index: editor.cpp =================================================================== RCS file: /cvsroot/inkscape/inkscape/src/application/editor.cpp,v retrieving revision 1.7 diff -u -p -r1.7 editor.cpp --- editor.cpp 9 May 2005 04:44:55 -0000 1.7 +++ editor.cpp 1 Nov 2005 06:17:50 -0000 @@ -13,7 +13,7 @@ */ #ifdef HAVE_CONFIG_H -# include <config.h> +#include <config.h> #endif /* @@ -207,4 +207,4 @@ Editor::exit() fill-column:99 End: */ -// vim: filetype=c++:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : +// vim: filetype=cpp:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : Index: editor.h =================================================================== RCS file: /cvsroot/inkscape/inkscape/src/application/editor.h,v retrieving revision 1.7 diff -u -p -r1.7 editor.h --- editor.h 9 May 2005 04:44:55 -0000 1.7 +++ editor.h 1 Nov 2005 06:18:00 -0000 @@ -95,4 +95,4 @@ protected: fill-column:99 End: */ -// vim: filetype=c++:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : +// vim: filetype=cpp:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : Index: app-prototype.cpp =================================================================== RCS file: /cvsroot/inkscape/inkscape/src/application/app-prototype.cpp,v retrieving revision 1.1 diff -u -p -r1.1 app-prototype.cpp --- app-prototype.cpp 5 Mar 2005 20:51:51 -0000 1.1 +++ app-prototype.cpp 1 Nov 2005 06:16:57 -0000 @@ -39,4 +39,4 @@ AppPrototype::~AppPrototype() fill-column:75 End: */ -// vim: filetype=c++:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : +// vim: filetype=cpp:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : Index: app-prototype.h =================================================================== RCS file: /cvsroot/inkscape/inkscape/src/application/app-prototype.h,v retrieving revision 1.3 diff -u -p -r1.3 app-prototype.h --- app-prototype.h 5 Mar 2005 20:51:51 -0000 1.3 +++ app-prototype.h 1 Nov 2005 06:17:07 -0000 @@ -38,7 +38,7 @@ protected: } // namespace NSApplication } // namespace Inkscape -#endif // INKSCAPE_APPLICATION_EDITOR_H +#endif // INKSCAPE_APPLICATION_APP_PROTOTYPE_H /* Local Variables: @@ -49,4 +49,4 @@ protected: fill-column:75 End: */ -// vim: filetype=c++:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 : +// vim: filetype=cpp:expandtab:shiftwidth=4:tabstop=8:softtabstop=4 :

2 1

Re: [Inkscape-user] knotes tool
by Aaron and Sarah Spike 01 Nov '05

01 Nov '05

bulia byak wrote: > On 11/1/05, Hibbs, Phil <phil.hibbs@...1056...> wrote: >>I'm guessing that you mean "nodes tool". Do you mean move a node to a >>different place on the line without affecting the shape of the line? I don't >>think this is directly possible. It may not be possible, after all, to >>represent the same shaped curve with nodes in different places. You could >>add a new node (select two nodes, press Ins, and a new node appears half way >>in between them), but when you delete one of the original nodes, the shape >>of the line changes dramatically. > > There was a proposal to delete nodes without changing shape as much as > possible, and Aaron started looking into it (I think). Hopefully this > will be implemented soon. I haven't started looking at this yet. Since I don't know or understand the complex math is trying to guess at the best approximation, I had planned to sample the two curve segments adjacent to the node in a configureable number of places and send that list of points to the bezier fitting functions in bezier-utils.cpp to have it find the best fitting single segment approximation (I think that it has the ability to do this with end tangent constraints). Does this sound like a reasonable idea to the people in the know? Aaron Spike

3 2

Re: [Inkscape-user] drag, drop and copy-paste
by unknown＠example.com 01 Nov '05

01 Nov '05

Quoting Bryce Harrington <bryce@...961...>: > There isn't a mechanism like that currently. I suspect that the > DOM work Ishmal is heading up would be the logical place to put > this capability. ...wha? What we'd need, first and foremost, to implement this would be a bit of portable IPC code that the inkscape executable could use to check if an existing session was running, and if so instruct that to open the document. I don't see how that is related to DOM? At the simplest, it would mean opening an IPC port (Unix domain socket on Unix/OSX; named pipe on Win32) from main.cpp and using some dirt simple protocol to discover and communicate with an existing Inkscape instance. Besides Mozilla/Firefox, xmms is another example of an application that does this. -mental

2 1

Useful info for potential Mac users
by William Swanson 31 Oct '05

31 Oct '05

Hi, I have a few friends who use Macs, and the X11 requirement seems to be a real tripping point for them when installing Inkscape. One friend figured it out and wrote up the following instructions: "If you are running later than OS X Tiger 10.4 you will need to download the X11 software from Apple at http://www.apple.com/support/downloads/x11formacosx.html. Or, if you already have OS X Tiger, you will need to insert your OS Disc #1 and run a Spotlight search in the CD for "X11User.pkg". Once you find and install that file, start another search for "X11SDK.pkg" and install that. Once you have both of those installed (with the OS Disc inside your drive), take out the disc, run the inkscape.dmg install file, and X11 will pop up. It might take a minute or two the first time you try, but it will load." I am not a Mac user, so I can't evaluate these directions myself. Perhaps someone using a Mac could verify them and put them on the website where folks downloading the .dmg will see it. Making this information more readily to Mac users should reduce the "I can't get Inkscape to work" troubles they seem to have. -s_tec

2 2

patch: crash on layer delete
by Ralf Stephan 31 Oct '05

31 Oct '05

Hello, regarding the recent 'crash on layer delete' I propose a patch that at least handles the simple case of that bug. As this is not my field, I'd ask you to review it. The idea is to setCurrentLayer() after the layer is deleted, and not before. setCurrentLayer() emits the layerChanged signal which is listened to by the layer selector widget. ralf --- verbs.cpp~ 2005-10-31 10:03:13.000000000 +0100 +++ verbs.cpp 2005-10-31 12:18:15.000000000 +0100 @@ -1123,11 +1123,11 @@ if (!survivor) { survivor = Inkscape::previous_layer(dt->currentRoot(), old_layer); } + old_layer->deleteObject(); + sp_object_unref(old_layer, NULL); if (survivor) { dt->setCurrentLayer(survivor); } - old_layer->deleteObject(); - sp_object_unref(old_layer, NULL); sp_document_done(SP_DT_DOCUMENT(dt));

2 1

Re: [Clipart] clipartbrowser 0.41
by Greg Steffensen 31 Oct '05

31 Oct '05

Ok, the clipartbrowser cvs module is now synched up again with the latest tarballs, and the cannonical download location for releases is now http://www.python.org/pypi/clipartbrowser (it used to be on Berlios). If you download a release (they work better than ever :), install using "python setup.py install" (assuming you have the dependencies met). The "easy_install" method mentioned earlier works too. Greg On 9/20/05, Greg Steffensen <greg.steffensen@...400...> wrote: > > I didn't explain the technical situtation with the install method very > well. Basically, if I write a file "setup.py" that defines certain > information, users should be able to execute "python setup.py install" to > install the program correctly, and I should be able to execute commands > "python setup.py bdist_win" to create actual win32 EXE files containing > pretty automated installer GUIs. In addition, users will be able to install > the way I described in the release email as well. In general, setup.pyuses the "setuptools" which are the successor to the "distutils", which is > the distribution/installation tools included with python. I'm still not > certain whether I should use the setuptools or the older distutils, and am > figuring stuff like that out, but they're both supposed to be the > python-friendly replacement for Makefiles, and I'm trying to reorganize the > code to do stuff the "correct" way. > > Greg > > On 9/20/05, Greg Steffensen <greg.steffensen@...400...> wrote: > > > > Hey, yeah, this is kinda what I was referring when I said that the > > packaging isn't as polished as it needs to be. For what its worth, most of > > the changes (bug fixes, performance improvements) actually are committed to > > CVS; I just didn't commit commit the change in the install method simply > > because I was having trouble figuring out how to get files like COPYING, > > NEWS, etc. included using that method, and I didn't want to put a totally > > messed up version into CVS. Basically, I actually really released more on a > > whim, not because I'd worked everything out, but because I'd gone too long > > without releasing code, wanted people to know that work was ongoing. So, at > > a minimum, I should have indicated that this was definitely a development > > release. > > > > So, solutions... in terms of where formal releases (formal tarballs) > > should go, I actually think the python package index is definitely the > > correct place... its now the "official" place where the python folk > > reccomend that python projects be listed, and it will offer a number of > > technical advantages, including publication of new releases, and > > installation automation. I'm very happy keeping CVS at Inkscape though (not > > that PyPI offers CVS anyway), and treating the code as a subproject of > > Inkscape. But as long as it offers the ability to be installed standalone as > > well, I'd like to make standalone tarballs available from PyPI. In general, > > I'm learning more about python, and am trying to make my practices for > > installation, etc. match accepted practice. > > > > I'll try to get CVS synched up with the current state of the project > > very soon; I'm still having some trouble with the python installation tools, > > and have sent an email to their mailing list for advice, but haven't heard > > back yet. Once I know how to get the documentation files included, and where > > to put the main install file (setup.py), I'll get that committed and CVS > > will contain the official version of the code gain. Again, I would have > > waited until this was done to release, but just felt bad about having gone > > too long without releasing already, and was overeager to get something out. > > > > Anyway, does this cover the stuff you were concerned about? If not, let > > me know. Also, you may recall that someone posted a link to a mockup for a > > very similar project that they'd found, and I replied that this was "very > > depressing" :). I used that mockup to develop version 0.4, and emailed > > the designer (as the community suggested); he's finally written me back, and > > said he's interested in contributing, which rocks. Later, > > > > Greg > > > > > > On 9/19/05, Jon Phillips <jon@...235...> wrote: > > > > > > <offlist /> > > > > > > On Mon, 2005-09-19 at 05:20 -0400, Greg Steffensen wrote: > > > > I'm releasing another version of the clip art browser. Lots of bug > > > > fixes, some performance improvements, code cleanups, and a new > > > > installation procedure (yes, yet another). > > > > > > > > Installation is now 3 steps, and hopefully easier than ever: > > > > > > > > 1) Satisfy the dependencies of Python 2.4 and PyGTK 2.6. > > > > > > > > 2) Download and run the following script, which installs the python > > > > setuptools: > > > > > > > > http://peak.telecommunity.com/dist/ez_setup.py > > > > > > > > 3) Run "easy_install clipartbrowser" > > > > > > > > As you can see, I've switched the installation system from Makefiles > > > > > > > to the python setuptools. The setuptools are still under development > > > > (they're apparently going to be included in python 2.5), and I'm > > > still > > > > very much learning how to use them, so the packaging isn't as > > > polished > > > > as it needs to be, but this makes installation a breeze. Eventually, > > > > it should allow arbitrary python dependencies to be intelligently > > > > installed as well using the same process. > > > > > > > > I'm still working on getting this integrated back into the Inkscape > > > > effects menu, that's next on the list. As always, feedback greatly > > > > appreciated. > > > > > > > Greg, > > > > > > I thought we were going to do the next release from Inkscape CVS? What > > > you have done is a non-standard release of the project now that we > > > consolidated the code into Inkscape. > > > > > > Also, you have now used a non-standard approach to packaging which > > > then > > > again breaks what users and developers are use to. > > > > > > The major thing though is that we were going to do a solid release > > > which > > > means you need to involve the people who would contribute to this in > > > the > > > release to help smooth out the bugs. > > > > > > Instead, now you have released from another location thus confusing > > > users and developers more. The problem with this is that it is not > > > pro-community. > > > > > > Anyhow, I'm curious what you think and also want to get these things > > > on > > > track with the community. > > > > > > It is so great that you are rocking these changes and I'm so proud of > > > what you are doing so I don't want to dismay you, but really I think > > > the > > > next release has to be really on track with the community and we > > > should > > > coordinate it, push it out through the sourceforge system we have in > > > place, and push the press release globally. > > > > > > Without these procedures, honestly, it is not very likely that others > > > will help on development nor use your work. > > > > > > So, lets talk some more and sort these things out. > > > > > > Jon > > > > > > > > > -- > > > Jon Phillips > > > > > > San Francisco, CA > > > USA PH 510.499.0894 > > > jon@...235... > > > http://www.rejon.org > > > > > > MSN, AIM, Yahoo Chat: kidproto > > > Jabber Chat: rejon@...896... > > > IRC: rejon@...897... > > > > > > Inkscape (http://inkscape.org) > > > Open Clip Art Library ( www.openclipart.org<http://www.openclipart.org> > > > ) > > > > > > > > >

5 8

a couple of "effects"
by unknown＠example.com 30 Oct '05

30 Oct '05

Yesterday at Bryce's prompting I wrote a little effect that makes the selected objects a <marker /> in the <defs /> of the current document. Inkscape doesn't really seem to deal well with this but there is some code there to work with if anyone has ideas on how it could be used. I think Bryce made some modifications to his copy as well. Because there is a lack of interactivity you must position the connection point of the marker at (0,0). And there are likely a few other nuances I haven't thought of yet. http://www.ekips.org/comp/inkscape/inx/makemarker.tar.gz I also wrote a python script that embeds images in SVG because I didn't feel comfortable editing the perl script. It functions as an effect and can be called from the effects menu. If objects are selected it will only replace the images in the selection, otherwise it should replace the images in the entire document (although in retrospect I didn't test that, oops). Hopefully this effect will be obsolete soon and we can have "embed all" in a menu and "embed" in the images' context menu. http://www.ekips.org/comp/inkscape/inx/embedimage.tar.gz Aaron Spike

4 3

Additional info regarding Inkscape CVS compile error
by Steven P. Ulrick 29 Oct '05

29 Oct '05

Hello, Everyone For the past few days, I had been getting error messages like this when running "make" on Inkscape from CVS: file=./`echo it | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -c -o $file it.po it.po:1989: message catalog has plural form translations... it.po:10: ...but header entry lacks a "plural=EXPRESSION" attribute it.po:1989: message catalog has plural form translations... it.po:10: ...but header entry lacks a "nplurals=INTEGER" attribute make[2]: *** [it.gmo] Error 1 make[2]: Leaving directory `/home/steve/CVS/Assorted-CVS-Modules/inkscape/po' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/steve/CVS/Assorted-CVS-Modules/inkscape' make: *** [all] Error 2 For a while, I tried going back to old revisions of the *.po file that "make" seemed to choke on. Sometimes I would get the same error, but on a different *.po file. In each different error message, the numbers next to the name of the *.po file that was compiling when "make" crashed was different. Here is a new error message. Now "make" is choking on sr.po. I haven't seen it bomb on that one before: Making all in po make[2]: Entering directory `/home/steve/CVS/Assorted-CVS-Modules/inkscape/po' file=./`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -c -o $file sr.po sr.po:3224: format specifications in 'msgid' and 'msgstr' for argument 1 are not the same sr.po:4774: format specifications in 'msgid' and 'msgstr[0]' for argument 1 are not the same /usr/bin/msgfmt: found 2 fatal errors make[2]: *** [sr.gmo] Error 1 make[2]: Leaving directory `/home/steve/CVS/Assorted-CVS-Modules/inkscape/po' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/steve/CVS/Assorted-CVS-Modules/inkscape' make: *** [all] Error 2 Further, I noticed the following in the output for "configure": Running aclocal-1.7 ... Running autoheader ... Running libtoolize --copy --force ... Running automake-1.7 --add-missing ... Running autoconf ... Running glib-gettextize --copy --force ... Copying file mkinstalldirs Copying file po/Makefile.in.in Running intltoolize --copy --force --automake ... patching file po/Makefile.in.in Hunk #4 FAILED at 95. Hunk #5 succeeded at 194 (offset 15 lines). 1 out of 6 hunks FAILED -- saving rejects to file po/Makefile.in.in.rej This is the error that I posted that I referred to in the response to Erik's "What is happening?" message. I have reported this to the list, but no one apparently has seen it yet, or has knowledge about the possible cause. So that you can get all of the information that I have sent to the list about this problem, here is a link to my original thread in the archives: http://sourceforge.net/mailarchive/forum.php?thread_id=8808340&forum_id=360… As always, if you need any more information, let me know. Oh yeah, I said it elsewhere, but I am attempting to compile this on Fedora Core 3. Steven P. Ulrick

2 3