- Inkscape Devel - Inkscape Mailman

Inkscape Project Status 2004-03-15
by Bryce Harrington 16 Mar '04

16 Mar '04

The bug hunt has been rumbling along. Easy bugs are getting knocked out left and right, harder ones are being tackled through concerted teamwork. It's taken quite a bit of time to get to this point, but finally we can see the light at the end of the tunnel. Special thanks to all users who have taken the time to identify and report bugs; we've uncovered and solved a large number of issues that we never would have caught ourselves. Thanks is also due to the team of developers tackling these bugs, especially the new developers using the bug hunt as a good way to get involved with the codebase. Tonight a user popped onto Jabber to share what he's using Inkscape for - to make the text bubbles for his comics! http://www.cybersewer.com/comics/16 Statistics Nov 15 Dec 15 Jan 15 Feb 15 Mar 15 ========== ====== ====== ====== ====== ====== Lifetime Rank on SourceForge: 4391 2452 1928 1599 * (68.5%) (82.4%) (86.1%) (88.6%) * Max Week's Rank on SourceForge: 62 27 321 70 * (99.6%) (99.8%) (97.5%) (99.5%) * Total SF Page Views * 86,000 126,500 200,000 * Total SF Downloads * 3640 5,735 10,000 * Total Freshmeat URL Hits 746 2237 2,958 3,437 4,670 Total Freshmeat Subscriptions 16 28 33 35 50 Lines of Code in src/: 115,901 132,134 166,914 167,386 177,286 Code lines 100,549 133,150 131,540 138,457 Comment line 11,591 12,468 12,995 15,584 Blank 20,559 21,929 23,513 24,061 Lines of Docs in doc/: 1,135 2,225 3,000 4,500 4,434 Lines of content in website: 1,173 2,090 2,885 4,300 5,087 Size of the Inkscape wiki: 3,700 7,385 11,284 13,114 14,840 Minutes since last ChangeLog mod: 360 1260 6 2 0 Bugs open/total: 9/15 67/111 74/160 53/178 43/244 Features open/total: 18/18 40/45 104/120 120/137 151/184 Patches open/total: 1/ 6 6/25 4/32 2/ 35 6/ 45 CVS Commits (as per inkscape-cvs): 481 * * 2796 3070 Inkscape-devel membership: 49 64 64 63 75 Inkscape-announce membership: 9 16 22 26 35 Inkscape-user membership: 0 21 38 * - Statistics unavailable

1 0

Updated RPMS
by Peter Linnell 16 Mar '04

16 Mar '04

Hi all, I have uploaded updated SuSE and FC-1 rpms for Inkscape, which have some minor spec file tweaks. The first QA review from Fedora QA was pretty positive. So, getting Inkscape into the Fedora stable repository should happen as soon as it is further QA'd. The 0.38 release notes have a section I added on Build Requires. Can someone give that a good look over to make sure the versions are correct? Cheers, Peter

1 0

is Python scripting supported yet?
by Kevin Altis 15 Mar '04

15 Mar '04

Is Python scripting of Inkscape supported yet? If not is it still planned? ka

2 1

RE: [Inkscape-devel] Bug 866103: non-well-formed preferences.xml causes data los
by bulia byak 15 Mar '04

15 Mar '04

>What's a good approach for dealing with this issue? Do we need to have >a validation step so that it's possible to descriminate good from bad >files? The most useful and probably easiest is to create a backup file each time preferences are written. This, combined with modal errorbox saying that the preferences failed to parse and will be replaced by defaults, will be enough to resolve this. Validation is not necessary. _________________________________________________________________ MSN Premium: Up to 11 personalized e-mail addresses and 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

1 0

Bug 866103: non-well-formed preferences.xml causes data loss
by Bryce Harrington 15 Mar '04

15 Mar '04

Summary: non-well-formed preferences.xml causes data loss Bug ID: 866103 ------------------------------------------------------------------------ 1. edit ~/.inkscape/preferences.xml so it's not well-formed (e.g. delete any > in a tag) 2. run inkscape 3. quit The file is overwritten with all the default preferences, all old data in it is lost. Expected behavior: use default values while the program is running but NOT overwrite data on quit if it was not read successfully, or at least leave a backup copy. --buliabyak Currently there's no way to discriminate between a failure to load preferences because the file did not exist yet and a failure because that file was not well-formed. -- mental ------------------------------------------------------------------------ What's a good approach for dealing with this issue? Do we need to have a validation step so that it's possible to descriminate good from bad files? This sounds like a fairly easy thing to fix once an approach is decided. Bryce

1 0

Advert: inkscape-devel@lists.sourceforge.net - Due Payment, account.
by Leased I. Clobber 14 Mar '04

14 Mar '04

1 0

re: line wrapping
by MenTaLguY 14 Mar '04

14 Mar '04

...and yes, I realize I've occasionally gone back and tweaked line wrapping myself. That doesn't mean it's a good idea (except maybe in really extreme cases, but those are better candidates for actually being rewritten). -mental

1 0

line wrapping
by MenTaLguY 14 Mar '04

14 Mar '04

While the coding standards make suggestions for how to wrap lines, I do not think line wrapping should be required. I've been getting complaints about authors who are coming back to find their code line-wrapped in ways they are not happy with. I don't mind people going back and fixing whitespace/indents/brace positioning, but I would prefer that wrapping be left alone unless you're at least also making functional changes to those lines. Otherwise it creates a lot of needless churn in the diffs, and it can't simply be ignored with -b. I also notice that our emacs modeline includes a fill-column:99 ... do we need to rethink this? I don't mind it so much if it's wrapping new code, but if it's forcibly reformatting existing code, that's not cool. -mental

1 0

Re: offset & simplify
by bulia byak 14 Mar '04

14 Mar '04

> > I suspect it's something with your code. > >indeed it is. the ConvertToShape() return 4, meaning >it fucked up the uncrossing. the path you give him is >a good example of polygons intersectors don't like: >"long" edges with lots of intersections in a small >area, and worst of all, small angles between segments. >there is also another tiny star in the svg that isn't >rendered properly for the same reasons. >i'll take a look at the problem when i have some time, >but you must realize that converting strokes to >polygons just to raster them is not a clever method. >dumbly rasterizing them segment by segment with a >supersampled antialiasing is faster (well, ought to be >faster) and much more robust to numerical problems. if >you want to get rid of rasterization bugs, i'm afraid >you'll have to get there one day. Yes, I never could fully understand why an intersector is needed in a renderer at all. This is design we inherited from Sodipodi. Do you think it's realistic to change that? How hard could that be? > > you add a check that would prevent it from doing any > > simplification on a > > subpath that contains only one node? That would stop > > it from growing > > indefinitely. I would do this myself but I only know > >here is also a big algorithmical problem: the >simplification algorithm (if you can call that an >algorithm) is not even able to recompose a single >cubic bezier curve from a polyline coming from a >single bezier curve; it will produce several cubic >curves, unless you give a very big treshhold, or >refine the fitting a lot (and it takes time). the >growth/rotate/oddities would probably not happen if >the algorithm worked properly on a single cubic curve. >before adding shortcuts to prevent degenerate cases, >it's better (IMHO) to make the simplification behave >correctly on such simple paths. I don't know, but if part of what Simplify does is adding more nodes sometimes, I'd say it's OK. The design appeal of Simplify is in its "randomness" and "generalization". The number of nodes is of secondary importance. The goal is not a mathematically perfect simplification, but one that "feels right". The current algorithm is very good in this respect, imho. _________________________________________________________________ Add photos to your messages with MSN Premium. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

2 1

Re: FFDingbests
by bulia byak 14 Mar '04

14 Mar '04

>Hmm, this is getting stranger and stranger. Despite the warning >from pfaedit, the old one did work ok for me on both Linux and >Windows; On linux, that may be caused by different verions of fontconfig, freetype, or something else. But I didn't test that font on windows. > > Can you provide another example of a valid font which Inkscape > > sees on one platform but does not see on another? > >I'll try to find one when I get back to Windows next week. OK >I never thought about it, because I always edit text using Text >and Fonts. However, if Text and Fonts is going away, this >definitely would be useful (or perhaps "must be done" if we >don't want to lose existing functionality). OK, I will look into incorporating that patch. Another related question: Can you please test the status this bug: https://sourceforge.net/tracker/index.php?func=detail&aid=850966&group_id=9… Is this still a problem with the latest CVS? If yes, can you provide any additional pointers or information? What to look for to have that fixed? _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN Premium http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

2 1