On 7/3/11 12:12 AM, Alex Juarez wrote:
Editarea is a way to implement code mirror see
http://codemirror.net/demo/activeline.html, for an example of the
feature implemented. We would just need to update the back end in
EditArea to code mirror 2 for both all the features of tinyMCE and code
mirror. edit_area_full.js is larger because it currently has both
tinyMCE and codemirror code in it. I believe that if we upgraded
codemirror and tinyMCE in it to the most recent versions we would see
a significant reduction in the size of the code as well as a speed up.
What I mean to say is that with a rewrite we could have best of both
worlds, we would need to decentralize the current code so that it no
longer has its own tinymce and Codemirror but rather uses the ones saved
in sage.
From what you're saying, it's pretty clear to me that I don't have the
same understanding of EditArea that you do (not surprising, since you've
spent a lot of time with EditArea and I haven't). For example, when I
search for traces of codemirror in editarea, I see nothing:
~/Downloads/editarea_0_8_2% grep -ri mirror *
~/Downloads/editarea_0_8_2%
similar with tinyMCE...the only mention of "mce" I find is a file
elements_functions.js which "contains some generally useful functions
for javascript", as well as some acknowledgements: "I would like to make
a special thanks to TinyMCE developpers. I have taken some of their
WYSIWYG editor functions (managing the toolbar buttons), and it give me
inspiration for some point (gzip compression, translation,
documentation) of my project." To me, it sounds like the author used a
bit of code from TinyMCE, but did not incorporate TinyMCE to get a
WYSIWYG editor.
My understanding is that EditArea is a code editor (like codemirror, but
doesn't use codemirror code at all or incorporate codemirror in any way)
which is based on some of the same design principles as tinyMCE (again,
like tinyMCE, and even reuses some code, but does not incorporate
tinyMCE as a component nor does EditArea implement WYSIWYG editing like
tinyMCE). From what you've said, it sounds like there's something
lacking in my assessment of EditArea, or at least something lacking in
my understanding of how you plan to rewrite things to incorporate both
codemirror and tinymce into what I see as a third, distinct project:
EditArea. I appreciate you being patient with me while I learn.
To me (with my current understanding), it seems preferable (i.e., less
work on our part now and less maintenance work in the future) to depend
on two different projects (TinyMCE and CodeMirror2) which are very
active and are very good at their respective functionalities. But
again, I haven't spent the time working with EditArea that you have, so
to paraphrase William: he who writes the code gets to make the decisions.
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
