- Inkscape Devel - Inkscape Mailman

Compile warnings
by Jon A. Cruz 01 Mar '04

01 Mar '04

I just did a rebuild after updating to the new layout. When I did, it came up with 805 warnings. Eeeek!!!! Guys, when you have a chance, see if you have -Wall configured and try to get to zero warnings. I know a lot of more verbose ones have come up recently, especially with our changes to C++ and such. So I am being a bit of a complainer here. :-) But... on projects I've seen where warnings were kept out, quality came up. So though I expect zero-warnings may not be hit any time soon, keeping that in mind as a goal will help our code be better. Thanks.

2 1

9. Extract SVG Canvas into a library 0.43
by Charles Goodwin 01 Mar '04

01 Mar '04

>From the roadmap overview: (http://www.inkscape.org/roadmap.php) 6. Create Plugin Architecture 0.40 * This architectural change will establish a new mechanism for how features are added and maintained in the codebase. 7. New Features 0.41 * Implement snap-to object, enhanced layer support, and boolean operations. 8. STL Architectural Change 0.42 * Shift codebase to using STL for data structures. * Replace use of #defines and enums with hashmap lookups 9. Extract SVG Canvas into a library 0.43 Obviously I'm massively ignorant of the issues involved, but from what I can see milestones 6 and 7 are relatively independent of 6 and 9. >From a GO perspective, it would absolutely brilliant if you could bring milestone 9 into milestone 6, the point at which you might start using libgoffice for the plugin handling. (And I personally hope you do because it will help make goffice more functional, featureful, and robust as well as give Jody a bit of help.) The reason I bring this up is that the sooner the Inkscape SVG canvas is available, the sooner other applications (esp. GO apps) can organise themselves around incorporating it. -- - Charlie Charles Goodwin <charlie@...208...> Online @ http://www.charlietech.com

5 4

scrolling weirdness
by Jonathan Phillips 29 Feb '04

29 Feb '04

Bulia or anyone else, When I scroll use the vertical scrollbar everything is very smooth and the canvas is not smeared, but when I use my scrollbar mouse, the canvas is smeared in the update. This is especially true when looking at the tutorial. Can someone else verify this. Although this is not a bug, it is kinda weird updating of the canvas. Anyway...it becomes cumbersome to use the scroll mouse to move around with these weird updates, as you can't see exactly where you are heading. It would be nice if a similar update method was used as is with the vertical scrollbar wheel. NOTE: I have not looked at the code for thi. Jon -- Jonathan Phillips <jon@...15...>

1 0

Reminder on IRC Scribus and Inkscape or Inkscape and Scribus ;)
by Peter Linnell 29 Feb '04

29 Feb '04

Hi all, To clarify: IRC meet at #scribus on freenode.net 07:00 CET Sat 28 Jan. = 1 AM EST or 10 PM PST. Fri. PM Please review the notes at: http://www.inkscape.org/cgi-bin/wiki.pl?ScribusInteroperability Thanks and look forward to this. Peter

5 10

Re: [Inkscape-devel] xft font fixes
by bulia byak 29 Feb '04

29 Feb '04

>This is probably unrelated, but I am getting a segfault on nr-type-w32.cpp Hi Bob, this is now fixed, fonts work again on win32 at least as they used to (plus with styles sorted in the list). However when I tried to make it correctly display Cyrillic font names, I found that g_locale_to_utf8() does not work (even though g_locale returns the correct locale, CP1251). The error returned by the conversion function says "Error during conversion: no such file or directory" (code 2), which suggests that it requires some external module or table which is not included with your GTK or Glib files. Could you please check this, and add anything necessary for conversion functions to work? _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/photos&pgmarket=en-ca&RU=http%3a%2f%2fjo…

3 2

Re: [Inkscape-devel] inverse handles
by bulia byak 28 Feb '04

28 Feb '04

>Just to clarify, "as they used to" refers just to the final visual result >if the background is white, it doesn't mean using semi-transparency: >just as currently we don't do "pure" inversion (especially when the >background is near 50% grey), we can similarly tweak the function >to give a given image as the background approaches white. OK, now the function is (in helper/sodipodi-ctrl.cpp): #define COMPOSE_X(b,f,a) ( ( ((guchar) b) * ((guchar) (0xff - a)) + ((guchar) ((b ^ ~f) + b/4 - (b>127? 63 : 0))) * ((guchar) a) ) / 0xff ) where b is background, f is foreground, a is alpha. Propose your own and we'll compare. >which the default style is decidedly bad. E.g. inversion is bad for >very noisy background: inverting noise is still noise. The goal of the handle is not to turn noise into non-noise. Its main goal is to be visible. With inversion, it fails to be visible only when it overlays an object which is a copy of the handle, i.e. has inverse color relative to the surroundings and has the same shape. The probability of this is close to zero. Any other noise is not an obstacle to it being visible with inversion. _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoi…

3 2

IRC Logs
by Peter Linnell 28 Feb '04

28 Feb '04

Hi all, First, I think it is fair to say it was a very promising start at cooperation and many many good things will come from this in the future. For those unable to attend or had connection problems, I have posted the log (60k) at: http://www.atlantictechsolutions.com/inkscape/28022004.log Cheers, Peter

1 0

Re: [Inkscape-devel] further font problems
by bulia byak 28 Feb '04

28 Feb '04

>however when I skimmed it a little while back I recall noticing that there >were many problems with font info getting collapsed to simple strings when >there were more details in the info available. Yes, simply because CSS requires such collapsing. That's the point. Jon: Do you know if there's any progress with bug 866197, "problems with non-ascii filenames"? There was some activity in file-related areas recently, but I'm not up to date on the current status. _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

1 0

further font problems
by bulia byak 28 Feb '04

28 Feb '04

Now that Inkscape can see all font styles, futher problems emerge. The biggest problem is that SVG uses CSS, and the premise of CSS is different from that of a design app. CSS was designed to get "as close as possible" font rendition on a wide variety of platforms. The goal of a design app is to render the font _exactly_ so long as it is available on the system. The font selection properties used by CSS include family, style, weight, variant, and stretch. Each property has a fixed limited set of values: http://www.w3.org/TR/SVG11/text.html#FontPropertiesUsedBySVG Of these, currently supported by Inkscape (to some extent) are only style (italic or normal) and weight. However, even if all these properties are fully supported, Inkscape _would still be unable to reproduce some fonts_. Take a look at the list of fonts in the Caslon family here: https://sourceforge.net/tracker/index.php?func=detail&aid=904962&group_id=9… It has many variants that CSS simply cannot handle: Swash, Alternates, Old style figures, Expert, etc. I think it is unacceptable for Inkscape to ignore any fonts simply because CSS cannot describe them appropriately. So, I think the only acceptable (although unelegant) solution is to introduce a two-tier font specification. Namely, I propose to introduce <text> attributes inkscape:font-family inkscape:font-style that will hold the family and style exactly as reported by the OS, without attempting to parse them into weight, stretch etc. These will have precedence over CSS in Inkscape and will allow it to reliably use any installed fonts. For non-Inkscape renderings, the CSS specification will work as before (although it probably needs to be improved to handle more of the CSS properties and values). Comments? _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

2 1

Re: [Inkscape-devel] RE: yet another patch
by bulia byak 28 Feb '04

28 Feb '04

Thanks a lot, I committed your patch. We're excited about it because the old rasterizer was a sore spot, it was buggy and so cryptic that no one could really debug it. Your code is much easier to understand and improve. I hope we'll be able to optimize and further develop it. P.S. Let me know if you want CVS write access again. >From: fred <yafoyah@...48...> >To: bulia byak <archiver_1@...19...> >Subject: Re: [Inkscape-devel] RE: yet another patch >Date: Sat, 28 Feb 2004 00:54:36 +0100 (CET) > >a little modification that will make rasterization a >tad faster on some shapes (but not all). >the bug you have i cannot reproduce (same zoom same >file doesn't exhibit any problem), nor guess where it >comes from, sorry... > > > > > >Vous manquez despace pour stocker vos mails ? >Yahoo! Mail : 6 Mo gratuits ! >Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ > >Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez >Yahoo! Messenger sur http://fr.messenger.yahoo.com ><< modif.tar.gz >> _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

1 0