- Inkscape Devel - Inkscape Mailman

Angled guidelines
by unknown＠example.com 19 Dec '07

19 Dec '07

Hi all, I am working hard on getting angled guidelines. At the moment, the only thing that is missing is UI + rendering. Snapping already works for example, Diederik has done a wonderful job on the snapping as it worked without any effort from me or him: just putting the right values in the places that were already there! cool ! I have probably broken the translation of the statusbar text. Can somebody please check whether it is still translatable? thanks a bunch, Johan

1 0

Representing frames in SVG
by Gerrit . 19 Dec '07

19 Dec '07

Hello everyone! I am using Swfmill to generate SWF files from SVG assets created with inkscape.All of my peers work with the Flash IDE though, therefore I'd like to implement an swf2svg conversion too, so I can swap assets back and forth. My question is: what would be the best way to represent frames (as in frame-based animation) in the SVG code? Afaik SVG doesn't have the concept of frames. SMIL animation can change references of use elements, but these are just normal symbols. Are there any plans to include animation or frames in Inkscape anytime soon? If so, I'd like to use the representation favoured by the respective developers. Otherwise, I might just use some interim attribute, e.g. class="frame" or something. Any insights will be appreciated! Gerrit _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

2 1

Launchpad mail subscription update
by Bryce Harrington 19 Dec '07

19 Dec '07

Mark Shuttleworth saw the write up about our experiences and remaining issues with Launchpad, and mentioned that some improvements for the email subscription for bug teams is in the work. I don't know the ETA but would assume it to be a 1-3 month type thing. Btw, I noticed today that we now have three Inkscape bug triagers with karmas over 1000 (and ryan's cracked 2000!) When we started in Launchpad, 98% of our 1900 open bugs were in state New; today this is down to 46% and the open bug count is down to 1710. Bryce <bryce> http://people.ubuntu.com/~brian/project-graphs/inkscape/plots/inkscape-mont… <sabdfl> bryce: the inkscape folks seems to think LP has helped? <ted> sabdfl: To answer for bryce, I think so. <ted> sabdfl: We've seen more bug triaging activity than we ever saw on Sourceforge. <ted> sabdfl: Bryce's write up: http://bryceharrington.org/drupal/node/18 <sabdfl> that's a neat write-up feature requests == blueprints and the bugmail situation should improve nicely when intellectronica's structural subscription work lands <ted> Hmm, never thought of blueprints as feature requests. More thought of them as "plans". <sabdfl> ted: they can start out as 1-liners then evolve to more concrete plans <bryce> sabdfl: yes it's definitely helped a lot with the triaging! <sabdfl> i liked your write-up and suggestions <bryce> thanks <sabdfl> thanks for taking the trouble! i bet it made all the difference getting the community over the hump

1 0

Upcoming About Screen Contest & Screenshots
by Joshua A. Andler 19 Dec '07

19 Dec '07

Hey all, Re: About screen I will be announcing the About Screen contest this evening. It will be held again via DeviantART. I plan on it running from 12/22-1/6 (to allow three weekends during the holiday season). Then the community judging portion will be done from 1/7-1/12. As with last time, the top 3 will be passed on to the dev team to determine what best represents the new release. I'm also thinking it would be good to change the number of submissions this go around to 2 per contestant rather than 3 (it seems less likely that we'll get minor variations). But, it still gives people the opportunity to try a couple different ideas. I was going to launch the contest a few days ago and realized that we were lacking up-to-date packages for Linux (autopackage) & OSX (.dmg). The OSX one is fairly recent, but lacks the refactored and enabled 3d box tool. Obviously the same goes for the APs. Additionally I believe a few other good bug-fixes went in during this period as well. Part of the reason that I wanted to shoot this pre-announcement to the list was to request that we please have up-to-date packages provided for those platforms (if possible). If we want the artsy people to use the new features, we should see if we can provide a way for them to do so (as they're generally not the compiling type). I also want to see if it would be possible to have packages produced on a semi-regular basis during the contest and bug-fixing phase so that the community can give better feedback. If anyone has any questions, thoughts, or input... please let me know. Otherwise, I do plan on making the announcement on DA tonight and CC'ing the lists with it as well. Re: Screeshots Bulia, I have two pieces that rock filters and LPEs. Is it cool to produce the screenshots now or do you think there will still be more UI changes happening soon? It will be VERY easy to produce them since they're the type that shows in-production use vs mini-tutorial style. Also, if you'd like a mini-tutorial style done for LPEs, I'd be more than happy to do that as well. Luckily I have a long weekend coming up and will be able to devote some time. -Josh

3 2

Tango icons set for Inkscape
by Michael Grosberg 19 Dec '07

19 Dec '07

A while ago I started cooperating with Jiho on restarting the Tangofication of Inkscape. Well, it's not yet finished but I'd like to hear your opinions on what I've done so far. Mostly I'd like your input on the following subjects, on which I'm not certain myself: *toolbox colors (square, arc, star, spiral) - should they be a single color or multiple colors? the original Tango Icon set has them all in white, but I tried to see what they'd look like in multiple colors. *lower / raise selection icons - I couldn't make a nice tango-style icon from the current icon so instead I changed it to look like the raise/lower icon from other applications such as office suites. *colors of all items which have generic looking squares in them, such as align, transform , grid arrange, clones, etc. I haven't settled on a single color and so some are blue while others are light gray. It shouldn't be hard to change colors as I've attempted to share a single gradient between all of the similarly-colored squares. the file can be downloaded here: http://geocities.com/preacher_mg/icons.svg Thanks in advance for any input - Michael

5 5

Alt and Mode_switch for shortcuts
by jiho 19 Dec '07

19 Dec '07

Hi everyone, On Mac OS X Leopard, the option/alt key is mapped to Mode_switch by default under X11 and this apparently cause it to no longer work as "alt" in Inkscape (the behavior is supposed to be consistent with the previous OS version though I never saw any problem with Alt before. anyway, they changed a lot of stuff on X11 side, not always for the better...). Modifying the ~/.Xmodmap [1] works for me but since Alt is so important in Inkscape I would prefer fixing it upstream rather than asking everyone to modify their ~/.Xmodmap.So my questions are: - what is the difference in essence between Alt and Mode_switch? Mode_switch in particular seems to be used rather inconsistently between the OSes, keyboards etc. - Would there be a problem in using Mode_switch or Alt conversely for all alt based shortcuts in Inkscape? Is it already the case in some places? - What about the Alt remapping hack. I could find a patch o the mailing list but nothing after that. I think it was applied though so how could I use it? Thanks in advance for your help. [1] ! This one switches both alt keys to be alt: keycode 66 = Alt_L keycode 69 = Alt_R clear mod1 add mod1 = Alt_L Alt_R JiHO --- http://jo.irisson.free.fr/

3 4

WMF handling, various apps and libs
by Tobias Jakobs 19 Dec '07

19 Dec '07

Hello, I hope a number of people would find this report interesting: http://www.sk1project.org/modules.php?name=Report Regards, Tobias

1 0

More recent autopackage builds?
by Richard Michael 18 Dec '07

18 Dec '07

I have a large PDF I've converted to PS an am attempting to edit in Inkscape, but it is causing quite a few problems. I'd like to test with the most recent version of Inkscape, but the latest autopackage build appears to be 07 Nov 2007. Are there any more recent pre-0.46 builds available? Richard

1 0

lxml errors on os X.5
by carl olsen 18 Dec '07

18 Dec '07

I'm on OS X.5 with Inkscape 0.45+devel, built Dec 8 2007 Whenever I try to use a filter get this: [] < The fantabulous lxml wrapper for libxml2 is required by inkex_lxml.py and therefore this extension. Please download the latest version from <http://cheeseshop.python.org/pypi/lxml/ >. [] < and when i try to install it, it has an error and doesnt finnish and I can't figure out what is up. This is a copy of all the stuff from the terminal when i'm trying to instal lxml: easy_install lxml Searching for lxml Reading http://pypi.python.org/simple/lxml/ Reading http://codespeak.net/lxml Best match: lxml 2.0alpha5 Downloading http://cheeseshop.python.org/packages/source/l/lxml/lxml-2.0alpha5.tar.gz Processing lxml-2.0alpha5.tar.gz Running lxml-2.0alpha5/setup.py -q bdist_egg --dist-dir /var/folders/ H9/H9Jwuv1LGha040cHGswzMk+++TI/-Tmp-/easy_install-Dt6zmJ/ lxml-2.0alpha5/egg-dist-tmp-Inbqr_ Building with Cython 0.9.6.9. Building lxml version 2.0.alpha5. warning: no previously-included files found matching 'doc/pyrex.txt' warning: no previously-included files found matching 'src/lxml/ etree.pxi' src/lxml/lxml.etree.c:69:31:src/lxml/lxml.etree.c:69:31: error: error: libxml/schematron.h: No such file or directory libxml/schematron.h: No such file or directory lipo: can't open input file: /var/folders/H9/H9Jwuv1LGha040cHGswzMk++ +TI/-Tmp-//ccI51eCM.out (No such file or directory) error: Setup script exited with error: command 'gcc' failed with exit status 1

1 0

help needed to fix a windows-only bug
by bulia byak 17 Dec '07

17 Dec '07

I would be grateful to anyone who can debug on Windows for any help with this critical bug: https://bugs.launchpad.net/inkscape/+bug/169011 I don't develop on Windows and I have no time to set it all up right now, but the bug seems somewhere in the style code which I know well, so if someone can tell me at least approximately where or when the unsetting happens I will probably be able to guess how to fix it. Thanks! -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

3 5

Fwd: [Clipart] Anyone Know How To Donate To Inkscape?
by ryan lerch 17 Dec '07

17 Dec '07

Forwardded on from the OCAL list... cheers, ryanlerch ---------- Forwarded message ---------- From: Greg Bulmash <oneminuteinspirations@...400...> Date: Dec 17, 2007 1:39 PM Subject: [Clipart] Anyone Know How To Donate To Inkscape? To: Open Clip Art Library list <clipart@...626...> Doing some year-end donations... not for taxes, but for karma. Already gave a few bucks to OCAL (via Jon) back when all the server issues happened. Used Inkscape a lot this year, so I figured it was worth a small sum. But I couldn't find anywhere I could donate. Even if it's not a 503c non-profit, I don't mind. Still happy to give a small non-deductible donation to say thanks for the great software and encourage its further development. If they're not comfortable calling it a donation, call it a a tip, a couple of bucks in the development team's collective g-string. Anyhoo, before I take that metaphor to places where people start wishing their imaginations had eyes to claw out, just wanted to ask if there was somewhere I could paypal $20 to say "thanks for doing that voodoo that you do so well." Anyone? - Greg _______________________________________________ clipart mailing list clipart@...626... http://lists.freedesktop.org/mailman/listinfo/clipart

2 1

the number of NEW bugs in the Tracker is now < 1000
by Ryan Lerch 17 Dec '07

17 Dec '07

Good news everyone, Your friendly Inkscape Bug Team has been busy triaging bugs over the weekend, and the total number of Bugs with a "NEW" status is now under 1000 (about 57% of total bugs.) When Triaging on Launchpad started a couple of weeks ago, this figure was up near 1900 (nearly 100% of all bugs) cheers, ryanlerch

2 1

reinterpret_cast unreliable on windows?
by bulia byak 17 Dec '07

17 Dec '07

I have fixed this windows-only bug, but I cannot fully understand how: https://bugs.launchpad.net/inkscape/+bug/169011 The problem was in this line: g_snprintf( b, len, "%s:%s;", key, css.gcharp() ); and gcharp is defined as: gchar const *gcharp() const { return reinterpret_cast<gchar const *>(ostr.str().c_str()); } The problem is that sometimes, rarely on some Windows systems and more frequently on others, gcharp() returned empty string for non-empty ostr. I replaced it with simply: g_snprintf( b, len, "%s:%s;", key, css.str().c_str() ); and the problem went away. Can anyone explain how this could happen? Is reinterpret_cast unreliable? Maybe we should eliminate it everywhere? -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

2 1

lxml + numpy (on OS X PPC but not only)
by jiho 16 Dec '07

16 Dec '07

Hi everyone, In order to provide out of the box python functionality on OS X for the upcoming 0.46 release, we'll bundle the python packages Inkscape uses in all flavors (i.e. ppc and intel, for every version of python). I would need someone who has these packages installed to send them to me: - lxml and numpy ppc with python 2.4.* - lxml and numpy ppc with python 2.5.* These two versions of python are *not* the one shipped with Mac OS X Panther or Tiger. They are typically obtained via MacPorts, Fink or the binary distribution of Python for Mac. MacPorts versions are in / opt/local/Framework/Python/.../lib/site-packages. Versions for the binary distribution of python are probably somewhere in /usr/local or in /Library/Frameworks/Python.framework/2.4/. I am looking for two directories in site-packages, unsurprisingly named lxml and numpy. If no-one has them already it would be really nice if someone could compile them for me on a PPC machine. This is really simple: - download lxml and numpy (from their respective homes, google is your friend ;)) - decompress them (usually already done for you) - in terminal sudo python setup.py install - go fetch the directories where they where installed (check the latest terminal messages), zip them and contact me. Thanks in advance. PS for the more knowledgeable around here: I am acting under the assumption that packages such as lxml and numpy are incompatible between point versions of Python (2.3 vs 2.4 vs 2.5), which is what I read somewhere. If someone has indication that this is not true, it would be very nice to point my mistake: things would be simpler and Inkscape won't grow too fat if we can just ship one version of the packages (the sum of all pyton packages will probably be around 70Mb, compared to the 80Mb of Inkscape itself, it seems a bit overkill...). JiHO --- http://jo.irisson.free.fr/

2 2

"make check" failures
by Ted Gould 16 Dec '07

16 Dec '07

Table of Contents: 1) Attributes -- looks like 3d-box tool 2) Style -- may be a bad test? 3) Bezier issue -- no clue 4) Rotate inversion -- no clue I'm not sure on all of these. I can of course start to look into them, but if you know you've modified these areas in the last year or so please look at the tests. Thanks, Ted --- 1 - Attribute test --- In AttributesTest::testAttributes: ./../../src/attributes-test.h:448: Error: Test failed: "azimuth" ./../../src/attributes-test.h:448: Error: Expected (recognized == all_attrs[i].supported), found (true != false) ./../../src/attributes-test.h:448: Error: Test failed: "elevation" ./../../src/attributes-test.h:448: Error: Expected (recognized == all_attrs[i].supported), found (true != false) ./../../src/attributes-test.h:448: Error: Test failed: "in" ./../../src/attributes-test.h:448: Error: Expected (recognized == all_attrs[i].supported), found (true != false) ./../../src/attributes-test.h:448: Error: Test failed: "limitingConeAngle" ./../../src/attributes-test.h:448: Error: Expected (recognized == all_attrs[i].supported), found (true != false) ./../../src/attributes-test.h:448: Error: Test failed: "pointsAtX" ./../../src/attributes-test.h:448: Error: Expected (recognized == all_attrs[i].supported), found (true != false) ./../../src/attributes-test.h:448: Error: Test failed: "pointsAtY" ./../../src/attributes-test.h:448: Error: Expected (recognized == all_attrs[i].supported), found (true != false) ./../../src/attributes-test.h:448: Error: Test failed: "pointsAtZ" ./../../src/attributes-test.h:448: Error: Expected (recognized == all_attrs[i].supported), found (true != false) ./../../src/attributes-test.h:448: Error: Test failed: "result" ./../../src/attributes-test.h:448: Error: Expected (recognized == all_attrs[i].supported), found (true != false) ./../../src/attributes-test.h:448: Error: Test failed: "z" ./../../src/attributes-test.h:448: Error: Expected (recognized == all_attrs[i].supported), found (true != false) ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 11 {inkscape:path-effect} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 53 {inkscape:snap-bbox} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 54 {inkscape:snap-nodes} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 55 {inkscape:snap-guide} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 56 {inkscape:snap-center} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 57 {inkscape:snap-intersection-grid-guide} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 58 {inkscape:snap-intersection-line-segments} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 61 {inkscape:bbox-paths} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 62 {inkscape:bbox-nodes} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 74 {inkscape:original-d} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 80 {inkscape:3dbox} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 81 {inkscape:box3dcornerA} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 82 {inkscape:box3dcornerB} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 83 {inkscape:box3dcornerC} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 84 {inkscape:perspective} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 85 {inkscape:box3dface} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 165 {flood-color} not handled" ./../../src/attributes-test.h:491: Warning: "Attribute string with enum 166 {flood-opacity} not handled" ./../../src/attributes-test.h:496: Error: Assertion failed: !found ./../../src/attributes-test.h:501: Error: Test failed: "Enum round-trip through string {flood-color} failed." ./../../src/attributes-test.h:501: Error: Expected (index == postLookup), found (165 != 257) ./../../src/attributes-test.h:501: Error: Test failed: "Enum round-trip through string {flood-opacity} failed." ./../../src/attributes-test.h:501: Error: Expected (index == postLookup), found (166 != 258) --- 2 - Style --- Testing style... sp_style_new, sp_style_write_string...Assertion `streq(str0_all, str0_all_exp)' failed sp_style_merge_from_style_string(whitespace, ifset...OK sp_style_merge_from_style_string(whitespace, always...Assertion `streq(str0_all, str0_all_exp)' failed sp_style_merge_from_style_string("fill:", ifset)...OK sp_style_merge_from_style_string("font-family:", always)...Assertion `streq(str0_all, str0_all_exp)' failed sp_style_merge_from_style_string("fill: ", ifset)...OK sp_style_merge_from_style_string("font-family: ", always)...Assertion `streq(str0_all, str0_all_exp)' failed sp_style_merge_from_style_string(":none", ifset)...OK invalid color setting: #4321...Assertion `streq(str0_set, "color:#123")' failed invalid color setting: currentColor...Assertion `streq(str0_set, "color:#123")' failed invalid color setting: #87654321...Assertion `streq(str0_set, "color:#123")' failed invalid color setting: #42...Assertion `streq(str0_set, "color:#123")' failed invalid color setting: aquam...Assertion `streq(str0_set, "color:#123")' failed sp_style_merge_from_style_string(default): ifset...Assertion `streq(ifset_str, str0_all_exp)' failed sp_style_merge_from_style_string(default): always...Assertion `streq(ifset_str, str0_all_exp)' failed sp_style_merge_from_style_string...Assertion `streq(str0_all, str0_all_exp)' failed SP_SCALE24_MUL...OK sp_style_merge_from_dying_parent: opacity...OK style: FAILED (6/18 tests passed) --- 3 - Bezier issue --- bezier_pt(1)...Assertion `bezier_pt(1, a, ti) == si * a[0] + ti * a[1]' failed sp_bezier_fit_cubic...Warning: got different control points from previously-coded (diffs=0x3c). Previous: (5, -3) (7.57134, -0.423509) (4.77929, 1.22426) (3, 3) Found: (5, -3) (7.32396, -0.46791) (5.06163, 1.32841) (3, 3) TODO: Update this test case for revised right_tangent implementation. --- 4 - Rotate issue --- inverse...Assertion `rot234.inverse() == NR::rotate(-.234)' failed

4 5

Grids
by Maximilian Albert 13 Dec '07

13 Dec '07

Hi all! Diederik, thanks a lot for enabling the axonometric grid in SVN! It's great to play around with it. Just one small thing I noticed: It doesn't honour the "snapping enabled" option in the Document Properties dialog. As I was giving it a try I was for a short moment a bit confused that the newly created grid (which had the checkbock "visible" ticked) didn't appear on the canvas - until I remembered to press '#' to make all grids visible. I still believe that users unfamiliar with the way it works may be quite confused by this behaviour. Any suggestions how to make the difference between enabling grids globally and individually more obvious to users? Would it be sufficient to add a caveat to the the tooltip in Document Properties? Max P.S.: Just noticed one other thing. When more than one grid is present then pressing '#' always switches to the tab of the first grid in Document Properties. This is a bit annoying when you actually want to work with the second grid, for example. Is there an easy way to change this?

9 17

The 3D box tool is dead. Long live the 3D box tool!
by Maximilian Albert 13 Dec '07

13 Dec '07

Hi all, I don't know how many times I announced this, but it has finally happened: As of rev #16681 the new, completely reworked(TM) 3D box tool code is now in SVN, hopefully still in time for 0.46. Those of you who played around with the tool before may have noticed that although it was certainly usable, there were a couple of issues; most notably, undo/redo didn't work reliably, some box configurations in degenerate perspectives were not really stable, etc. But most of all, development was getting more and more of a pain, making both debugging and adding new features tremendously difficult. All this was due to the internal architectural design of the tool at the time. Since I didn't see a way to easily sort this out by continuing the chosen path (and even if I had, it would only have led the tool even further into a dead end as far as extensibility and applicability to other 3D related tasks are concerned), I decided that it would be better to rewrite a lot of it more or less from scratch. I apologize that this has taken me so long, but I'm studying for my finals right now (or rather should be :-/ ), which has been a major distraction for completion. Anyway, the bulk is done now, and I'd like to give you a very quick overview of the changes. As far as the "ordinary" user is concerned, the overall behaviour of the tool is roughly the same as before, except that it is more stable and reliable. :) (In particular, there haven't been any great new features added yet). The most notable visible changes are the following: - Boxes now come equipped with a default depth, i.e. simply dragging on the canvas creates a full-featured box. This hides the allegedly hard-to-discover Shift+drag feature from the user and makes it easy for newcomers to find out what the tool actually does. - Boxes sharing the same perspective move together when a vanishing point is dragged, as if they form part of the same 3D scene that is simply viewed from a different angle (before, they all moved independently of each other). This makes it easy to create entire scenes and adjust them as a whole during drawing. If you want boxes to move independently of each other, you can split perspectives up by shift-dragging a vanishing point. For a full list of this and other features of the tool, please wait until I have updated the Release Notes (a copy will be posted to this list). So much for the visible part of the tool. For those who are interested here comes a more in-depth description of the internal changes: 1) *All* 3D box related structures (namely, the box itself, its sides, and also perspectives) are now handled as SPObjects, which fixes the annoying issues with undo/redo. A notable consequence is that the SVG representation of boxes is now slightly different than it was before, which probably renders old files invalid or even unusable. This shouldn't be a great issue, though, since the tool has not officially been enabled yet (which turns out to be a good decision). I'm going to give the current representation a final revise in the next one or two days, but I don't expect it to change any more. 2) Perspectives are now added to the document's defs so that they can in principle be reused by other objects. This doesn't have an immediate effect on the tool itself but should make applications to other 3D related situations easier. 3) Before the refactoring, all constructions were made geometrically by computing connecting lines, points of intersection, etc. The way it works now is that we use the information given by the three vanishing points to compute a mapping from 3D space to the canvas which results in the specified perspective. By computing inverse images of canvas points, this allows us to determine "real" 3D coordinates of boxes, to model the concept of lengths (at least to a certain extent), to compare coordinates of boxes, etc. Also, degenerate perspectives can be handled in a numerically stable way because not the boxes themselves are degenerate but only their _images_ on the canvas. In fact, this description is a bit of an oversimplification. In order to compute the mentioned perspective mapping, it is necessary to (at least implicitly) specify a _fourth_ point on the canvas, which can be thought of as the origin of the coordinate system (whose three axes point towards the vanishing points). This fourth point is not currently represented on screen. A while ago in one of our discussions Bulia suggested that it should be hidden from the user because its meaning might be unintuitive. Personally, I'm not entirely convinced and I'm tempted to leave it as an option to the user whether it should be drawn on the screen or not (it can also be quite useful for adjusting 3D scenes). Any opinions from other people? At present you can visualize this point by pressing 'O' in the 3D box tool (you may need to draw a box first). This draws a small pink point on the canvas. Note that I added this shortcut for debugging purposes and it will be removed later on. Think of this point as the "anchor" of the coordinate system - it is the only point that always remains fixed when vanishing points are dragged. Well, that is pretty much all I can think of at the moment. Please ask if you are missing anything or if something remained unclear. In principle, everything should more or less work now. There are a few known issues I'm going to sort out in the next days, including (but probably not limited to) the following: - I had to temporarily disable the spin buttons in the toolbar after introducing an undo-related crash yesterday (Inkscape chokes with the message "assertion failed: (doc->priv->sensitive)"). I will debug this and make them work again very soon. In the meantime, the states of vanishing points can be toggled using the shortcuts "X", "Y", and "Z". In addition, the angles of infinite perspective lines can be rotated using the various types of brackets - namely [], (), {} (where Alt+dragging results in a very small rotation angle). - Although z-orders should be set reliably now, there may be a few degenerate cases where they are still wrong (I think I know which these are). If you discover such a case, you can send me a corresponding *.svg file if you wish. - Transformations of boxes work, but if a single box is transformed this also transforms all other boxes sharing the same perspective. Bulia said that instead this box needs to be unlinked. Will fix this soon. - Stroke, patterns, and gradients are not yet adapted during transformations. I'll have to see how to do this because transformations are implemented differently in 3D boxes than in the other tools. Any general pitfalls I need to know or keep in mind regarding this? - Constrained dragging of handles (by using Ctrl) somehow sets the box off a certain amount from the intended position. Don't know precisely what causes this but I hope it won't be hard to fix. - flipping boxes doesn't update its z-orders - ... whatever you may discover ... As always, if there are any questions, comments, suggestions, you name it - please don't hesitate to tell me. And now: Happy testing and enjoy. :=) Cheers, Max P.S.:There is still a number of debugging messages present in the code (most of them commented out, but maybe I forgot some). I will of course get rid of them soon, but currently they are helping me in resolving the remaining issues, so I left them in.

5 8

compile error on windows
by bulia byak 13 Dec '07

13 Dec '07

trying to compile with bob's latest mingw: In file included from src/transf_mat_3x4.cpp:17: src/syseq.h: In function 'void SysEq::fill_random(double (*)[T], double, double)': src/syseq.h:74: error: there are no arguments to 'random' that depend on a template parameter, so a declaration of 'random' must be available src/syseq.h:74: error: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated) -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

3 3

Error: Unknown verb name
by Maximilian Albert 13 Dec '07

13 Dec '07

Hi, for a while now I have been getting the following error messages during startup if Inkscape: ** (inkscape:6536): WARNING **: Unknown verb name: EditCloneOriginal Unable to find: EditCloneOriginal ** (inkscape:6536): WARNING **: Unknown verb name: EditCloneOriginal Unable to find: HelpKeys ** (inkscape:6536): WARNING **: Unknown verb name: HelpKeys Unable to find: org.inkscape.help.keys Even "make clean" didn't help. Any ideas where they come from? I can't imagine that everyone is seeing this because no one else has complained so far. Thanks! Max

2 3

Process for patching 2geom
by John Faith 13 Dec '07

13 Dec '07

Hello, A while ago I submitted a patch which helps OS X build to the 2geom SourceForge tracker assuming that the patch would be added to 2geom, then 2geom would be updated in inkscape source. Is this correct or should I submit a patch to the new launchpad system? It's been about a month and nothing has happened with the patch, so I guess I must have done something wrong. Thanks!, John

3 2

Inkscape overcomes Xara in Google Trends
by bulia byak 12 Dec '07

12 Dec '07

http://www.google.com/trends?q=inkscape%2Cxara Note that "xara" does not always refer to the vector editor, so in reality it's even better for us. Now, to support the momentum, we must release a smashing 0.46 soon enough, and make a lot of noise about it. It really deserves it. (Note by the way that while we are ahead in user interest, we are nowhere to be seen on the lower graph which reflects mentions in the news. That's not fair.) GSoCers and all others, please let's get to work one more time and fix all the loose ends in your projects. They need not be perfect but the most glaring user-visible problems must be ironed out for Inkscape to reach a releaseable state. You know who you are and what you need to do :) If you think that your project is already good enough for a release, please drop a note here, otherwise let us know of your current state, what remains to do, and when you are planning to finalize your work. And, let's make bugfixing a priority right now, even without waiting for a freeze. We have a scary number of open bugs in the tracker. Yet we now have so many developers that if each one closes just one bug a day, we'll make the tracker shrink pretty fast. Note that closing a bug need not necessarily involve coding; you can just take some old bug, test it and close as fixed or unreproduceable. Any help from non-developers is of course very welcome too. Let's all test, report, comment, add info, code, test again, and close as many bugs as possible. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

19 38

svn/deb
by Alexandre Prokoudine 12 Dec '07

12 Dec '07

Hi, >From what I remember, there is a repository to provide .deb files for SVN revisions. Should we add it to http://inkscape.org/download/, "Compiled Packages" section? Alexandre

2 3

need-review: Default Metadata Preferences Patch
by Felipe Sanches 12 Dec '07

12 Dec '07

hi! I have just submitted a patch that implements a "default metadata" page on the preferences dialog. This defines the default values to be used as metadata for newly created documents. I need someone to review this code, please. It works fine for me. There is just one little issue: I havent been able to figure out how to update the status of the license radiobuttons on the documentMetadata dialog. Some more experienced programmer could, please, take a look at it? I imagine that it may be a simple thing that is still just not clear enough for me. This is my first patch for inkscape, so I am not much comfortable yet with the overall structure of the program. here is the patch: http://sourceforge.net/tracker/index.php?func=detail&aid=1746892&group_id=9… thanks, Juca

7 15

Inkscape 0.46 Chill
by Bryce Harrington 12 Dec '07

12 Dec '07

It looks like we've given enough time for finalizing development work, so I'd like to shift us into release mode by entering our Chill phase. Here's the tasks to focus on now: Chill. Development focuses on wrapping up. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes. Update tutorials and other docs Triaging is probably the biggest task ahead of us. I'll try to focus my time on assisting here; I'll try to focus on scripting of bulk changes, as I've got several ideas for cleanup projects on the wiki. Ted, could you post a listing of recent development work, and collect status from the developers, so we can see if there's any remaining absolutely must-do tasks before we release? ACSpike, would you mind doing a first pass at running make distcheck and post to the list what errors there are that we'll need to sort out? Ryan Lerch, can you give us an update on where things stand for bug triaging, and where other people can get involved? Scislac, would you be able to run an about screen contest for us again? I figure we can do it just like the 0.45 contest. Bulia, the Release Notes look like they're in great shape, but you generally have the best eye of any of us on them. Could you identify any major holes we need filled (esp. with names of people we need to get to write stuff up). ScislaC and Bulia - how do we sit currently respecting tutorials and docs? I think it's too late in the game to start writing any new ones, but if there's high priority stuff that absolutely must get done, we should list it out now and make sure we've got people to tackle them. Finally, if anyone has questions or concerns of anything that needs to be handled or accounted for during this release, or wishes to help out directly in the release process, this is the time to speak up. Let me know of any release issues and I'll help make sure they get straightened out. Bryce On Sat, Nov 03, 2007 at 10:56:46AM -0700, Bryce Harrington wrote: > Hi all, > > Now that GSoC projects are finished and the code has had time to > stabilize, it seems a good time to get the 0.46 release moving ahead. > With Gutsy released, I finally have some time to contribute towards > Inkscape release work, and will help try to get efforts organized. > > I'd like to propose the following release plan, based roughly on the > 0.45 plan. Let me know if there's anything missing. > > 1. Open development. > > 2. Chill. Development focuses on wrapping up. > Identify 'make distcheck' issues > Triage bug reports > Run an About Screen contest > First draft of Release Notes. > Update tutorials and other docs > > 3. Frost. Most development complete. > Release Notes should be >90% filled in. > Bug Hunt: 500 points > Post inkscape-0.46-alpha.tar.gz > > 4. Feature Freeze. No further development work. > Disable features that can't be finished in time > Focus on critical bug fixing. > Finalize all tutorials, docs, etc. > Finalize all extensions > Translators create translations. > Inkscape must pass 'make distcheck' > Post inkscape-0.46-beta.tar.gz > > 5. Hard freeze. Only release wardens can commit to mainline. > No further string changes > Focus on release-critical bug fixing. > Finalize translations, release notes, etc. > Packagers test creating pkgs of the -beta release > Post inkscape-0.46-rc1.tar.gz > > 6. Branch. Establish the Stable Branch for release > Complete any late-late-late work. > Final verification of packaging, release notes, > docs, etc. > Publish more release candidates until ready for > release. > Plan 0.46.1+ release(s), if needed > > 7. Release. Post inkscape-0.46.tar.gz > Post packages > Post official announcements > > 8. Open development. > > > I'm sort of thinking for this release we ought to plan on establishing a > stable branch much earlier than we've done before, and maintain split > devel / stable branches for a bit (maybe a couple months). I think > that'd allow us to spend much more time than usual getting things > release-worthy, without too heavily impacting people who wish to keep > doing development work. > > We'll have a bunch of interesting random tasks (mostly non-coding) to do > to get the release polished up and ready to go. Are you interested in > participating in the release team? Let me know! > > Bryce

15 49

filters UI
by Felipe Sanches 11 Dec '07

11 Dec '07

nicholas, when I open the filters dialog in a document that doesnt have any filter primitives, I can see all of the settings widgets in the dialog. They should be hidden, instead. can you please try to fix this issue? Felipe (Juca)

1 0