Support/Comments for [Plugin] EditArea

We have officially launched v0.3 stable!

Check out the download link (in my signature) to get the best version yet! (Now with hotkey CTRL+S quick saving, and Plugin configuration parameters, which means NO CODE EDITS REQUIRED to configure your plugin!)

Feature request: I’m using FF2 and when I invoke the Find dialog, I enter the search terms and press Enter. Nothing happens. I have to click with my mouse.
Most distracting...

Otherwise I’m using the plugin and it helps me a lot.

This is getting better every time! Excellent work. I’d vote to get this into the MODx core...

One thing I noticed though. Why is the REGEXPS section in php.js commented out? (It’s meant to highlight php variables) I uncommented it without it causing any problems.

Quote from: andrazk at Feb 23, 2007, 02:40 AM

Feature request: I’m using FF2 and when I invoke the Find dialog, I enter the search terms and press Enter. Nothing happens. I have to click with my mouse.
Most distracting...

Otherwise I’m using the plugin and it helps me a lot.

You know what, I think I noticed this happened and inadvertently discarded it... I should have known better... no worries, once I get it updated, I’ll update the repository as well as this thread.

@TobyL,

I totally agree! One concern I do have about Core implementation is that this plugin does seem to function a bit slower, if you will, in Internet Explorer...Not totally sure why, but there is a noticeable delay in IE from FF... However, my recommendation since Day 1 has been for a Core implementation, but with the plugin Disabled by default (or a plugin configuration which doesn’t load in Highlight-mode by default)...this way, users who Really want to use it can simply toggle on the plugin/highlighting and be good to go hopefully without impacting any other users who might not care

If we get enough push, let’s see if I can’t encourage a core-release roll out

As for the REGEXPS/php.js, I’m not quite sure... possibly Gildas can comment?

UPDATE:
I also confirmed uncommenting this section within php.js seems to work just fine, with increased highlighting to boot. Hmmm... once confirmed, I may commit both these requests into the repository Today.

Quote from: pixelchutes at Feb 23, 2007, 09:46 AM

As for the REGEXPS/php.js, I’m not quite sure... possibly Gildas can comment?

Thanks TobyL I think that the REGEXPS section in php.js has been commented out for performance reason when editing huge files. I’ve uncommented this section in the SVN repository (Rev.24). Wait and see...

Quote from: Gildas at Feb 23, 2007, 10:51 AM

Quote from: pixelchutes at Feb 23, 2007, 09:46 AM

As for the REGEXPS/php.js, I’m not quite sure... possibly Gildas can comment?

Thanks TobyL I think that the REGEXPS section in php.js has been commented out for performance reason when editing huge files. I’ve uncommented this section in the SVN repository (Rev.24). Wait and see...

Sweet! Thanks, Gildas...Any luck regarding the CTRL+F (Find) feature and no longer being able to use "Enter" to submit? I played around in keyboard.js (tried some troubleshooting) but not with much luck...if I had more time, I’m sure I could track it down...

I love this plugin by the way. Anyway, anyone know what event can be used to make this available in quickedit on the front end? I tried all the render events and it doesn’t work. I would just like certain pages content to be editable through this rather than through WYSIWYDG.

Quote from: jazzfanatic at Feb 23, 2007, 12:26 PM

I love this plugin by the way. Anyway, anyone know what event can be used to make this available in quickedit on the front end? I tried all the render events and it doesn’t work. I would just like certain pages content to be editable through this rather than through WYSIWYDG.

Actually, we are working on this implementation for an upcoming release. It should be pretty easy, we just need to devote a bit of testing in this area. Regardless, it is Definitely on the To-Do list included in the package.

In IE7 with MODx 0.9.6-rc1 I don’t seem to get any highlighting. editArea loads fine, just no pretty colors! Can anyone confirm this before I start pulling things apart at my end?

Hmm, come to think of it, if it’s a problem at my end I might just leave it as is, it’s only IE afterall

Quote from: TobyL at Feb 23, 2007, 05:33 PM

In IE7 with MODx 0.9.6-rc1 I don’t seem to get any highlighting. editArea loads fine, just no pretty colors! Can anyone confirm this before I start pulling things apart at my end?

Hmm, come to think of it, if it’s a problem at my end I might just leave it as is, it’s only IE afterall

In 0.9.6 RC1(rev 2374), I successfully tested EditArea 0.3 in IE 7, syntax highlighting working fine...

Please double check that "Initialize with highlighting enabled?" is set to "true" in the Plugin Configuration tab, or try clicking on the "toggle syntax highlighting" button??

Also, can you confirm if it is working for you in FF either? (working in both FF/IE on my end here...)