[sage-devel] Re: sage notebook project

2009-09-27 Thread William Stein
On Sun, Sep 27, 2009 at 2:04 PM, Serge A. Salamanka wrote: > > William Stein wrote: >> >> In the notebook separation, it has been a fine line between rewriting >> things (which takes longer) and just leaving them possibly suboptimal. >>   One thing I did was completely rewrite everything that use

[sage-devel] Re: sage notebook project

2009-09-27 Thread Serge A. Salamanka
William Stein wrote: > > In the notebook separation, it has been a fine line between rewriting > things (which takes longer) and just leaving them possibly suboptimal. > One thing I did was completely rewrite everything that used pexpect, > so the notebook doesn't depend on the sage/interfaces/

[sage-devel] Re: sage notebook project

2009-09-27 Thread William Stein
On Sun, Sep 27, 2009 at 12:17 PM, Harald Schilly wrote: > yes, i can do that. this week i'm a little bit short on time, but i > can do it. is there already something online? just tell me any details > that might be necessary to know, like the repository or mailing list, > and i can set it up. OK

[sage-devel] Re: sage notebook project

2009-09-27 Thread William Stein
On Sun, Sep 27, 2009 at 11:31 AM, Ondrej Certik wrote: > On Sun, Sep 27, 2009 at 11:25 AM, William Stein wrote: >> Harald, >> >> Is there any chance you could design a website for "The Sage Notebook" >> as a separate project from Sage, kind of like how >> http://pynac.sagemath.org/ is a separate

[sage-devel] Re: sage notebook project: status report

2009-09-23 Thread Paulo César Pereira de Andrade
2009/9/22 William Stein : > > Hi, > > I was able to create a limited functionality separated sage notebook so far: > >  http://sage.math.washington.edu/home/wstein/patches/sagenb/ > > One key thing I did was abstract out how the worksheets communicate > with another python process.  I then did a r

[sage-devel] Re: sage notebook project: status report

2009-09-23 Thread Tim Joseph Dumol
04:11 < timdumol> wstein-3852: Oh, I've been looking through the sagenb code, and I noticed that WorksheetProcess is an old-style object (doesn't inherity from object). Also, `misc/sageinspect.py` has been patched in 4.1.2.alpha2, and the changes are not yet reflected in the one y

[sage-devel] Re: sage notebook project: status report

2009-09-22 Thread Michael Brickenstein
voila, here it is. http://bitbucket.org/brickenstein/rumcomponent/src/tip/rumcomponent/ See test_component.py for examples. Cheers, Michael On 22 Sep., 17:33, Michael Brickenstein wrote: > I am just in the progress of seratating the component architecture. > I still have a test to > fix. > Then

[sage-devel] Re: sage notebook project: status report

2009-09-22 Thread Michael Brickenstein
I am just in the progress of seratating the component architecture. I still have a test to fix. Then I'll upload it to bitbucket. After that I'll have to upload it to PYPI, adjust RUM to use it. Furthermore, I would like to create a wrapper for Pylons/TG2 (somewhere you have to hook in some config

[sage-devel] Re: sage notebook project: status report

2009-09-22 Thread Michael Brickenstein
Hi William! > Many thanks for pointing that out!  You're exactly right that I'll > need a lightweight component architecture, and I'm glad that I don't > have to write it. Actually, I am not so very deep in the technical details. But I know, that Alberto's constructions are always technically su

[sage-devel] Re: sage notebook project: status report

2009-09-22 Thread William Stein
On Tue, Sep 22, 2009 at 1:27 AM, Michael Brickenstein wrote: > > Hi! > > I had a small look at it. > > Of course, there is a lot of Sage code in it and it looks, as if you > have a lot > of partial problems, that will be specific to Sage/... . Yes, there is of course a lot of Sage code in it, si

[sage-devel] Re: sage notebook project: status report

2009-09-22 Thread Michael Brickenstein
Hi! I had a small look at it. Of course, there is a lot of Sage code in it and it looks, as if you have a lot of partial problems, that will be specific to Sage/... . So it seems, you will need some component architecture like that we are using in RUM. It is completely light weight. The goal is