
Has anyone looked into using AGG (http://www.antigrain.com) as the low level back-end? AGG itself seems very low-level in some places, which might cause problems but it seems very functional. I searched this list and found another reference that said it might be good for being able to add the SVG filter support. Personally, I would love to finally have that functionality.
I made a real quick look at the code and it looked nice and seems flexible.
In my limited testing I found that it was extremely fast.
It doesn't have much in the way of SVG support though. There is an example SVG viewer but barely has any functionality. I suppose Inkscape would just keep its current SVG stuff anyway.
I was just wondering if anyone had looked into it and if they found any serious issues. I assume Inkscape switched from librsvg to livarot for some good reason and I'm just wondering if AGG was a consideration.

On Mon, 10 Jan 2005, Chris wrote:
Date: Mon, 10 Jan 2005 11:38:05 -0500 From: Chris <radical@...78...> To: inkscape-devel@lists.sourceforge.net Subject: [Inkscape-devel] AGG backend?
Has anyone looked into using AGG (http://www.antigrain.com) as the low level back-end? AGG itself seems very low-level in some places, which might cause problems but it seems very functional. I searched this list and found another reference that said it might be good for being able to
When you have gone to the trouble of finding references please try to include links to them so others do not have to try and find them all over again
add the SVG filter support. Personally, I would love to finally have that functionality.
I made a real quick look at the code and it looked nice and seems flexible.
In my limited testing I found that it was extremely fast.
It doesn't have much in the way of SVG support though. There is an example SVG viewer but barely has any functionality. I suppose Inkscape would just keep its current SVG stuff anyway.
I was just wondering if anyone had looked into it and if they found any serious issues. I assume Inkscape switched from librsvg to livarot for some good reason and I'm just wondering if AGG was a consideration.
I'm pretty sure Inkscape (and Sodipodi) never used librsvg.
I haven't heard Antigrain Geometry (AGG) mentioned before (at least not on the Inkscape lists) but you suggest it has come up already so perhaps it was only mentioned briefly and now that you have mentioned it developers will take another look at it.
Sincerely
Alan Horkan http://advogato.org/person/AlanHorkan/
Sincerely Inkscape, Draw Freely http://inkscape.org Abiword is Awesome http://abisource.com

On Mon, 2005-01-10 at 19:10 +0000, Alan Horkan wrote:
When you have gone to the trouble of finding references please try to include links to them so others do not have to try and find them all over again
Sorry, it was a couple of days ago and I'm not sure where I saw it. There wasn't any discussion of AGG in that thread. Someone just made an off-hand comment in the midst of a bunch of other stuff about AGG making future filter support easier but that was it.
However, while searching for that reference I found this: http://sourceforge.net/mailarchive/message.php?msg_id=8193141
AGG is not used by Cairo though.
I don't know about the license problem that was mentioned. As far as I know AGG is using a BSD-like free license.
Nothing more was ever mentioned. I wonder if some issue was discovered, or maybe the idea was just forgotten.
I'm pretty sure Inkscape (and Sodipodi) never used librsvg.
I haven't heard Antigrain Geometry (AGG) mentioned before (at least not on the Inkscape lists) but you suggest it has come up already so perhaps it was only mentioned briefly and now that you have mentioned it developers will take another look at it.
OK. I thought Sodipodi used librsvg and at some point Inkscape changed to livarot.

On Mon, 10 Jan 2005, Chris wrote:
I don't know about the license problem that was mentioned. As far as I know AGG is using a BSD-like free license.
At the time we were primarily in the market for a library to do various path operations (e.g. boolean union, etc), which is handled by the GPC portion of AGG. Although the overall AGG license is GPL-compatible, the GPC license is not.
OK. I thought Sodipodi used librsvg and at some point Inkscape changed to livarot.
Originally Sodipodi used libart as its renderer, and then Lauris wrote his own renderer. After that, Inkscape forked and we brought in livarot to do boolean operations on paths, but not rendering at first.
We eventually found Lauris' renderer to be unmaintainable, and pressed livarot into service as a renderer too. It has its own problems though.
In principle I don't think I'd object to using the non-GPC portion of AGG for interactive rendering. I would certainly eventually like to offer a renderer based on it as a choice for bitmap export.
The only downside in terms of capabilities is maybe the lack of hardware acceleration (versus Cairo), and that AGG isn't a "finished" graphics API -- it just gives you a lot of tools with which to roll your own.
-mental

On Mon, 10 Jan 2005, Chris wrote:
On Mon, 2005-01-10 at 19:10 +0000, Alan Horkan wrote:
I'm pretty sure Inkscape (and Sodipodi) never used librsvg.
Ah, I believe I was confusing libart and librsvg. Sodipodi/Inkscape used libart then Inkscape switched to livarot. Right?
Yup, that's right.
Bryce
participants (4)
-
Alan Horkan
-
Bryce Harrington
-
Chris
-
MenTaLguY