Release: EditArea Template Extention

It ain’t perfect, but it’s not half bad. Thanks, wlvrn!

Good, bad, ugly? Notice anything off with it Wilson?

Sorry, I wasn’t clear. By “it” I meant EditArea. It’s not perfect (syntax highlighting can get a little goofy, I noticed), but it’s only at 0.6.4 or something like that. Your extension works just fine, as far as I can tell. I haven’t seen any crashes, hiccups, or other shenanigans.

Groovy. I agree on EditArea, but I find it makes like a lot easier when trying to make quick fixes with the template. Not being able to tab in there really annoys me. For large scale changes, I usually go to trusty EditPlus and copy and paste back and forth.

where is the javascript file? it isn’t in the zip..

Yes, the first post isn’t 100% clear on where to get the js files and what to do with them. I wrote this to assist:

1) download extension 2) download zip file from EditArea 3) Open zip file / upload directory named edit_area to http://www.website.com/js/edit_area/ 4) open extension - around line 42

right below

$editareacode = '

see this below - modify by adding domain to http://www/

script src="http://www/js/edit_area/edit_area_full.js

5) upload & enable extention

Handy, I’ll probably use this going forward on my site. Thanks.

My main quible with TextArea text editor at the moment is that the font type is a little smudgy – it’s not as clean as what the default EE font is in its template text area. I know this sounds ticky tacky but I work in these editors a lot and something like that really makes a difference. I wonder if that font type can mirror what EE uses?

– EDIT ADD: in edit_area_full.js doing a search for “monospace” you can swap out that font for one of your own choices. It appears that EE templates by default use “Lucinda, Verdana, san serif.” To also mirror EE’s default template font size: in edit_area_full.js search for:

font_size: "10"

and change “10” to “8.” In addition to changing the font family to Verdana (my personal choice) I also changed the font color to mirror EE’s default styles by adding “color: #333;” here:

body, html, table, form, textarea{font: 12px Verdana, sans-serif; color: #333;}

–

The full screen editor mode is very nice btw.

Also noted in the todo.txt file in the TextArea zip:

/*** Compatibility ***/ Supported browsers: Firefox 1.5 & 2 IE 6 & 7 Opera 9 No more supported: Netscape 8 with rendering mode IE Mozilla 1.7 (buggy) Safari will wait until I can test it and debug it on a mac

Oh my God! I got that working. I must say that has got to be the best extension yet. I can’t believe this isn’t part of the standard package. You sir are amazing.

Fantastic updates Rob Q! Thanks!

Is it possible to have line wrap? with really long lines I end up with horizontal scrolling.

Other than that I love this extension.

I’m not sure, to be honest. I’d have to take a look at the EditArea documentation.

Yeah, i think the line wrap is the deal breaker for me here because I tend to have multiple windows open when I work and it’s unproductive when I have to scroll sideways so much with it. I hope we could figure that out.

==

EDIT ADD: Ok so in the documentation it doesn’t mention world wrap anywhere so I’m thinking it doesn’t have that functionality built in natively. So, I came across that you can set the “dispay” to “later” which means that it would not load the editor unless you toggle the “Toggle editor” check mark. Essentially EE stays as the primary editor and EditArea can be engaged after page load with the toggle. I figure if isn’t my default editor I can still use it in full screen mode when it’s the only thing I’m working on and need extra space. Also, by changing “fullscreen” to true - it will load in fullscreen mode automatically and then can be toggled back if you want to go back to regular size. Those were my two changes I made, making it the secondary editor and then entering full screen mode automatically. Again, though, with this extension enabled I noticed that even EE’s line lengths get much much longer even when Edit Area is not toggled on. That’s a little strange.

I also emailed the contact at the EidtArea page about line wrap capabilities but not sure if I’ll get a response - the webform was in french.

I have a question regarding the loading of the [removed]

in the extension this line:

if($IN->GBL(‘M’,’GET’) == ‘edit_template’ || ‘update_template’) {

As far as I understand this should check if we are in the template area and only then inject the script headers….unfortunately the JS header are injected in the entire CP and the script throws an error since it can’t find a field with the given ID… Plus all the editors (no access to the templates) are loading an additional 120kb of script.

What seems to be wrong with that line?

if(false or true) {

Will evaluate true, every time.

If should be:

if($IN->GBL('M', 'GET') == 'edit_template' OR $IN->GBL('M', 'GET') == 'update_template') {