Le vendredi 29 avril 2011 à 16:10 -0600, Aaron S. Meurer a écrit : > On Apr 29, 2011, at 4:01 PM, Vinzent Steinberg wrote: > > > On Apr 29, 10:59 pm, Ronan Lamy <ronan.l...@gmail.com> wrote: > >> Le vendredi 29 avril 2011 à 11:56 -0700, Ondrej Certik a écrit : > >>> On Fri, Apr 29, 2011 at 11:24 AM, Brian Granger <elliso...@gmail.com> > >>> wrote: > >>>> In my mind the different mathematica *Form functions are analogous to > >>>> the different printers we have. In that light, I would develop > >>>> TableForm and yet another printer. Same is true of any other *Form > >>>> functions we want to copy from Mathematica. > > > > I also think it should be some kind of matrix printer. I'm not sure if > > we need some special object to store some flags, but then we should > > redesign our printer system to be consistent. > > > >>> I am not sure I understand what your idea is, but it seems that's > >>> exactly how I implemented it? TableForm is an object (it's not an > >>> issue for me whether or not it is derived from Basic, currently it is > >>> from technical reasons, but this can be changed), and then I have > >>> enhanced the printers to be able to print TableForm nicely in all our > >>> output printers. Because I want to use it with ascii (in terminal), in > >>> latex (when I write articles, it would be so much easier to just > >>> create the table in sympy, instead of wrestling with latex by hand), > >>> html, and so on. > > > > I think there are some misunderstandings. It seem that Ronan is rather > > against the technical implementation. > > Well, I understood it that he was against the idea itself, especially > based on his first email to this thread. > > I'd say rather he is against implementing in SymPy, as opposed to in > some other library that uses SymPy. Perhaps Ronan can clarify? > Well, I'm not sure. I think that this feature is peripheral to sympy's core mission and, consequently, that it will hardly be properly maintained inside sympy. So it would be better to find a suitable upstream and to shift the maintenance burden to them. I don't know whether tablib is suitable, but, in the long run, it seems much easier to extend it than to reimplement it from scratch.
If it turns out that it has to be implemented inside sympy, the difficulty is that it's essentially a new kind of object - neither a mathematical object, nor a simple printer, because it carries additional information. Actually though, it would fit quite well with the idea of an intermediate printing representation I suggested a few weeks ago [http://groups.google.com/group/sympy/browse_thread/thread/b33cf5d156691786#]. -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com. To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
