[Patch/Mod] Editor Selection when editing a document

[Guest]

Welcome, Guest. Please login or register.
Did you miss your activation email?

1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Bravado]

Ok...this is a bit of a sneak peek on a feature that has been added for the next MODx release.  In a nutshell, I've had a few folks asking if there was a way to use a plain textarea instead of FCKEditor or TinyMCE when editing a document.  The answer?  Yes...but it would have required a bogus plugin...which doesn't make sense in this case.  So...instead, I opted to just add an option to allow selecting "None" under the System Configuration thus forcing the content area to display a plain textarea instead of an RTE.  Simple...and it works well!

Now that that's out of the way, another thing I thought would be nice is to allow switching between the different editors without having to visit the System Configuration page each time.  I ran into this problem while attempting to add a document that would act as a pure CSS content page...which can be a bitch to edit without FCKEditor and TinyMCE screwing up the code!  So, what I thought would be nice is to have a simple dropdown menu that allows you to select the editor you want to use: None, FCKEditor, or any other editor that has been added in (TinyMCE, Xinha).  This way, if I edit a document that just has pure CSS code in it, I can switch to 'None' and safely edit my document knowing that FCKEditor isn't going to screw it up.  Works great and I'm happy!  The dropdown was added just below the main content editor like so:



Attached is a zip file of the three files that have changes to them.  These are based off of the default files in version 0.9.1 so if you've made changes to these file make sure and run a comparison check against them.  These files will go in your /manager/actions/dynamic directory.  I've tested the code in Firefox and IE 6 on XP and feel pretty confident that it'll work nicely on the Mac and Linux as well.  Let me know if you find a problem with it.

Aside from these changes, I'm also planning to change the way the Template and Chunk editing works.  I don't see any reason why we couldn't implement similar functionality in these sections.  I'll be experimenting with the code here and if all goes well I'll submit my changes for the next version very soon. 

Have fun! 

Jeff

[sottwell]

Um...scratches head...Can't you just un-set the Rich Text checkbox in the Page Settings tab of a document?  And click No in the system configuration?  I think I'm missing something here.

What would be useful is to have the Resource Browser available even if the RTE isn't.

I also found useful the patch that allows an individual user to be set to use None as well as which editor to use.

[rthrash]

This is really awesome as it allows you to set different editors for different docs in the same in stall. Sweet. I can see instances where FCK would be preferable, and others where Tiny would work, and (most) others where a plain text would be my preference. Killer job!

[Bravado]

This is really awesome as it allows you to set different editors for different docs in the same in stall. Sweet. I can see instances where FCK would be preferable, and others where Tiny would work, and (most) others where a plain text would be my preference. Killer job!

The editor preference isn't actually saved with the document...however though, I'm sure that could easily be changed!    Definitely something to think about! 

[Bravado]

Another thing that was brought up is the ability to set permissions on a per-user basis on which editors are available for use.  If you add a per-page /per-document setting then it's probably necessary to implement a different approach to per-user and global settings for the editors.  Need to brain-storm this...and quick!  LOL!

[Djamoer]

Another thing that was brought up is the ability to set permissions on a per-user basis on which editors are available for use.  If you add a per-page /per-document setting then it's probably necessary to implement a different approach to per-user and global settings for the editors.  Need to brain-storm this...and quick!  LOL!

In fact we spell it ja-son

Anyway, I think the format does need to be a commonly used format. I like the idea of xml, but I also like the idea of having other text format.
I think suggestion or comment will be awesome.

Sincerely,

NOTE:  I think I post on the wrong topic. It's suppose to response Jason's response on Json

[chanh]

Another thing that was brought up is the ability to set permissions on a per-user basis on which editors are available for use.  If you add a per-page /per-document setting then it's probably necessary to implement a different approach to per-user and global settings for the editors.  Need to brain-storm this...and quick!  LOL!

Jeff, (updated after Wendy point it out)

To have this feature that you just sighted it would be really nice!

I tried out your patch it works very nicely!  Well done!

[Djamoer]

Jason,

To have this feature that you just sighted it would be really nice!

I tried out your patch it works very nicely!  Well done!

I think it's suppose to be Jeff, not Jason. Sorry for my previous post