On 7/2/11 1:19 PM, Jason Grout wrote:
On 7/2/11 12:59 PM, William Stein wrote:
On Sat, Jul 2, 2011 at 9:33 AM, Christophe BAL<projet...@gmail.com>
wrote:
Thanks.
I'll try to do this as soon as possible.
C.
You might find this 3-person student project from Math 480 that did
*exactly* this relevant:
http://wstein.org/edu/2011/480a/projects/juarez-sean_johnson-priya_chagaleti.zip
Alexander Juarez, Priya Chagaleti, Sean Johnson: "Integrating a coding
view to replace the current textfield and tiny MCE views"
This is from the list here: http://wstein.org/edu/2011/480a/projects/
I took a look at this. Here are some thoughts:
* it appears to use EditArea (not CodeMirror). I'm curious what the
rationale for this is, especially since the paper seems to reference
CodeMirror.
Some follow-up thoughts relating to EditArea:
* the last release was Jan 2010, so 1.5 years ago. That's a long time
ago for a web tool.
* EditArea appears to be based on tinymce, which would mean that it uses
contentEditable features of the browser. This is potentially
problematic since contentEditable stuff is very buggy and inconsistent
across browsers. The ACE and CodeMirror2 implementations approach
things a different way (a hidden textarea, with the representation in a
div) that apparently is not only much less buggy, but also much faster
as well.
So I'm not convinced, on the surface, that EditArea is the right choice
for code cells. However, this patch is valuable even so, as it shows
how to replace the code cells with some more sophisticated technology.
Of course, the devil is in the details and nothing beats trying out both
ways to see which is better.
Thanks,
Jason
--
Jason Grout
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
