On Jan 9, 2009, at 8:25 AM, William Stein wrote: > On Fri, Jan 9, 2009 at 2:30 AM, Martin Albrecht > <m...@informatik.uni-bremen.de> wrote: >> >>> Sure. I think that what you want is still orthogonal to the TinyMCE >>> effort, but having another edit widget in the tree "just" for >>> highlighting ought to be well thought out and the burden of >>> maintenance must be taken into account, i.e. if somehow TinyMCE >>> could >>> be extended to do Python and all the other languages the notebook >>> supports syntax highlighting via some plugins that would be >>> preferable. As far as I understand we don't use TinyMCE to edit the >>> cells themselves yet, but that could be something we might do in the >>> future. >> >> One concern I'd have about this is that this added convenience >> could slow down >> the creation and work with the input cells. They're quite snappy >> now and I >> would like to keep them that way (rather them being bloated). >> >> Martin > > I also share this concern, having done a lot of the work to make the > notebook snappy and not bloated. Last year, Tom Boothby did integrate > the EditArea code editor into the notebook, and we tried it > extensively, but it just plain "felt slow", so we didn't go forward > with including it in Sage at the time. > > Tom likes to push the notebook quite hard, e.g., editing dozens of > very large cells in a single worksheet, so he's pretty sensitive to > the bloat versus speed issue.
The same holds true for me too, if there was a mode to turn it off that could be sufficient. On the plus side, javascript execution is advancing by leaps and bounds in modern browsers. - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
