February 2006 - Inkscape Devel

Re: [Inkscape-user] Autopackage: dependence on libcairo.so.2
by Bryce Harrington 28 Feb '06

28 Feb '06

Has the Cairoification begun? :-) Looks like some Autopackage updates are needed... On Mon, Feb 27, 2006 at 04:24:14PM +0100, Norbert Nemec wrote: > Hi there, > > I'm usually working at a workstation at university which is centrally > administered, so I'm really thankful for the Inkscape autopackages that > allow me to use the development version without much installation hassle. > > However the latest autopackage 20062270113 seems to depend on > libcairo.so.2 which is not installed. > > Our machines contain a nearly clean and fairly complete Debian stable, > so I think this dependence should generally be avoided in the autopackage. > > Thanks in advance, > Norbert Nemec > > -- > -----------------------------------------------------> Norbert Nemec > Molecular Computing Group ... Institute for Theoretical Physics > University of Regensburg ... D-93040 Regensburg > phone: +49-(0)941-943-2026 ... mobile: +49-(0)179-7475199 > eMail: <Norbert.Nemec@...1195...> ... room: Phy 4.1.30 > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Inkscape-user mailing list > Inkscape-user(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-user

3 3

PayPal Security Measures
by PayPal 25 Feb '06

25 Feb '06

1 0

Re: [Inkscape-cvs] SF.net SVN Commit: inkscape: [10939] including typecheck trying to prevent #1432680
by unknown＠example.com 25 Feb '06

25 Feb '06

http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/trunk/src/ui/dialo… Hmm, I don't think that typecheck is the best way to address the bug. It's just papering over the real problem... If the problem is that you're sometimes getting a (non-NULL) garbage pointer in dlgPtr, that has to be fixed upstream. It's probably a source of other bugs too. Besides, a typecheck here would only catch a garbage pointer most of the time. Occasionally, the arbitrary data being pointed to will have the right bit pattern... -mental

3 5

Subversion beta completed
by Bob Jamison 24 Feb '06

24 Feb '06

Hi, all, It looks like Subversion is now available to everyone at Sourceforge.net. Here is the notice. I bet that the guys at subversion.tigris.org are partying, now they have passed this 'tipping point.' bob

1 0

[root@...1070...: [Inkscape-tester] inkscape build report]
by Bryce Harrington 22 Feb '06

22 Feb '06

Nice work, down to 10 warnings. :-) Bryce ----- Forwarded message from root <root@...1070...> ----- Date: Tue, 21 Feb 2006 17:21:08 -0800 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Tue Feb 21 17:16:03 2006 (Run 1212) Snapshot: inkscape-20060221-1600.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 10 0 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == none == Warnings == sp-flowtext.cpp:324: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-item.cpp:729: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.cpp:718) sp-shape.cpp:611: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-text.cpp:472: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:638: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:717: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) display/canvas-arena.cpp:85: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:85: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:132: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:132: warning: (perhaps the `offsetof' macro was used incorrectly) == Environment Summary == ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&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

Message From eBay Member
by eBay 22 Feb '06

22 Feb '06

1 0

flattening transparency
by Aaron Spike 21 Feb '06

21 Feb '06

I've been trying to educate myself about our printing problem by exploring cairo, librsvg, the uberconvertor and pdf in general. I stumbled across this document entitled, "Achieving Reliable Print Output from Adobe Applications when Using Transparency." http://partners.adobe.com/public/asn/en/print_resource_center/TXPGuide.pdf It seems to me that most all of the functionality needed for flattening out transparency already exists in Inkscape. A rather brute force method could be: 1) Replace all strokes with paths 2) Decompose all overlapping objects (this would be an additional boolean op, and it has been requested twice in my recent memory) 3) Replace all area's of overlapping transparency with a bitmap copy. 4) Replace all non overlapping transparency with the resultant color. Further optimizations would of course be possible. My exploration of cairo and librsvg has only been very casual, but I can't imagine that either of them will be well suited to this sort of decomposition task. But maybe with all of the recent excitement and advancement around vectors a good LGPL computational geometry library will pop up. Aaron Spike

5 6

[inkscape build report]
by Bryce Harrington 21 Feb '06

21 Feb '06

>From 20 yesterday to 16 today ----- Forwarded message from root <root@...1070...> ----- Date: Tue, 21 Feb 2006 05:21:12 -0800 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Tue Feb 21 04:54:40 2006 (Run 1199) Snapshot: inkscape-20060221-0300.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 16 0 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == none == Warnings == sp-flowtext.cpp:324: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-item.cpp:729: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.cpp:718) sp-shape.cpp:611: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-text.cpp:472: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:638: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:717: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) display/canvas-arena.cpp:85: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:85: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:132: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:132: warning: (perhaps the `offsetof' macro was used incorrectly) removeoverlap/pairingheap/PairingHeap.h:47: warning: friend declaration `std::ostream& operator<<(std::ostream&, const PairingHeap<T>&)' declares a non-template function removeoverlap/pairingheap/PairingHeap.h:47: warning: (if this is not what you intended, make sure the function template has already been declared and add <> after the function name here) -Wno-non-template-friend disables this warning removeoverlap/pairingheap/PairingHeap.h:68: warning: friend declaration `std::ostream& operator<<(std::ostream&, const PairingHeap<T>&)' declares a non-template function removeoverlap/pairingheap/PairingHeap.h:47: warning: friend declaration `std::ostream& operator<<(std::ostream&, const PairingHeap<T>&)' declares a non-template function removeoverlap/pairingheap/PairingHeap.h:47: warning: (if this is not what you intended, make sure the function template has already been declared and add <> after the function name here) -Wno-non-template-friend disables this warning removeoverlap/pairingheap/PairingHeap.h:68: warning: friend declaration `std::ostream& operator<<(std::ostream&, const PairingHeap<T>&)' declares a non-template function == Environment Summary == ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&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

Private Use Area
by Jon A. Cruz 21 Feb '06

21 Feb '06

On Feb 20, 2006, at 5:19 PM, bulia byak wrote: > On 2/20/06, Jon A. Cruz <jon@...18...> wrote: >> For that entry problem, go ahead and file a bug report that >> Inkscape's input does not allow private use area characters to be >> entered. That, at least, can be fixed in Inkscape's code. > > Maybe it can, but it's not the right way to do it. We use a library > function to check whether a character is printable, so the right way > is to raise this issue with the library maintainers. No, I actually checked into this. The library is doing the right thing. In and of itself, any private use character could be printable or non- printable, and is not covered by the specs or such functions. If our application can deal with the Private Use Area (which I've verified we do), all we need to do is check for it. g_unichar_validate () then g_unichar_type(..) == G_UNICODE_PRIVATE_USE will take care of things the right way. Aside from other issues, this makes Inkscape's input behavior consistent with other systems, including the built-in OS X method. (Tricky to find, but easy to use once it's checked). Of course, this led me to wonder if we might want to warn upon insertion of a Private Use Area character. I'm attaching a quick sample that shows the use of two private area characters (the second being the Apple glyph). This is happy-happy for me here in Inkscape and FireFox.

2 1

inkscape build report
by Bryce Harrington 21 Feb '06

21 Feb '06

Some warnings on hidden virtual functions, deprecated functions, and template issues. (Btw, the test harness has been offline for a while - it had just run out of disk space. I cleared space, so it should be good for another month or so.) Bryce ----- Forwarded message from root <root@...1070...> ----- Date: Mon, 20 Feb 2006 17:21:08 -0800 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Mon Feb 20 17:10:37 2006 (Run 1188) Snapshot: inkscape-20060220-1600.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 20 0 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == none == Warnings == sp-flowtext.cpp:324: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-item.cpp:729: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.cpp:718) sp-shape.cpp:611: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-text.cpp:472: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:638: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:717: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) display/canvas-arena.cpp:85: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:85: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:132: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:132: warning: (perhaps the `offsetof' macro was used incorrectly) ui/dialog/dialog.h:37: warning: `virtual void Inkscape::UI::Dialog::Dialog::present()' was hidden ui/dialog/transformation.h:151: warning: by `void Inkscape::UI::Dialog::Transformation::present(Inkscape::UI::Dialog::Transformation::PageType)' ui/dialog/dialog.h:37: warning: `virtual void Inkscape::UI::Dialog::Dialog::present()' was hidden ui/dialog/transformation.h:151: warning: by `void Inkscape::UI::Dialog::Transformation::present(Inkscape::UI::Dialog::Transformation::PageType)' removeoverlap/pairingheap/PairingHeap.h:47: warning: friend declaration `std::ostream& operator<<(std::ostream&, const PairingHeap<T>&)' declares a non-template function removeoverlap/pairingheap/PairingHeap.h:47: warning: (if this is not what you intended, make sure the function template has already been declared and add <> after the function name here) -Wno-non-template-friend disables this warning removeoverlap/pairingheap/PairingHeap.h:68: warning: friend declaration `std::ostream& operator<<(std::ostream&, const PairingHeap<T>&)' declares a non-template function removeoverlap/pairingheap/PairingHeap.h:47: warning: friend declaration `std::ostream& operator<<(std::ostream&, const PairingHeap<T>&)' declares a non-template function removeoverlap/pairingheap/PairingHeap.h:47: warning: (if this is not what you intended, make sure the function template has already been declared and add <> after the function name here) -Wno-non-template-friend disables this warning removeoverlap/pairingheap/PairingHeap.h:68: warning: friend declaration `std::ostream& operator<<(std::ostream&, const PairingHeap<T>&)' declares a non-template function == Environment Summary == ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&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