The visual examples are in test.py in the root (the file will be
deleted/moved if there is ever a version for merging)- it's meant for copy
pasting or interactive shell, so you can see how it works.
About the differences: The code in newplot is just a *simplified* interface
to whichever backend you choose (eg matplotlib, textplot, google chart api,
the current plotting module, etc). Only textplot and matplotlib backends are
present (and they are fairly simple).
The *only* advantage of using this code instead directly one of the backends
it's that you have simplified interface for all of the common tasks
(including for example coloring as a function of parameters). For
complicated stuff you can directly access the backend.
So instead of typing
x_points = range(N_points)/float(step)
y_points = [(x**2).eval(subs={x : point}) for point in x_points]
do_whatever_you_need_to_do_to_use_THE_CHOSEN_BACKEND()
you write
p = Plot(x**2,x,start,end)
p.backend = THE_CHOSEN_BACKEND.
Obviously the current plotting framework also presents a simple interface,
but the quality of the plot is not great and the options it presents are
limited.
In test.py you can see (in comments) the basic options that the module
provides.
There is more stuff to be added, but as it already does all that I need, I
am waiting for your opinion before adding anything else that may turn out
nobody will use.
Stefan
On 26 October 2011 15:34, Christophe BAL <[email protected]> wrote:
> Hello,
> what are the main differences with the current plotting system ? Are there
> some "visual" examples ?
>
> Best regards.
> C.
>
> 2011/10/26 [email protected] <[email protected]>
>
>> Hi,
>>
>> Some time ago I announced that I was playing with some code for a new,
>> more general plotting framework for sympy.
>>
>> The pull request for the proposal is
>> https://github.com/sympy/sympy/pull/673 and I've cleaned it up a bit. In
>> the pull request I describe the idea. It should support multiple backends
>> (the current framework can be one of the possible backends, but a cleanup is
>> needed).
>>
>> I'm not sure if the code is fitting your vision for a plotting framework
>> but on numerous occasions Certik has mentioned that he would like a backend
>> agnostic framework. The code I propose is good enough for me but you may
>> consider it too limited.
>>
>> So, should I continue working on this proposal, do you like it, do you
>> have any comments/objections/corrections?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sympy" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/sympy?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/sympy?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sympy?hl=en.
