- Inkscape Devel - Inkscape Mailman

Proposal for 0.39 freeze
by Bryce Harrington 11 Jul '04

11 Jul '04

It feels like things are getting close to being ready for a freeze, and to start preparing for the release. There's a lot of work still going on, and we don't want to interrupt things abruptly, so it may be worthwhile to settle on some loose target dates. How does the following plan sound? 1. 'Feature chill' - June 28. No new features should be started, work should be wrapping up on existing features and code cleanup. Unfinished features should be hidden. Focus should be on bug fixing. 2. 'Feature freeze' - Sometime in first week of July. Only bug fixing should occur after this point. Focus should be on closing critical bugs and bugs in new features. 3. 'Hard freeze' - When all major bugs have been closed that we intend to close, we go into a short hard freeze period for a few days where no changes are allowed except under strict change control. We do final QA, verify on as many platforms as possible, create the packages and verify they work well, and make sure no last minute bugs slipped in. 4. 'Release' Bryce

12 28

Update on release process
by Bryce Harrington 11 Jul '04

11 Jul '04

There are still a few remaining Must-Fix items prior to going into the Hard Freeze, so we'll be giving it a bit more time. Hopefully by the end of the weekend we'll be ready. Tomorrow morning, I will send out a proposal for how to conduct the Hard Freeze segment of the release process. Bryce

1 0

Check ReleaseNotes
by Bryce Harrington 11 Jul '04

11 Jul '04

Just as a reminder, everyone who has done work on the codebase between 0.38.1 and now, please go review the ReleaseNotes and doublecheck that those changes are accounted for. Minor bug fixes, optimizations, etc. can be omitted, but it's worthwhile to include anything major, both for educating users about the new stuff, and for testing/troubleshooting purposes. http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes Thanks, Bryce

4 4

libccc: criawips' cairo-based canvas (using gtkcairo)
by Sven Herzberg 10 Jul '04

10 Jul '04

Hi all, I just started to play around with gtkcairo because I got stuck with some limitations of the gnome-canvas that I hope to be able to solve when developing a cairo based canvas. My current aims are: * get a high level canvas using cairo * get rid of issues like we have in gnome-canvas (e.g. text cannot zoom) * have a gnome-canvas-like api * use gobject interfaces for some things and lots of signals to make extending more easy (e.g. 'zoom canged' signal would have helped to fix the GnomeCanvasText things) I'm playing around within the criawips CVS repository on cvs.gnome.org. There's neither something that works yet nor much stuff, I just want to tell you about my plan to be able to get feedback before I introduce some issues that you had with something similar. The code is located in the criawips/src directory and consists of the cc-* files. Regards, Sven PS: I hate cross-postings, please continue this thread within criawips-devel@...448... and DO NOT reply to other lists. Thank you -- Sven Herzberg <herzi@...449...> · GNOME Deutschland <www.gnome-de.org> Jabber <herzi@...450...> · ICQ <177176642> GnuPG Fingerprint: <F020 B158 2696 6D6A 2870 F53C 0565 FD6B B1C3 0AFE>

1 0

export to bitmap: very bad behaviour
by Artemio 10 Jul '04

10 Jul '04

Hello all! I noticed several changes in the recent snapshot (20040706) that make my work much slower. 1. The exported image name defaults to drawing.svg.png instead of drawing.png. What is this for? Generally, you'll want shorted and simpler names, just drawing.png. Currently I have to delete the .svg portion each time. 2. The behaviour of the export dialogue is inconvenient. One thing it should be able to do IMHO is to detect whether a selection is active and automatically set the export mode to selection. 3. Also, compared to a snapshot of 20040628, Inkscape forgot how to update the export x/y/size on the fly. For example, I have three drawings on a single canvas and I want them exported to drawing[123].png. Previously, I could fire up the export dialogue, and hit export three times while selecting different drawings and changing 1 to 2 and then 2 to 3 in the target file name. In the current snapshot, if I change a selection while the export dialogue is up, the selection range is not updated. So if I want to do what I explained, I have to select a drawing, then hit "selection", then adjust the file name and hit export. This adds one exrta action which makes you work longer. I think the export x/y range should update on the fly. Just my 2 cents ;-) Artemio.

4 3

Working locally
by Gazal, Geraud (MED) 09 Jul '04

09 Jul '04

As my home internet connection is not up at the moment, I was wondering if there was a way for easily downloading the complete list of RFEs and Bugs in order to be able to read/sort it locally... Anyone having already done this ?

4 4

Updated spanish po
by Lucas Vieites 09 Jul '04

09 Jul '04

Hi, attaching updated spanish po. Will there be a 'translation freeze' before the 0.39 release so we can have translation at 100%? And now for something completely different: I found at least two strings containing "sodipodi" in the po file. Is this correct? msgid "Could not create sodipodi-svg-doc factory" msgid "Export document to plain SVG file (no sodipodi or inkscape namespaces)" -- Lucas 'Basurero' Vieites Dept. Desarrollo <lucas@...212...> Asix Informática <http://www.asixinformatica.com/> Tel/Fax: +34 986 54 26 98

4 3

AW: [Inkscape-devel] isnan
by Taraben, Adib 09 Jul '04

09 Jul '04

>> isnan without the std:: qualifier doesn't compile for me on mingw gcc >> 3.2.3. Are we going to need a platform-specific hack here? > Same for me (cross-compiling). Is there a way to change is so that > everyone is happy? using namespace std ??? Adib.

5 5

autopackage now requires explicit --enable-binreloc
by Peter Moulder 09 Jul '04

09 Jul '04

The autopackage code has the following problems: - The code for enable-binreloc=auto (which was previously the default) checked the build environment rather than the execution environment. - autopackage code prevents running inkscape from the build directory. (This problem is reduced if the source directory and the build directory are the same.) It should fall back to using the configure-supplied PREFIX value. - Also, there are a few problems with prefix.cpp code that make me wonder what other problems the autopackage code has: - br_locate uses sscanf("%x-%x") and unsigned ints whereas linux/fs/proc/array.c uses printf("%08lx-%08lx") and unsigned longs. This presumably leads to bugs on 64-bit platforms. - br_prepend_prefix needlessly requires that its path argument be writable. - br_strcat uses calloc, only to write over the space. It in effect calculates strlen(str1) 3 times and strlen(str2) twice. - br_strndup has buffer overflow if size excedes the length of str by more than one. - br_extract_prefix doesn't behave as its documentation indicates. Also it does an unnecessary strndup when it could use memrchr. Therefore I've changed configure.in to default to enable-binreloc=no. Autopackage binary builders, you may wish to add --enable-binreloc to your configure options. pjrm.

2 1

"layers"
by MenTaLguY 09 Jul '04

09 Jul '04

I think I've fixed most of the layer-related bugs I could find now. If you guys could give the "Edit group" feature a workout and see if there's anything I missed... (I think I still need to add transformation compenstation to Paste, at least) -mental

3 2