On Thu, Mar 8, 2012 at 10:33 AM, [email protected] <[email protected]> wrote: > On 8 March 2012 18:25, Aaron Meurer <[email protected]> wrote: >> This looks like a good start. Did you think about ways that some of >> these ideas can be used in SymPy Live too? >> >> On Thu, Mar 8, 2012 at 9:55 AM, Bharath M R <[email protected]> wrote: >>> Hi, >>> I am Bharath M R, a student of Electrical Engineering at IIT Madras. >>> I would like to apply for the building the gamma.sympy.org site. I would >>> like to >>> implement the following things as part of the project. >>> >>> 1)Basic parsing >>> Something like solve x**2==1, integrate x**2 will be parsed and interpreted. >>> Doing something like wolphram alpha would require a lot of ideas from >>> natural language processing which I am not familiar with. >> >> This is something that can be improved upon over time. The important >> thing here is to start with a good framework in SymPy to build upon, >> so we can easily extend it with new rules. >> >> And no matter how much you implement, it will always be a heuristic. >> We just want it to catch the common case. We can do things like >> provide a feedback button for mis-interpreted input, so we can get an >> idea of what doesn't work and where things need to be improved the >> most. >> >>> >>> 2) An incremental search for functions in symPy >>> Its very important for a person to get to know the particular function he >>> wants to use. This will be implemented using ajax calls to the sphinx >>> documentation database.This will be similar to search in scilab / >>> mathematica. >> >> Additionally, there should be links throughout the interface to the >> relevant Sphinx documentation for the various functions used (similar >> to in WolframAlpha). >> >>> >>> 3) A lyx/ Mathematica styled input. >>> This greedily converts the expressions into latex symbols, so that the user >>> knows what he is actually computing. We can also add a set of symbols for >>> summation, integrals, differentiation as a bottom bar. The input will look >>> like latex input to the user, while we convert the expressions into required >>> symPy functions in the backend. >> >> How did you plan to implement this? For now, the way that I know to >> do it is to first compute the whole expression to SymPy, then call >> latex() on it, and parse the latex with MathJax. That is what happens >> at SymPy Live. It sounds like you want something that lets you type >> LaTeX styled math on the fly, which basically amounts to an equation >> editor. >> >>> >>> 4)Matplotlib for plotting >>> We plot the expressions, if it is plottable just as Wolphram Alpha by >>> default. >> >> The app engine now supports numpy, so this should be doable (I hope). >> Our matplotlib plotting engine is still in its infant stages (for now, >> it only lives at https://github.com/sympy/sympy/pull/673), but it >> should grow. Hopefully we will get another project that will improve >> it. You could also spend some time of this project working on it, >> though obviously it would be better if most of the time were spent >> doing the other things. > I am not certain but I think that matplotlib includes some C code and > so it won't work on GAE. But the new module can easily be extended > with other backends like Google Chart API. > > Also there are some less used matplotlib backends that do not need > compilation (pure python) > http://old.nabble.com/Pure-python-matplotlib-for-Google-App-Engine-td32721389.html
Oh, OK. Here is the app engine issue to add matplotlib: http://code.google.com/p/googleappengine/issues/detail?id=482. Someone there suggests using http://code.google.com/p/svgfig/ as a pure Python alternative to Google Charts. It's GPL, though, so I don't know if that would be a problem. Regardless, it looks like a neat library to add a backend for. It should be easy (see http://code.google.com/p/svgfig/wiki/PlottingTutorial). Aaron Meurer >> >>> >>> 5)Ipython like notebook. >>> I think it is possible to port the Ipython notebook according to this >>> discussion(https://groups.google.com/forum/?fromgroups#!topic/sage-notebook/re2bUt4vCxA). >>> But the time it takes to port is not very fixed. I want to know whether I am >>> overreaching by including it. >> >> Even without the notebook, we should use IPython itself in SymPy Live >> (http://code.google.com/p/sympy/issues/detail?id=2645), if that's >> possible. That will give us things like better tab completion and >> access to IPython magic. My idea is that you should be able to click >> on a SymPy Gamma calculation and just get a little SymPy Live session, >> so the two projects are related. >> >>> >>> 5) Make the interface look beautiful with twitter bootstrap. >> >> +1. I don't know anything about this specific library, but a >> beautiful, highly functional interface is almost as important as good >> functionality. >> >> Aaron Meurer >> >> -- >> 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.
