First of all, if you want to edit a html textarea in your favourite editor then you can do that already with browser extensions.
A Sage browser UI that is more suitable to developing code was part of my motivation for setting up http://sagepad.org. I Coupled with menu entries / keyboard shortcuts to doctest the current method / class / file, this would be a nice way to develop code (the latter part isn't implemened yet though). Since different people use Sage in different ways and for different purposes there is definitely space for more than one user interface. I also think that this could be turned into a way to edit, build, and test the Sage library. Probably with a bit of unionfs hackery. On Thursday, August 9, 2012 1:04:51 PM UTC-4, Nils Bruin wrote: > > Short version: > > Given that there is already an editor widget with the sage notebook, > perhaps it's easy to make a "open in a dedicated editor widget that > remains open" option? > > Motivation: > > While the notebook works excellently for smaller experiments, its use > gets painful for testing and editing a class definition of, say more > than 100 lines. Its key binding of page up/down and its notions of > scrolling simply aren't very compatible with code editing. Plus, in a > lot of these cases, one would probably want a an edit window on the > code permanently, side by side with a testing (notebook) window. On a > local system, this is of course no issue: You just put your code in a > local file, open it in an editor and put the relevant "attach" command > in a notebook next to it. > > This almost works on a remote notebook server too ... > * The location of the code is clear: DATA. > * There already is an editor: click "edit file" and you get line > numbers and even syntax highlighting! > > I noticed (at least) two problems that prevent productive use for code > development: > * The editor window opens in a rather limited frame. For this > application it would be nice if it used a full browser window > * The "save" button jumps back to the worksheet. I was hoping for two > browser windows side-by-side, one with a code editor onto the code, > the other one on the notebook page. The editor should remain open on > the file. > > Possible remedy: > > Given that there is already an editor widget with the sage notebook, > perhaps it's easy to make a "open in a dedicated editor widget that > remains open" option? > > I'm not so ambitious to propose all sage development should happen in > a browser. However, I think the phase where someone has some > substantial code that is not tied into the sage build infrastructure > at all yet would still be convenient to support from the notebook > itself. > > In the phase following that, it's pretty clear one needs a private > sage installation anyway, because integrating code into sage proper > means "sage -b". That's only necessary once one *has* code to > integrate, though. Especially in supervising situations, it is > actually pretty convenient to have everything reside on a (shared) > worksheet before proper integration. > > (I am aware havoc will ensue if multiple people open a file in DATA in > an editor and start editing simultaneously. This will be more likely > with editor windows that remain open. I guess the "save" button should > pop up a dialogue if the file in DATA was found to be changed by > something else.) > -- -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
