- Inkscape Devel - Inkscape Mailman

Report for 2004-07-03 18:00 GMT-0500
by unknown＠example.com 05 Jul '04

05 Jul '04

Hi. I have some bad news. Unfortunately, the last build attempt at compiling Inkscape CVS was very unsuccesful. I'm sorry, I really tried hard. Really. Here is the LOG file, and I hope that helps.

5 5

General and Specific Meta-Data
by Jon Phillips 04 Jul '04

04 Jul '04

Right now in Inkscape and OCAL graphics files meta-data is file wide, yet how can we maintain meta-data for discrete objects and groups of objects? How can we have both the General/Abstract meta-data and then have specific meta-data for discrete items and groups? I wonder how we can have it so that when an object or collection of objects is copied and pasted, imported and transformed, that its specific meta-data (beyond specified graphics attributes) can be copied along with itself (making a media object). In the future this will be vital for algorithmic composition of graphics. Thoughts? Jon -- Jon Phillips Graduate Researcher Visual Arts Department PO BOX 948667 LA JOLLA, CA 92037 USA cell.858.361.2811 jon@...235... http://www.rejon.org

4 4

L10n questions
by Arpad Biro 04 Jul '04

04 Jul '04

Hi, I have a few questions concerning new strings: #: src/dialogs/rdf.cpp:227 "Coverage" #: src/dialogs/rdf.cpp:228 "Extent or scope of this document." Do these mean "the things this document talks about"? #: src/dialogs/rdf.cpp:238 "URI to the License namespace definition." Is "License" the name of a namespace? #: src/interface.cpp:936 "Make Current Layer" Does this mean: "make it the current layer"? #: src/dialogs/rdf.cpp:225 "classication" Does this mean the same as "classification"? Arpad Biro __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail

3 2

Re: [Inkscape-devel] Clone command
by bulia byak 04 Jul '04

04 Jul '04

>Bulia...this is an awesome feature. I wish the keyboard shortcut was >easier to do with one hand. Most keys are already taken. Feel free to propose another shortcut. >Also, I think there should be another feature that should be added >called EXPAND, which allows for selected cloned objects to be made into >complete copies of the referenced image. Better "Unlink clone". Also a command to look up a clone's original. >Also, markers applied to the original do not apply to the clones. Yes. Please file a bug. _________________________________________________________________ http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

6 5

away for a while
by MenTaLguY 04 Jul '04

04 Jul '04

I'll be without phone or internet access for the next few days (hopefully not longer), so I probably won't be getting much Inkscape work done in that time. CVS isn't really very friendly for disconnected operation. In my absence, there are a few important things I wanted to make sure were nailed down before the 0.39 release: A. Clipping Paths Clipping paths are an extremely important feature for me personally, so I want to make sure they're in order before the release. 1. I think the clipping-paths-not-activating-on-load bug is related to a cut+paste mistake in sp_item_set -- if you compare the SP_ATTR_CLIP_PATH and SP_ATTR_MASK branches, one ->clip_ref has not been changed to ->mask_ref in the SP_ATTR_MASK branch. (hopefully that's right; this is from memory) Could someone please check, fix and commit that? 2. 'clip-path' specifications are currently only supported as XML attributes, not style= properties. Changing that now will require non-trival architectural work (I think), so just be aware of that when testing. 3. In case Bulia or anyone is interested, clipping paths currently require recursive updates. Not fatal, but if it bothers you you might want to have a look. B. Layers I kind of snuck in some layers stuff over the weekend. You can pick "enter group" from the context menu to start using a group as the current layer (i.e. the drawing tools will draw within it). "leave group" will "back out a level" (until you hit the root <svg> element again). I'd been hoping to get it a little more polished, but I probably won't have a chance before the release at this point... 1. The implementation is pretty crude and doesn't add any UI feedback; we should probably disable those menu entries for the final release 2. If you do decide to add feedback, I'd recommend adding a SigC++ signal to Inkscape::ObjectHierarchy that fires whenever the top or bottom object in the hierarchy changes. Also add a signal to SPDesktop that indicates when the current layer changes. The SPDesktop layer change should be driven by the signal belonging to SPDesktop::_layer_hierarchy (an Inkscape::ObjectHierarchy). SPDesktop would also end up needing to keep a SigC::Connection around to track its connection to the hierarchy signal -- so please remember to: a. explicitly call the constructor and destructors for any SPDesktop members of types in the SigC:: namespace b. disconnect the SigC::Connection before destroying it 3. The tools currently set the newly created item's transform by directly assigning to SPItem::transform. That's incredibly bad, and I had not intended to leave it in. It'd be nice if someone could make a public SPItem::setTransform() method (which would more or less just call the private sp_item_(mumble?)_set_transform() .. sorry, this is from memory) and use that instead. SPItem::transform should really be treated as read-only by outsiders. 4. "enter group" and "leave group" should really both go next to each other in the menu and in interface.cpp 5. There are also some issues of "transparency" (in the sense of event delivery) for layers currently, which is another reason I think we're probably best off shipping with the feature disabled. C. 0.40 release planning Also some entries I want to make sure we have on the 0.40 roadmap in the wiki: 1. add a dependency on libgc (the Boehm conservative collector), which will be required for the AST code 2. add a dependency on libcroco (which will be needed for the CSS portion of AST) 3. switch to sigc++ 2.0/newer gtkmm early in 0.40, before we start doing gtkmm-intensive stuff like the layers dialog etc. See y'all in a few days I hope... -mental

3 7

Perf improvement to IntLigne::Copy(FloatLigne)
by Bryce Harrington 04 Jul '04

04 Jul '04

I've checked in a patch to IntLigne::Copy(FloatLigne*) that improves performance on my box. Previously, it had been taking 0.10 sec (4.74%), but now has been reduced to 0.03 sec (1.47%). I don't think I made any algorithmic changes, and booleans seems to still be working right, but I'd appreciate it if someone could keep an eye on it in case a goof got introduced. Bryce Before: % cumulative self time seconds seconds name 11.85 0.25 0.25 Shape::SwapEdges(int, int) 7.11 0.40 0.15 Shape::ConvertToShape(Shape*, fill_typ, bool) 4.74 0.50 0.10 IntLigne::Copy(FloatLigne*) <---- 3.79 0.58 0.08 Shape::SwapPoints(int, int) 3.32 0.65 0.07 Shape::CmpToVert(NR::Point, NR::Point, bool, bool) ... After: % cumulative self time seconds seconds name 13.73 0.28 0.28 Shape::SwapEdges(int, int) 7.35 0.43 0.15 Shape::ConvertToShape(Shape*, fill_typ, bool) 5.39 0.54 0.11 Shape::SwapPoints(int, int) 3.43 0.61 0.07 FloatLigne::InsertBord(int, float, int) 3.43 0.68 0.07 FloatLigne::Flatten() 3.43 0.75 0.07 Shape::TesteIntersection(SweepTree*, SweepTree*, NR::Point&, double&, double&, bool) 2.94 0.81 0.06 Shape::AddEdge(int, int) 2.45 0.86 0.05 Shape::TesteAdjacency(Shape*, int, NR::Point, int, bool) 2.45 0.91 0.05 Shape::CheckAdjacencies(int, int, Shape*, int) 1.96 0.95 0.04 Shape::CheckEdges(int, int, Shape*, Shape*, bool_op) 1.96 0.99 0.04 Shape::SortEdges() 1.47 1.02 0.03 sp_repr_attr(SPRepr const*, char const*) 1.47 1.05 0.03 IntLigne::Copy(FloatLigne*) <---- 1.47 1.08 0.03 nr_path_matrix_bbox_union(NRBPath const*, NR::Matrix const&, NRRect*) 1.47 1.11 0.03 nr_object_check_instance_type(void*, unsigned) ...

2 3

layercake layercake baker's man...
by MenTaLguY 04 Jul '04

04 Jul '04

Just a quick note that I've been polishing the layers feature and even without the layers dialog it's becoming rather usable. So basic layers (of a sort) might actually make it in for this release. Here are some of the relevent changes: * I've retired the inkscape:groupmode attribute as it has served its purpose * You get Sodipodi-style "enter group"/"leave group" commands on the context (right click) menu which can be used to switch to using a group as a layer, or switch back to that group's parent * when a group is in this "layer" mode, the drawing tools create shapes within it and you can drag and select its objects directly Here are the items that are still needed: * The "group mode" setting needs to be per-NRArena key, and persist across hide/show cycles (currently, the change in event handling behavior is global, even though layer activation is per-SPDesktop) * Some sort of visual indicator of the current layer would be nice. I have provided an SPDesktop (SigC++) signal for this purpose, which can be connected to via SPDesktop::connectCurrentLayerChanged() * should e.g. "Select All" etc be influenced by the current group? -mental

4 9

layers credit
by MenTaLguY 04 Jul '04

04 Jul '04

I should also note that this was part of my inspiration as well: http://inkscape.org/cgi-bin/wiki.pl?ObjectManager -mental

1 0

Re: [Inkscape-user] Inkscape Text Rendering Strangeness...
by bulia byak 03 Jul '04

03 Jul '04

> One interesting bug that has cropped up occurs when I use the library to output some text and tspan elements. As an example I have included the original file, the output of svggrayscale.py, Inkscape's saved version of the output, and a fixed version of Inkscape's output. It seems to be adding extra text XML elements (tabs, newlines, spaces) when loaded in Inkscape, so the text displays with an offset to the right. At first I thought it was a problem with SVG-Utils, but librsvg 2.7.2 renders the output from svggrayscale correctly, so now I'm not sure. I hope you could look into this issue and help me to understand why it is happening. Use Batik and/or Adobe SVG plugin as reference renderers. In this case they both display the same as Inkscape, so the problem is not with Inkscape. Your script adds newlines between <text> and <tspan>. Within <text>, whitespace is meaningful and is displayed as text. Note that Inkscape, when creating <text>, does not leave any extra whitespace inside.

2 1

Inkscape Startup Times
by Bryce Harrington 03 Jul '04

03 Jul '04

--------------------- Real Time (s) ---- Inkscape Run 1 Run 2 Run 3 Run 4 Run 5 Average ============================================================== 0.35 0.125 0.119 0.118 0.119 0.120 0.120 0.36 0.142 0.140 0.142 0.144 0.151 0.144 0.37 0.200 0.195 0.193 0.196 0.195 0.196 0.38.1 2.289 2.317 2.297 2.303 2.309 2.303 CVS 0.720 0.725 0.727 0.732 0.720 0.725 --------------------- User Time (s) ---- Inkscape Run 1 Run 2 Run 3 Run 4 Run 5 Average ============================================================== 0.35 0.096 0.092 0.091 0.094 0.098 0.094 0.36 0.117 0.111 0.119 0.114 0.113 0.115 0.37 0.166 0.166 0.170 0.172 0.162 0.167 0.38.1 2.216 2.228 2.223 2.233 2.244 2.229 CVS 0.645 0.652 0.665 0.654 0.645 0.652 --------------------- System Time (s) ---- Inkscape Run 1 Run 2 Run 3 Run 4 Run 5 Average ============================================================== 0.35 0.014 0.013 0.016 0.014 0.010 0.013 0.36 0.011 0.016 0.011 0.013 0.016 0.013 0.37 0.026 0.022 0.021 0.016 0.025 0.022 0.38.1 0.040 0.036 0.034 0.036 0.031 0.035 CVS 0.046 0.035 0.034 0.046 0.044 0.041 I got curious about startup times, from bug reports that we've gotten from 0.38.1 users. I downloaded all the past Inkscape releases and replaced their gtk_main() call with exit(), and timed how long each took to get to that point. These tests were run on a 3GHz P4 with 512K cache and 1G RAM. Sure enough, 0.38.1's startup was significantly slower than previous releases. Good news it looks like CVS is much improved, although it's still slow compared with 0.37 and before. Bryce

2 3