On Sun, Sep 20, 2009 at 9:04 PM, William Stein <wst...@gmail.com> wrote:
> > On Sun, Sep 20, 2009 at 5:55 AM, Tim Joseph Dumol <t...@timdumol.com> > wrote: > > Hey, > > > > I've done some preliminary work on migrating the notebook to Django on > > http://github.com/TimDumol/sage-notebook-django-branch. A lot of > > functionality has not yet been implemented. I've had a fair load of work > to > > do these past days, so I haven't been able to do much. Feel free to base > > work on it. > > > > I'd love to hear feedback about it, and suggestions on improving the > > implementation. The idea of separating the notebook from the core is > > excellent. > > > > Thanks for thinking about that. Mike Hansen also spent a lot of time > over the summer rewriting the notebook in Pylons. > That's excellent. I personally favor Pylons as well, but I thought Django is the more popular, and thus more hackable framework at the moment. I would love to see his code. > > The Sage notebook will switch from twisted web2 to *something* else > for the actual web server. I have not decided what that something > else will be, except that it should be WSGI complaint. > > My immediate goal with separating out the notebook is to > as-soon-as-possible make something stable that can be shipped with > Sage. The main motivation for separating out the notebook first is > to make it easier for other people (like you, Ondrej, etc.) to > contribute to the notebook. I would like this separated-out version > to be included in Sage-4.1.3. > > Speaking of making things easier to contribute to the notebook, the separation of notebook related data to the $SAGE_ROOT/data/extcode/notebook/ folder makes it inconvenient to make branches/clones and work on it. > When you started > http://github.com/TimDumol/sage-notebook-django-branch did you first > create a fully functional version of the Sage notebook separate from > the rest of Sage, then work from there? Or did you dive in, and > create a massive amount of work for yourself to get to an > again-functional version of the notebook? > I did the latter. Doing the former seemed too much like redoing much that that was done by Codenode. > William > > > Note: Twisted-8.2.0 does not work with Django, as noted on > > http://trac.sagemath.org/sage_trac/ticket/6897. I've made a few packages > for > > this: http://drop.io/trac_6897_reqs. Jinja2 > > (http://sage.math.washington.edu/home/palmieri/SPKG/jinja2-2.1.1.p0.spkg) > is > > also needed -- I expect #6856 to be included soon, so Jinja2 will become > a > > standard package anyways. > > > > On Sun, Sep 20, 2009 at 8:34 PM, William Stein <wst...@gmail.com> wrote: > >> > >> Hi, > >> > >> If anybody is planning on working on the Sage notebook during the next > >> week, please > >> keep in close communication with me and or this list. I'm working on > >> separating out the > >> notebook out as a completely separate Python library. > >> > >> William > >> > >> -- > >> William Stein > >> Associate Professor of Mathematics > >> University of Washington > >> http://wstein.org > >> > >> > > > > > > > > -- > > Tim Joseph Dumol <tim (at) timdumol (dot) com> > > > > > > > > > > > -- > William Stein > Associate Professor of Mathematics > University of Washington > http://wstein.org > > > > -- Tim Joseph Dumol <tim (at) timdumol (dot) com> --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
