> I was already discussing with Bharath some changes that need to be > > made in the class structure. For example, right now, plotting a list > > of expressions is handled by plot(). But really this should be > > factored out in some base class, so that any plotting function can > > just use it naturally. This will later be extended to things like > > plotting different expressions with different colors. > > I don't see how this makes sense in the current structure. What you > want to do can be added to the `Plot` class (and it makes sense to be > there). >
I agree with Stefan on this. I think the class structure is very nice, and any other class structure will increase the complexity of the code. > > At the moment there is a class representing the whole plot (`Plot`). > It contains each element to be plotted (subclass of `BaseSeries`). The > backends use methods like `get_segments` in order to get coordinates > and plot them. If we add something that represents "a few elements to > be plotted, for instances a number of lines" and call it > `MultipleSeries` what happens when we want to add two instances of > `MultipleSeries` to `Plot`. If the reason for the creation of > `MultipleSeries` was in the first place to be able to change colors > automatically, then we should merge the two instances of > MultipleSeries into one instance. However this is really ugly as it > just adds another layer between Plot and whatever single element is to > be plotted that only repeats what Plot already does. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To view this discussion on the web visit https://groups.google.com/d/msg/sympy/-/hDFoiKA8g74J. 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.
