- Inkscape Devel - Inkscape Mailman

Crash
by Diederik van Lierop 07 Nov '07

07 Nov '07

Using the latest rev. 16441, I get a very reproducible crash immediately after dragging anything. Is this related to any of the current work? See the trace below obtained using Eclipse on Linux. Regards, Diederik New_configuration [C/C++ Local Application] gdb Debugger (11/7/07 9:36 PM) (Suspended) Thread [1] (Suspended: Signal 'SIGSEGV' received. Description: Segmentation fault.) 43 Inkscape::URIReference::getObject() /home/diedenrezi/eclipse_workspace/inkscape/src/uri-references.h:75 0x000000000046474f 42 SPPaintServerReference::getObject() /home/diedenrezi/eclipse_workspace/inkscape/src/sp-paint-server.h:68 0x0000000000464770 41 SPIPaint::isPaintserver() /home/diedenrezi/eclipse_workspace/inkscape/src/style.h:169 0x000000000046479d 40 sp_item_adjust_gradient() /home/diedenrezi/eclipse_workspace/inkscape/src/sp-item.cpp:1014 0x00000000004c2b5f 39 sp_item_adjust_paint_recursive() /home/diedenrezi/eclipse_workspace/inkscape/src/sp-item.cpp:1150 0x00000000004c49cb 38 sp_item_write_transform() /home/diedenrezi/eclipse_workspace/inkscape/src/sp-item.cpp:1214 0x00000000004c4fad 37 sp_selection_apply_affine() /home/diedenrezi/eclipse_workspace/inkscape/src/selection-chemistry.cpp:1571 0x0000000000476cf2 36 Inkscape::SelTrans::ungrab() /home/diedenrezi/eclipse_workspace/inkscape/src/seltrans.cpp:403 0x00000000005ed2fe 35 sp_select_context_root_handler() /home/diedenrezi/eclipse_workspace/inkscape/src/select-context.cpp:549 0x00000000005e5b5d 34 sp_event_context_root_handler() /home/diedenrezi/eclipse_workspace/inkscape/src/event-context.cpp:836 0x0000000000592655 33 sp_event_context_item_handler() /home/diedenrezi/eclipse_workspace/inkscape/src/event-context.cpp:854 0x00000000005926b9 32 _arena_handler() /home/diedenrezi/eclipse_workspace/inkscape/src/desktop.cpp:1381 0x000000000057ac2d 31 sp_marshal_INT__POINTER_POINTER() /home/diedenrezi/eclipse_workspace/inkscape/src/helper/sp-marshal.cpp:475 0x000000000084ce87 30 g_closure_invoke() 0x000000379a40af39 29 Gtk::Widget::hide_all() 0x000000379a41a838 28 g_signal_emit_valist() 0x000000379a41ba4d 27 gtk_signal_emit() 0x0000003339d8dc6c 26 sp_canvas_arena_send_event() /home/diedenrezi/eclipse_workspace/inkscape/src/display/canvas-arena.cpp:447 0x0000000000808a3a 25 sp_canvas_arena_event() /home/diedenrezi/eclipse_workspace/inkscape/src/display/canvas-arena.cpp:434 0x0000000000808ed5 24 sp_marshal_BOOLEAN__POINTER() /home/diedenrezi/eclipse_workspace/inkscape/src/helper/sp-marshal.cpp:352 0x000000000084d192 23 g_closure_invoke() 0x000000379a40af39 22 Gtk::Widget::hide_all() 0x000000379a41ae48 21 g_signal_emit_valist() 0x000000379a41ba4d 20 gtk_signal_emit() 0x0000003339d8dc6c 19 emit_event() /home/diedenrezi/eclipse_workspace/inkscape/src/display/sp-canvas.cpp:1303 0x0000000000825f1a 18 sp_canvas_button() /home/diedenrezi/eclipse_workspace/inkscape/src/display/sp-canvas.cpp:1507 0x00000000008281e0 17 Gtk::Widget::hide_all() 0x0000003339d32ded 16 g_closure_invoke() 0x000000379a40af39 15 Gtk::Widget::hide_all() 0x000000379a41ae48 14 g_signal_emit_valist() 0x000000379a41ba4d 13 g_signal_emit() 0x000000379a41be53 12 Gtk::Widget::hide_all() 0x0000003339e30ede 11 gtk_propagate_event() 0x0000003339d2c3dd 10 gtk_main_do_event() 0x0000003339d2d3f1 9 snooper() /home/diedenrezi/eclipse_workspace/inkscape/src/main.cpp:668 0x0000000000446cda 8 Gtk::Widget::hide_all() 0x000000333a646b6c 7 g_main_context_dispatch() 0x0000003799c2d224 6 Gtk::Widget::hide_all() 0x0000003799c3005d 5 g_main_loop_run() 0x0000003799c3036a 4 gtk_main() 0x0000003339d2d783 3 sp_main_gui() /home/diedenrezi/eclipse_workspace/inkscape/src/main.cpp:710 0x0000000000447725 2 Inkscape::NSApplication::Application::run() /home/diedenrezi/eclipse_workspace/inkscape/src/application/application.cpp:117 0x0000000000612fc6 1 main() /home/diedenrezi/eclipse_workspace/inkscape/src/main.cpp:525 0x0000000000447f4b gdb (11/7/07 9:36 PM) /home/diedenrezi/eclipse_workspace/inkscape/src/inkscape (11/7/07 9:36 PM)

3 2

Bug trackers
by Bryce Harrington 06 Nov '07

06 Nov '07

We've been wanting to switch from the extraordinarily painful SF bug tracker. Initially I thought we should host the service, but we don't have people with the expertise and time to do it, esp. given the DOS attack Inkscape suffered last week. Ted, Kees, and I are investigating Launchpad, and think it will give all-around improvement with no regressions. Mental and ACSpike also thought Launchpad sounded like a good option. Bulia and other heavy bug tracker users - can you give a thumbs up that this would be worth trying? Launchpad has the usual advanced bug tracking capabilities we've been badly missing, like proper bug duping, auto dupe detection, email interface, milestoning, tagging, SVN/CVS/etc.-integration, and so on. It also allows linking to upstream and downstream bug trackers, so we will be able to hook Inkscape bugs to corresponding Gtk, Cairo, etc. bugs (this is an extremely handy feature). We're here local with the Launchpad engineers, so it would be a good opportunity for us to have them run their import scripts and set up a public demo site for us. They'll also provide the exported data files, in case we would choose to go with something different. Bryce

3 4

Linux svn 16434 build failing
by Thomas Worthington 06 Nov '07

06 Nov '07

I'm getting this error when running make: make[2]: *** No rule to make target `extension/internal/libwpg/Makefile_insert', needed by `Makefile.in'. Stop. Any ideas? TW

2 1

Re: [Inkscape-devel] bug? 'embed all images' can't find png files in local directory
by Tom Davidson 06 Nov '07

06 Nov '07

This is fixed in the latest SVN (16429), so I marked the bug closed. My test file now fails for a related, but slightly different reason :). I opened a new bug for that (1826197) and posted a patch in the bug tracker... Both of these bugs were triggered by the use of relative paths in an SVG file without a backup sodipodi:absref tag to indicate where the linked image file can be found. I'm not sure if you all keep a suite of test files, but if so this one seems like it could be a useful addition... Thanks! Tom On 11/4/07, Tom Davidson <tjd@...1007...> wrote: > OK, I think I understand what's causing the bug. When I run > embedimage.py on the command-line against the original test file, it > works fine. But it doesn't work against the temporary file that > inkscape is writing to /tmp and handing off to the extension. > > Here is a diff of the two files: > > $ diff /tmp/ink_ext_GOTW0T ~/tmpsvg/embedtest_simple.svg > 19,20c19,20 > < sodipodi:docname="ink_ext_GOTW0T" > < sodipodi:docbase="/tmp" > --- > > sodipodi:docname="embedtest_simple.svg" > > sodipodi:docbase="/home/tjd/tmpsvg" > 51,52c51 > < <defs > < id="defs5" /> > --- > > <defs /> > > As you can see the 'docbase' directory is being changed to /tmp, but > the links out to images are still 'local'. Since the image files are > not also copied over to the /tmp directory, these links are not valid. > > So I guess the question is whether the links in my svg file are > buggy/underdefined (the svg is being generated by a matlab script > called plot2svg), and inkscape is letting me get away with this when > displaying the images, or whether this is a bug that needs fixing. > > I will post this additional info to the bug report and maybe > inkscape-devel as well... > > Cheers, Tom > > 11/4/07, Tom Davidson <tjd@...1007...> wrote: > > Hi Aaron, > > > > I have run into some odd behavior with the embedimages.py script. Inkscape can find and display the linked images, but when I call the 'embed all images' extension, I get an error that the files can't be found. I have filed a bug report (1824893) with a test case and the error messages on the tracker at http://sourceforge.net/tracker/index.php?func=detail&aid=1824893&group_id=9… ). I will also poke around and see if I can't figure out how to debug it myself, but I'm not a Python person... > > Thanks very much for your work on Inkscape! > > -Tom > > >

1 0

inkscape + ocal features into the release notes
by Jon Phillips 05 Nov '07

05 Nov '07

Bruno, could you please add the features you made as part of GSoC, to the release notes for the upcoming release...we are going to need to do some testing too: http://wiki.inkscape.org/wiki/index.php/ReleaseNotes046 Cheers! 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... Please note: the contents of this email are not intended to be legal advice nor should they be relied upon as or represented to be legal advice. Jon Phillips does not represent any organization through this email address.

2 2

Stuck on Clone
by Martin Owens 05 Nov '07

05 Nov '07

Hi all, Trying to create the most simple part of this animation extensions; the clone frame part. I'm stuck because the xml python lib we're using (at least as of 0.45) doesn't implement the w3c DOM, instead it's patch hodge podge of none standard methods with buggy getElementById, no insertAfter method and buggy cloneNode when deep is switched on. Error message: xml.dom.HierarchyRequestErr: Node manipulation results in invalid parent/child relationship. The basic idea was to create a clone of the currently selected layer, add it after the current one and change a property in each child element to link it back to the original element in the original layer. Then another script would come along and combine each of these layers into an animation; forcing elements that disappear or appear new to fade, elements that are linked to be combined into an animation for each frame and any other layers to be left alone (for background or foreground layers) this would support paths, object transformations and style/attribute changes over time. Other extensions that could then be written after these first two: Animation > Tween Frames - Creates a step between the current layer and the next layer for all linked elements Animation > Link Selected - Creates an animation link between the two selected elements kees said if the first two can be implemented then he's see about writing in the UI handler which makes the current layer visible only (with the next and previous semi transparent at your option) with a slide bar to select the layer/frame. I'll resume when I think I can begin sanely writing the code, otherwise I'll hand the svg off to perl and write the extensions using that (which wouldn't be ideal to be honest) Best Regards, Martin Owens

2 1

Re: [Inkscape-devel] PR Planning (was Re: Inkscape overcomes Xara in Google Trends)
by ryan lerch 05 Nov '07

05 Nov '07

On 11/5/07, Jon Phillips <jon@...235...> wrote: > > Totally, I wonder if we can do a push to get some screencasts and > tutorials of the new features prior as well...that would rock...ppl. > just want to see screenshots, right? > > What would be needed? > We have already started some preliminary work on some new tutorials, http://wiki.inkscape.org/wiki/index.php/TutorialUpdates-0.46 some of which cover some of the new features, this can easily be expanded ... cheers, ryanlerch

1 0

PR Planning (was Re: Inkscape overcomes Xara in Google Trends)
by Bryce Harrington 05 Nov '07

05 Nov '07

On Tue, Oct 09, 2007 at 10:50:03AM +1000, Ryan Lerch wrote: > Is it worth fleshing out a PR plan for promotion of the upcoming release? It > will be a huge release (feature wise) and I reckon people will want to know > about all our cool new features... Yes, this sounds like a very good idea. Ryan, would you and Jon and prokoudine arrange to put some thought into this sometime within the next week or two, and post what you come up with to this list for review? Thanks, Bryce

4 5

[ted@...11...: [Fwd: [Clipart] Fwd: Announcement: Wikimedia Foundation Greenspun illustration project]]
by Bryce Harrington 04 Nov '07

04 Nov '07

----- Forwarded message from Ted Gould <ted@...11...> ----- Date: Sun, 04 Nov 2007 14:35:26 -0800 From: Ted Gould <ted@...11...> To: Bryce Harrington <bryce@...961...> Subject: [Fwd: [Clipart] Fwd: Announcement: Wikimedia Foundation Greenspun illustration project] -------- Forwarded Message -------- From: Brianna Laugher <brianna.laugher@...400...> To: clipart@...626... Subject: [Clipart] Fwd: Announcement: Wikimedia Foundation Greenspun illustration project Date: Mon, 5 Nov 2007 00:32:15 +1100 Hi OpenClipArters, Forwarding along an announcement from the Wikimedia Foundation that it is facilitating a project to pay for the creation of illustrations. I (Brianna Laugher) am coordinating the project on the community side. I am thinking and hoping there may be a few cliparters who are interested in putting their SVG skills to work. The central wiki page for the project will be http://meta.wikimedia.org/wiki/Philip_Greenspun_illustration_project . The project is still in the gathering-requests stage and I will send out an announcement when we expect to open requests up for people to fulfil. Please let me know if anything about it is not clear. thanks, Brianna ---------- Forwarded message ---------- From: Cary Bass <cbass@...1827...> Date: 3 Nov 2007 05:32 Subject: [Foundation-l] [ANNOUNCEMENT] Greenspan illustration project To: Wikimedia Foundation Mailing List <foundation-l@...1828...>, Wikimedia Commons Discussion List <commons-l@...1828...> The Greenspan Illustration Project What is it? The Wikimedia Foundation has received a donation from Philip Greenspun for the purpose of creating and improving illustrations on Wikimedia. The Board has decided to accept his donation of $US20,000 for this special purpose. This is the first time the Foundation has been directly involved in funded content creation, although the German chapter's experience in winning a government grant to write articles on sustainable development has helped pave the way. The Foundation wants a "hands-off" minimal administration role with the bulk of the work of organizing the project and creating the content to be completed by members of our community. Since this is the first time we've done this, we're not sure how it will go. This is a bit experimental and we ask for your patience and enthusiasm to help make it a success. Brianna Laugher (<http://commons.wikimedia.org/wiki/User:Pfctdayelise>) will be coordinating the project, with my help as the Foundation's Volunteer Coordinator. How will it run? Since Philip's kind donation is a lot of money and we're planning to pay around US$40 per illustration (with some lower and higher amounts, see details to follow), we want to progress the project in stages. Starting out with a small number of 50 requested illustrations, we'll look at our results and modify and improve it for successive stages. The project will flow along as follows: * Create list of requested illustrations. * Open illustration requests on issue tracking software * Users will self-assign requests, signaling his or her intent to create that illustration. * On creation and approval, the user is paid the amount as set in the original request. Things to note: * The list of requests will be approved by Brianna, in order that balance exists among "things any decent reference work needs"; "things the Wikimedia community requests"; and "things we nearly have, or have poor versions of". * Approval: a review group will be formed in order to provide assessment of submitted images. The main checks will be 1) editor's original work and acceptable license, 2) correct rendering on MediaWiki and 3) how well the image depicts the requested item. No image will be accepted that do not pass all three of these checks. * Other checks will be recommended (e.g. language-neutral version). * The payment system is not yet finalized. How you can help If you are interested in suggesting illustrations to be created, you don't have long to wait: soon there will be some pages on Meta where you can get involved. We will write to foundation-l when the pages are ready for your input. If you are interested in being part of the review group, please email Brianna as follows: brianna.laugher AT gmail DOT com The benefits This project can have two good outcomes. One, we get illustrations we wouldn't otherwise have, or wouldn't otherwise have had so quickly. Another benefit is that we can use this project as a way to encourage and launch new people into the "illustrator community". Creating high-quality SVGs is not a skill a lot of people have immediately, but may be developed fairly quickly. While many people might be vaguely interested in it but no more, a monetary incentive might be enough to push them to act, and learn, and create. Some of the image requests will be for smaller amounts (US$15) for relatively simpler illustrations???these will be specifically targeted to newcomers to encourage them to get involved. At the end of this project we might have $20,000 worth of illustrations, but the value of the content creating community will potentially be a lot higher. We expect a side benefit to this project will be the creation/finding and maintenance of good documentation for specific tasks using tools like Inkscape. More details See the project specifications at: http://upload.wikimedia.org/wikipedia/foundation/5/51/WMF_Greenspun_Illustr… -- Cary Bass Volunteer Coordinator Your continued donations keep Wikipedia running! Support the Wikimedia Foundation today: http://donate.wikimedia.org Wikimedia Foundation, Inc. Phone: 727.231.0101 Fax: 727.258.0207 E-Mail: cbass@...1827... _______________________________________________ foundation-l mailing list foundation-l@...1828... Unsubscribe: http://lists.wikimedia.org/mailman/listinfo/foundation-l ----- End forwarded message -----

1 0

Text tool crash.
by unknown＠example.com 04 Nov '07

04 Nov '07

I just fixed a crash bug with the text tool: https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1645874&gro up_id=93438 The problem is that an empty flowtext thing is put in XML, and it is deleted on deselection when nothing is inputted. This crashes the XML editor, and also duplication of the thing. I disabled the automatic deletion on deselection, and now it no longer crashes. For who starts working on the texttool: I think it is best *not* to add things to XML when nothing has been actually typed yet. Upon typing the first character, *then* put it in XML. This removes the need for the automatic deletion and fixes the problem without cluttering the XML with empty texts. Off to another crash bug... Johan

1 0