[GiNaC-devel] AsyForGiNaC - an output extension producing Asymptote files

[Jens Vollinga]

Dear Vladimir,

Vladimir Kisil schrieb:
> 		Dear Jens,
> 
>>>>>> "JV" == Jens Vollinga <vollinga at physik.uni-wuppertal.de> writes:
> 
>     JV> GiNaC is mainly about algebra with some (large) admixture of
>     JV> numerics. 
> 
> 	Some people like algebraic expressions to be visualised,
>   e.g. gTubalt enriches GiNaC by drawing facilities from Root and
>   everyone seems to like it. 

agreed! The only concern I've expressed is whether to have this drawing 
facility be part of the GiNaC classes or not.

>     JV> And I don't like the idea of having classes that
>     JV> sport say 10 methods for the usual GiNaC stuff and then 10
>     JV> additional methods just for drawing
> 
> 	The idea is to add one more printing context "asy" to the "text",
>   "latex", "python", etc. family.

Ah, that is something I was not aware of. I thought that there should be 
draw, draw_like_this, draw_the_other_way methods added to the classes. 
So, is it just a new printing context?

>     JV> most cases). It is (almost) always like "draw(Object, Numerical
>     JV> Range, XYZ Spec)". 
> 
> 	Note that here "Numerical Range" and  "XYZ Spec" are properties of
>   the scene, not of "Object". Thus there is no need to store all drawing
>   option in the Object. Rather you may prepare an Asymptote scene with
>   required properties and then ask one or several GiNaC objects
>   "print_asy" themselves on this scene.

So, this preparation is done in some global object and later when the 
GiNaC objects are asked to print themselves they in turn ask (in case 
the asy printing context is used) this object for certain properties? Is 
this the plan, roughly?

>   A beautiful drawing is always uneasy and will require a lot of
>   customisation. However it will nice if GiNaC will have at least basic
>   possibility to draw a graph of function. It became even more true with
>   development of several interactive wrappers.

True.

Regards,
Jens