On 10/27/06, Robert Miller <[EMAIL PROTECTED]> wrote:
Yes, that is true. All the primitives defined for SAGE Graphics are in plot.py.
If a developer wanted to add new primitives she would directly add it to plot.py.
Those new primitives would build on *primitives inside of matplotlib* because after
all thats how the whole thing works.
(one could conceive of allowing both rendering engines, Tachyon and matplotlib,
plot all primitives, but thats not implemented as of now)
What you have from networkX is a bunch of *matplotlib primitives*, which will reside
happily on the same "Figure" as the SAGE "primitives".
To make them live perfectly happily together :)
(user interface and axes issues are what I can think of now)
is what needs to be done.
-Alex
I'm not trying to add a matplotlib primitive, exactly. I'm defining a
new type of primitive, GraphicPrimitive_NetworkXGraph. The user
doesn't need to use this primitive, but it's an intermediate step for
me in constructing a graphics object that will display a graph
properly. It would be good for Graphics to accept matplotlib
primitives too, but that's not quite what I'm trying to do.
What I'm saying is that the Graphics class isn't currently written to
allow expansion: The way the class is now, unless I use a hack like
below, I can't define my own primitives. This means that any developer
wanting to use the Graphics package as it stands can only use circles,
lines, polygons etc. as already defined.
Yes, that is true. All the primitives defined for SAGE Graphics are in plot.py.
If a developer wanted to add new primitives she would directly add it to plot.py.
Those new primitives would build on *primitives inside of matplotlib* because after
all thats how the whole thing works.
(one could conceive of allowing both rendering engines, Tachyon and matplotlib,
plot all primitives, but thats not implemented as of now)
What you have from networkX is a bunch of *matplotlib primitives*, which will reside
happily on the same "Figure" as the SAGE "primitives".
To make them live perfectly happily together :)
(user interface and axes issues are what I can think of now)
is what needs to be done.
-Alex
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
