I just finished tying the jQuery WYSIWYG editor into a new ExpressionEngine extension. It’s a really lightweight, simple and stripped down WYSIWYG editor that actually writes decent code. It’s worked well so far so i’m sharing it with all.

[UPDATE] Current Version: 1.1
Download SF jWYSIWYG Now.

I’ve attached a quick screenshot of it as well. Enjoy, and let me know if you have any issues.

VERSION 1.1

-Added: MSM Compatibility
-Added: CSS Setting to allow the jWYSIWYG window to be styled

Awesome, Jack.  Thanks for sharing it!  I’ve added it to this wiki page.

Very cool Jack.

Have you tested this editor at all with Safari?

I have authors that use Safari and Firefox both quite extensively and in the past all of the WYSIWYG editors croak in Safari.

Jamie

Jamie Poitra - 18 May 2009 01:08 PM

Very cool Jack.
Have you tested this editor at all with Safari?

Everything works perfectly in Firefox as well as Safari 4 Beta. Safari 3 works on bullets, italic, bold, etc.. but chokes on the SIZE functions (h1, h2, font size increase, decrease, etc) unfortunately. I’ll put in a support ticket on the Google Code site and see what comes of it.

Nice work, Jack. I’ve been looking for something simple like this.

Very cool.

That would actually be OK for me as I wouldn’t want the users doing that anyway.  Those can be disabled easily.

I think I might have to use this.  Exciting. 

I’m assuming you set the field to not be parsed by the XHMTL function?  Or can the editor be set to not do line breaks and paragraph tags?  That would probably be my preference as we have a lot of legacy data.

Is it possible to over-ride the inline styles that the editor puts in though. Would be much nicer if bold and italic weren’t done with inline styles.

Best wishes,

Mark

Cool, Jack. I would love to try it, but I have to have an integrated “paste as plain text” button before I can make it live anywhere. MS Word puts some hideous code in the copy buffer.

Mark Bowen - 18 May 2009 01:28 PM

Is it possible to over-ride the inline styles that the editor puts in though. Would be much nicer if bold and italic weren’t done with inline styles.

Didn’t realize that’s how this one works.  That’s really too bad.  Kills the usefulness of it for us.

Jamie

Jamie Poitra - 18 May 2009 01:36 PM

Mark Bowen - 18 May 2009 01:28 PM

Is it possible to over-ride the inline styles that the editor puts in though. Would be much nicer if bold and italic weren’t done with inline styles.

Didn’t realize that’s how this one works.  That’s really too bad.  Kills the usefulness of it for us.

Let me look into that. I think there’s a way to change that functionality. Will let you know!

@Dan
You can always paste it into TextEdit or windows alternative as a plain txt file, then copy and paste it into the WYSIWYG field… an extra steo I know but would solve the problem for you

@Justin - yes, definitely. But I can’t go back now and take away features we already have in TinyMCE that I’ve trained my clients to use.

Awesome, I was wondering if someone would get round to it.

No fan of WYSIWYG but it’s always good to have options. Cheers, Jack!

Saw this the other day and was also wondering if/when it would be made into an extension. Will check it out as an althernative to textile and the textile editor helper.

Regarding the

code re-writing, it seems there is no way to set that to use <strong> tags at this point. There are a number of threads in the Google Code page requesting its implementation, so when a change happens, i’ll make sure to update it.

All things considered though, it’s a worthy sacrifice for clean code.

I’ll also be adding a few more options to the extension—checklists for adding/removing buttons, link to your stylesheet to see live changes in the editor, and possibly an activate/deactivate button (or double click) feature so situations like @Justin’s will have a solution.

Hope it’s useful! Let me know how it works for you guys.

What are the chances of dropping this in to field frame to use as a cell?

Hi Jack, I’m getting this error on my publish page and no wysiwyg editor showing up after enabling the extension:

“Notice: Uninitialized string offset: 0 in /home/craps5/public_html/system/extensions/ext.jquery_wysiwyg.php on line 39”

MSM 1.1 - Build: 20081024, EE 1.6.7 Build: 20090515

This doesn’t appear to work with MSM very well.

I have to create the full folder structure for each MSM site which is a pain!

Any chance you can make it MSM aware so I only need it in one place?

@jkneeshaw Should be all set, give this link a shot:

jQuery WYSIWYG 1.0.1