On 1/31/11 5:49 AM, Timothy Clemans wrote:
I think the first step is making it so one can easily edit the notebook if they built Sage from source. The test notebook would automatically be launched. Once you've launched the notebook you shouldn't have to touch the command line.
That's an interesting opportunity. Maybe the /src url, which apparently currently shows the source tree, could have an "edit" link, like google code or github does. We already ship (an old version of) codemirror. The edit link could load the file into codemirror, allow an edit, check in the changes, and then restart Sage. Edits on the notebook repository are immediately live, and edits on the sage library would just require kicking off a sage -br in the background (until some current projects I've been hearing noises about fix that so that you don't have to do sage -br)
It sounds possible, and almost immediately implementable for the notebook. I suppose one nontrivial thing is maybe having some sort of user permission to edit the notebook, and implementing the copying of the file and checking in of changes (I certainly wouldn't want just anybody editing the public sagenb.org notebook live!)
Jason -- 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
