Quote from: Gildas at Oct 26, 2006, 01:09 PM
Before writing this plugin I’ve installed EditArea as explain by Pixelchutes i.e in /manager/media. But indeed, /assets/plugins is more apropriate As explain by Pixelchutes you only need to copy the edit_area directory from the EditArea distribution.
@Gildas- Great work! Haven’t tried out the Plugin yet, but looks very nice. Any idea on what the "bug" was/is during doc. editing?
@TobyL- Thank you for posting the events.
I do agree that I wish EditArea’s performance was a little better. It does say that it’s intended use is for SMALL TEXT. I wonder, whether it’s definable by param, or by default, would it make more sense to have EditArea (the "editor": line #, status bar, etc) and highlighting toggled OFF by default
? By allowing Toggling, but keeping off by default, highlighting--costing slight performance drawback--is only a click away...
, I enjoy the highlighting, Line #’s, and built in functions so much (for being in a browser) that I don’t get very irritated waiting a second or so for it to render.
I find it more irritating
not knowing where comments begin/end, if I’ve closed a string declaration, or typed a function name correctly (reserved keyword highlighting). Also,
I am a HUGE fan of the bracket matching, something I use very much in my desktop editor. As the old paradox says,
"Pain is beauty, beauty is pain."