- Inkscape Devel - Inkscape Mailman

Color choosers -- why isn't swatches with the others?
by Michael Moore 26 May '06

26 May '06

I was just wondering why the swatches color chooser isn't with the other color choosing methods in the fill and stroke dialog? Thanks, -- Michael Moore ------------------------------- www.stuporglue.org -- Donate your used computer to a student that needs it. www.ubuntu-utah.org -- In Utah? Interested in Ubuntu? Come join us.

4 4

libsigc++-2.0.11 required
by Ralf Stephan 26 May '06

26 May '06

Hello, since we could not find a workaround for the compile problem with libsigc++-2.0.10 + gcc-4.0.2, and 2.0.11 is over a year old, I have bumped up the requirements for compiling inkscape in configure to libsigc++ >= 2.0.11 and will update documents on the Web accordingly. ralf

7 11

NEW: improved "stroke to path" command
by bulia byak 26 May '06

26 May '06

I finally fixed the long-standing bug 933482: * Converting stroke to path now correctly processes dashed strokes. For paths with markers, this command now creates a group containing the stroke converted to path and all its markers as independent objects (i.e. they are not markers anymore, but instead you can easily transform them or paint them any color, as a workaround for the "markers don't take the color of the stroke" bug). -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

Xara LX 0.5 released
by MenTaLguY 26 May '06

26 May '06

http://lwn.net/Articles/184866/ The new Xara release has layer support and clipping paths -- looks like we've got some healthy competition again. :) -mental

2 1

Inkscape 0.44 Bug Status
by Bryce Harrington 26 May '06

26 May '06

Hi all, Now that we are in Feature Freeze, attention turns to bug fixing. As we've done before, we'll establish a point goal - 200pts. Each fixed bug between today and release will count towards that score. Low priority bugs score 3pts, medium 6pts, and high 9pts. When we've hit that list, *AND* closed all the Must-Fix bugs for 0.44.0, we will move into the Hard Freeze phase, and give control over to the release wardens to finalize the release. Must-Fix List for 0.44.0 ------------------------ *rwst 1467073 (DONE) make distcheck failing cyreve 1493680 Build: no compile with FreeType-2.2.1-2 ishmal 1489175 Win2K crash: entrypoint FreeAddrInfo not found ishmal 1489961 Autopackage: crash on save as ODG acspike 1244836 use newer glib2 on official build system Needs Fixed in 0.44.x Stable Series ----------------------------------- cyreve 1494337 Fonts/Win: this TTF font crashes Inkscape (pango error) rwst 1467137 Shrinking a pattern causes lock-up cth03 1488128 Snap: Aligning (Snapping) to Grid or Guides does not work joncruz 1418122 Conf corruption when opening files with non-UTF encoded joncruz 1370772 WinXP: Preferences.XML can't be accessed mjwyb 1448811 Connector: assertion failure when moving empty group ishmal 1395505 0.43 crash at startup on Win98se mental 1441003 Misc: flowRoot error with inkscape's svg cyreve 1448618 Fonts: weight variants selection rwst 1493580 SuSE: CVS builds but will not run on Suse 10.0 cth03 1429049 Snap: near-freeze in ObjectSnapper::_findCandidates with ~1000 obj Needs Fixed for 0.45 -------------------- dwyip 1464771 whiteboard: cannot connect to jabber server then crashses cth03 1431560 Snap: Crash at resizing/snapping to guidelines Needs Owner in Order to be Prioritized -------------------------------------- ---- 1484076 potrace freeze with multiple color scan ---- 1475189 Extension ignored by inkscape ---- 1468393 square/circle/polygon/spiral and linked offset misbehaviours ---- 1491646 WIN - Win32 extensions does not call delivered Python ---- 1491925 gradients referenced from masked object disappear ---- 1490430 [INFO NEEDED] Crash in libcairo.dll ---- 1489794 crash with composite ---- 1459502 Crash on imported image update (during Gimp save) ---- 1349761 Inkboard: inkscape crashes when trying to connect Note that I've deliberately kept the list of must-fix bugs for 0.44.0 very lean, so that we can release sooner rather than later. If you disagree and have a bug that you think really must go there, then please speak up now, and explain why it should be a release blocker. Some of the rationale I used for de-ranking bugs: Difficulty confirming the bug. Bug appears to affect just the reporter. Bug doesn't cause crash or data loss. Crash is due to something very unusual (like a specific font, or a directory with unicode characters, or selecting >1000 nodes while snapping is on, etc.) Bug is in a feature not enabled by default (i.e. inkboard). Also note that this list doesn't accept bugs unless they have an owner. This is strictly for pragmatic reasons - without someone volunteering to take care of it, we may end up waiting a very long time to close it. In past releases, we've often ended up simply having to release with these sorts of bugs anyway, so I figure, why accept them as Must Fixes in the first place? ;-) Bryce

3 6

Nuke gay whales for Jesus
by jonmarc paeton 25 May '06

25 May '06

1 0

Inkscape release status. Feature Freeze is on 5/23
by Bryce Harrington 25 May '06

25 May '06

Here's the latest status: ICC Preview - HOLD CMYK support - HOLD ArtLibre named icon and cursor loading - HOLD Palette editing and per-file color sets - HOLD Tablet Bugs - BUG Brush size adjustment on zoom toggle for calligraphic pen - DONE Layer dialog Fit Canvas to Selection - DONE ODG Format Support - HOLD DOM Support - HOLD SIOX Support Extensions Snapping - BUG Rendering Performance Speedup - DONE Screenshots Tutorials Calligraphic interface tweak - DONE Windows font handling bugfixes - DONE Python Extensions on Windows Text/Fonts UI Windows "dialogs on top" Patch for GTK - HOLD Undo/Redo Dialog - HOLD New File Chooser in Export - DONE Test Harness Two tasks are being converted into "Must Fix Bugs" since they're really bugs, not features. A few are now DONE, and a bunch we've agreed to put on HOLD for 0.45. The remaining 8 we're going to give a few more days. I hope that will be sufficient time to complete them all. In any case, we will be feature freezing on the 23rd, and move into bug fix mode then. Meantime, ACSpike, can you produce a -pre0 release within the next couple days, to give our testers something to start playing with? Current Feature Work ICC Preview - HOLD =========== Jon Cruz is working on this. Plans to have feature to a finished point for the release. 5/17 - Jon has put this on hold in order to contribute to getting the layer manager completed. CMYK support - HOLD ============ Jon Cruz is working on this. Plans to have feature to a finished point for the release. 5/17 - On hold until post-0.44 due to dependency on Peter's union purge ArtLibre named icon and cursor loading - HOLD ====================================== Jon Cruz is working on this. Plans to have feature to a finished point for the release. 5/17 - On hold until post-0.44 due to dependency on Peter's union purge Palette editing and per-file color sets - HOLD ======================================= Jon Cruz is working on this. Plans to have feature to a finished point for the release. 5/17 - On hold until post-0.44 due to dependency on Peter's union purge Tablet Bugs - BUG =========== MentalGuy is working on this. Says for the release he wants to get these resolved. Something drops tablet motion events on the floor while the button is held down. This occurs for some tools, but not with others. The bugs are quite annoying but weird. They don't affect all tablet users. 4/29 - Still underway 5/19 - Still unresolved. Mental considers this a release blocker. Brush size adjustment on zoom toggle for calligraphic pen - DONE ========================================================= MentalGuy is working on this and plans to have it to a finished point for the release. 5/1 - Mental reports this has been completed Layer dialog ============ This is an important feature for the release, and on MentalGuy's todo list. However, work has been stuck getting Inkscape::LayerManager to compile due to a subtle detail with sigc::mem_fun(), and it's uncertain if there is sufficient time to unstick it and finish the feature prior to the release. Additional people's help may be needed here. [Beyond the memory issue, are there other aspects to the layer dialog that others could help with, such as UI work or coding helper features or whatever? --bh] 4/29 - Still under way 5/17 - Huge amount of progress made on it. Still not to a point that it's ready to release, but it's close. One of the major remaining issues is that the layer manager is destroying and recreating the hierarchy when the user selects a different layer. This causes state to be lost, which results in a few ui quirks that will probably be irritating for users. It'll be worthwhile to give another day or two for development before freezing this feature. 5/19 - Mental mentions that with the advancements in the new layer dialog, the quick layer selector needs to be reworked as well, as a lot of previously hidden bugs now become apparent when reordering layers and/or using nested layers. The back-end portion needs to be replaced with LayerManager. If we don't do this, we can expect many bug reports that the layer selector is broken. This is perhaps a couple day's work to get done right. Fit Canvas to Selection - DONE ======================= This is a feature ACSpike has been working on, and plans to complete for the release. The patch is here: http://www.ekips.org/comp/inkscape/inx/current.diff ODG Format Support - HOLD ================== Ishmal is working on this currently. Help is needed from someone who knows inkscape gradients, such as mental or bulia. He needs to know how to read gradient info from an SPGradient object. 5/20 - not a release killer; going to leave it for .45. Ishmal had wanted to get some of the clipart and example images to look the same on oo.org as in inkscape. DOM Support - HOLD =========== Ishmal has been working on this. The newest code is all imported and builds. [Is there anything else needing to be done prior to release?] 5/20 - xpath won't make this release. The parsing and compilation are ok, but binding isn't yet, and will need to wait for a future release. SIOX Support ============ Ishmal has this over half done. The code is all imported and building, and the selection mechanism is now done. Getting Inkscape and SIOX intercommunication working, but this can be built as a filter to potrace, which simplifies things. The transformation issues reported previously have been sorted out, using a "confidence matrix". 5/20 - Ishmal says this is incredibly close and wants to finish it before the release. He's planning on devoting the next few days to it. He will need a lot of help testing it. Extensions ========== Ted is focusing on cleaning up extension parameters and felt he'd have this wrapped up by the end of the month. The plan is to have longer text (tool tips) available, and a few more widgets. More spacing in the autogui will be added to make it look nicer. * Ted reports there is an unverified bug in the ordering of the effects in the menu, to be investigated. The Extension Editor is further off, and not being planned for this release. 5/1 - Ted reports the feature is not yet working, but feels it shouldn't be a problem to get it fixed in the next couple weeks. 5/10 - Descriptions are added and status bar messages work. Tooltips have been implemented but don't work for some reason. The major remaining piece is documentation - release notes and a post about the new INX file parameters. * Update release notes Snapping - BUG ======== Ralf is coming up to speed on this issue. Hopefully Carl can also shed light on things. On 4/26 Carl said he hopes to have a look at it over the coming week. * Need to fix the freeze when dragging multiple selected objects: http://sourceforge.net/tracker/index.php?func=detail&aid=1429049&group_id=9… * Update Release Notes Rendering Performance Speedup - DONE ============================= Andrius has a very interesting rendering speedup patch. The feature is complete and accepted for the release. There is one known issue to address with scrolling, but Andrius feels this can be fixed. 4/30 - Andrius reports this is now done, and no other issues are known. Screenshots =========== Scislac has taken this task on, and plans to have it done for the release. Two screenshots are done currently, and one more is in the works. There will be a call for more screenshots on the Deviant Art site. 5/20 - 2 of 8 screenshots are uploaded. One is waiting on the text toolbar work. The ones related to "Tremor"... I'd prefer to have nicer art for that purpose (I have some that can suffice, but I'd like better ones). The Paste Size one which I haven't touched yet, but that will be fairly easy since it just needs to be "technical". I have the selected style indicator one which is probably a LOT of compositing to have most, if not all states. And I also have a relatively simple one to whip up for non-destructive node deletion. Tutorials ========= Calligraphy is mostly done, and a few of the other updates to the other tutorials have been drafted but that stuff definitely needs more work. Should be possible to have them done by the end of April. Man page should be current. Bulia will update keys.xml shortly. Note: The sooner these can be finalized, the sooner translators can get going on them. 5/1 - ScislaC says a lot of progress was made over the weekend, but has run into some errors regenerating the svgs & html Calligraphic interface tweak - DONE ============================ Bulia is working on this change requested by MentalGuy, and feels they are minor and should have no trouble completing for the release. Windows font handling bugfixes - DONE ============================== Richard (cyreve) has completed these bug fixes and updated the release notes. * Update ReleaseNotes Python Extensions on Windows ============================ !!! No owner has been identified for this task !!! Bulia reports that extensions that rely on PyXML still do not work on Windows. Due to the number of python extensions, this would be a major missing feature for Windows users. Text/Fonts UI ============= deadchip (aka Milosz Derezynski <internalerror at gmail dot com>) has written a font lister Gtkmm class, to enable re-use of the font list. He is planning to write a font picker dialog, and rewrite the current font picker to use the font _listing_ class. This enables using normal Gtk components (ListStore, etc.) for accessing the font info. He plans to have this work done by May 1st, or May 15th at the latest. Windows "dialogs on top" Patch for GTK - HOLD ====================================== !!! No owner has been identified for this task !!! This is not exactly an Inkscape-specific problem, since the code changes wouldn't be to Inkscape, but it would be nice to have it finally fixed. This 0.44 release effort may be a good vehicle to tie it to, but we won't hold up the release if it doesn't get done. Scislac had contacted the author previously. * Send a reminder email to the author to find status on this 5/20 - Not a release killer; we'll punt on this one Undo/Redo Dialog - HOLD ================ Gustav Broberg (broberg at kth dot se) is planning to try to get the changes Mental suggested prior to the Feature Freeze. We have a patch for this. Also needed is undo annotations. 4/30 - Gustav reports that due to more changes required than expected, this feature will be postponed until the next release. New File Chooser in Export - DONE ========================== We have a patch for this, but there were some thoughts of embedding it in the export dialog directly. In the spirit of "patch first, discuss later", the best approach may be to stick in the current patch for 0.44, see what folks think, and do the embedding later. Test Harness ============ Bryce is working on getting 'make test' working in the test harness. It works currently, but the data is not getting included in the reports. In fact, I seem to have busted the reports entirely, so it'll take a bit more poking at to make it work. Additional Release Tasks ======================== The following tasks will need to be done for the release, but are not required to be done prior to the Feature Freeze: * Identify the list of must-fix bugs. To keep the freeze phase from dragging out, we will need to be very choosy in what we allow to be must-fix bugs. * Set up a ReleaseChecklist wiki page or similar to keep track of The List. * Designate 2 release maintainers. * Keep and update the above list and encourage people to achieve completion of the items. * Notify translators to complete translation work * Wiki updates + Update Roadmap + Review/Update FAQ + Update InkscapeFeatures * PR / marketing efforts + Plan efforts + Draft press release + Finalize press release + Send out press release [rejon] + DeviantArt PR [ScislaC] * Packaging

7 9

[Fwd: [Inkscape-tester] inkscape build report]
by Bryce Harrington 25 May '06

25 May '06

With Kees' help last night, we got the test harness back online. But we're not certain if the issues shown below are legit, or due to changed dependencies. Jon or rwst, any advice you could provide? Bryce ----- Forwarded message from root <root@...1070...> ----- Date: Thu, 25 May 2006 05:21:03 -0700 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Thu May 25 04:22:04 2006 (Run 3043) Snapshot: inkscape-20060525-0400.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 1 1 52 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == checking for LCMS... configure: error: --enable-lcms was specified, but appropriate LittleCms development packages could not be found conftest.c:2: error: syntax error before "me" cc1: error: unrecognized option `-Wno-pointer-sign' conftest.cc:15: error: `exit' undeclared (first use this function) conftest.cc:15: error: (Each undeclared identifier is reported only once for each function it appears in.) conftest.cc:21: error: `p' was not declared in this scope conftest.cc:21: error: `i' was not declared in this scope conftest.cc:22: error: initializer list being treated as compound expression conftest.cc:22: error: syntax error before `char' conftest.cc:24: error: syntax error before `{' token conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:21: error: `p' was not declared in this scope conftest.cc:21: error: `i' was not declared in this scope conftest.cc:22: error: initializer list being treated as compound expression conftest.cc:22: error: syntax error before `char' conftest.cc:24: error: syntax error before `{' token conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:21: error: `p' was not declared in this scope conftest.cc:21: error: `i' was not declared in this scope conftest.cc:22: error: initializer list being treated as compound expression conftest.cc:22: error: syntax error before `char' conftest.cc:24: error: syntax error before `{' token conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:21: error: `p' was not declared in this scope conftest.cc:21: error: `i' was not declared in this scope conftest.cc:22: error: initializer list being treated as compound expression conftest.cc:22: error: syntax error before `char' conftest.cc:24: error: syntax error before `{' token conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:21: error: `p' was not declared in this scope conftest.cc:21: error: `i' was not declared in this scope conftest.cc:22: error: initializer list being treated as compound expression conftest.cc:22: error: syntax error before `char' conftest.cc:24: error: syntax error before `{' token conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:21: error: `p' was not declared in this scope conftest.cc:21: error: `i' was not declared in this scope conftest.cc:22: error: initializer list being treated as compound expression conftest.cc:22: error: syntax error before `char' conftest.cc:24: error: syntax error before `{' token conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:47: error: cannot convert `char*' to `char*(*)(char**, int)' for argument `1' to `char* f(char*(*)(char**, int), char**, ...)' conftest.cc:54: error: nonnull argument with out-of-range operand number (arg 1, operand 2) conftest.cc:48: error: `big' undeclared (first use this function) conftest.cc:48: error: (Each undeclared identifier is reported only once for each function it appears in.) conftest.cc:48: error: syntax error before `;' token configure:25101: error: --enable-lcms was specified, but appropriate LittleCms development packages could not be found == Warnings == cc1: warning: "-fno-rtti" is valid for C++ but not for C/ObjC == Environment Summary == ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

Announcing the 2006 Summer of Code Projects
by Bryce Harrington 25 May '06

25 May '06

Hi all! Today was the final day for the Google Summer of Code proposal rankings. As you can imagine, a number of us inkscaper's have been in deep, intensive discussions and votes to arrive at the final prioritization. The final decision of which 4 to select was extremely difficult, and really came down to the wire. A large part of the controversy was whether to have both of the SVG filter projects in the top 4, or to go with 4 distinct projects. But just then, in an amazing stroke of luck, Google was kind enough to allocate an additional project to Inkscape, increasing us to 5 slots! :-) Thus, our final project selection is as follows: Application Student Mentor ---------------------------------------------------------------------- SVG Filter Effects #1 Niko Kiirala Bulia Inkboard Protocol Spec / Lib Conversion Dale Harvey David Yip PDF Export with Cairo Mikos Erdelyi Ted Gould Memory Optimization Marina Diezler MenTaLguY SVG Filter Effects #2 Hugo Rodrigues Bulia As I understand it, one of the SVG filter projects will be focused on the internal handling of filters at the SPObject level, the other will be focused on the rendering of the filters. Thank you to everyone who applied this year. There were a number of excellent projects, and arriving at the final selection was extremely tough. Many of the proposed ideas were extremely cool and we would love to see them developed, and would love to be able to welcome the applicants to be part of the Inkscape community. Many criteria went into our final decision, more than can be easily related. However, one of the driving considerations was for work we felt would maximize the benefit to Inkscape users. We know from user feedback that these projects, if completed successfully, will have a transformational effect on Inkscape as an application - by the end of this summer, Inkscape will likely be a light-year ahead of where it is today. Bryce

5 4

Effects documentation
by Justin Wikinator 24 May '06

24 May '06

I would like to see some basic documentation for every effect in Inkscape telling: - what state Inkscape must be in for the effect to be successful - how the effect responds to errors - what changes to the document result from the effect - dependencies of the effect (language, additional libraries) A wiki seems like it's a good place to start for this documentation. Someone has already started a page for this here: http://wiki.inkscape.org/wiki/index.php/WhatEffectsDo, and I have added one more example. I was going to attempt this on my own, but I thought I'd do a callout to the developers first because they know what their effects do better than I do, and when I was effects code on the SVN some of it wasn't documented much. Thanks for effecting, --Justin

3 2