On Fri, Feb 22, 2008 at 1:09 PM, Jason Grout <[EMAIL PROTECTED]> wrote: > > Wow, this discussion blew up way to fast for me to keep on top of it and > form a coherent opinion. Ted, I'm specifically CCing you; if you don't > want to reply (either on or off list), I understand. Personally, I'd > like to keep working on some the issues that I find interesting and I > think you have already and will yet have a great deal to contribute (if > you decide to keep working with us, that is). >
... > > First point: a standard API for communication with Sage. > > Summary: Ted proposed a standard API to talk with a Sage session, taking > the Mathematica API as an example. He has done a lot of work > researching alternatives and even constructing an optional spkg and > example using JSON (see http://trac.sagemath.org/sage_trac/ticket/1510) > Several other people in the project have expressed views that the > Mathematica API as too heavyweight for Sage and there has appears to be > some confusion about what introducing a standard API would mean for the > project. > > My thoughts: I'd like to continue the discussion about an API. I've > extended the notebook (slightly) and so I've had some exposure to the > notebook "API" for communicating with Sage. In my experience, that > communication falls into two parts: the communication between the > notebook and Twisted and the communication between Twisted and the sage > session. The communication between Twisted and the notebook consists of > passing text blocks (the sage commands in a cell) and other fixed-field > information, like the time it took to run a cell, whether to create a > new cell, etc. The API there is very rigid and very notebook-centric > (it was evolved as the notebook evolved). The communication between > Twisted and the sage session is entirely a pexpect stdin/stdout type of > communication. Nothing fancy or anything. > ... > > > Whew. That was a long response and it's taken enough of my time. Is > there anyone (left :) who wants to work on a communication API or wants > to work on documenting the notebook with me? If not, then I'll probably > just continue learning about the notebook and document it as I have > time, as well as continue work on interactive widgets. Can you recommend an "API for dummies"-type reference? I might be interested in working on this. > > Over on sage-edu, we ought to pretty quickly get a focus so that we > don't become too fragmented to do any good. Maybe this should be another thread but possible topics: (1) writing education materials which are integrated with SAGE, such as http://sage.math.washington.edu/home/wdj/teaching/granville-calculus/ (2) API related stuff? (3) package for Geogebra? others? > > Jason > > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
