I’m trying to get the very last thing done for Inlay – the +#$&@ WYSIWYG editor. I have looked at a lot of them over the past few days, and I’m very close to settling for TinyMCE, simply because it has most of what I need. That said, it’s very MS Word-like, and that pains my soul to inflict on another – particularly a paying customer.
I know there’s been a lot of interest in this area lately, so I’m hoping there is a new option I haven’t considered yet. If you have any favorites, please let me know. Here are the requirements:
Free / open-source, with a liberal license like BSD, MIT, or LGPL2 (not 3).
No jQuery. At all.
Valid HTML5 output (or XHTML if that’s not an option).
An image tool that does NOT rely on being able to upload to the server (which will not work in this construction).
Basic formatting, but not enough rope for a client to hang herself. (If the editor comes with every damned option, then a way to turn some of these off.)
Not ugly (see TinyMCE for the reference of what ugly looks like). I don’t have another month to fiddle with icons and buttons and endless CSS.
TinyMCE has a lot going for it: it’s available in a lot of different languages out of the box, it has a client-friendly layout, and it produces clean code. If it didn’t remind me so much of fluorescent-lit felt-lined cubicles, I could actually get along with it quite well.
The latest TinyMCE looks pretty cool so you could skip the point 6, but it is on jQuery so point 2 comes in play - and it has no free image/file editor which means -1 on the scoreboard.
Some of Todd’s examples are not ugly but the most.
What about your own dev? Let’s start to make this pretty?
I would do this, but I have sincerely run out of time on Inlay – I have to get it launched and out there and making some income or I can’t justify more development time on it.
Walter
On Aug 2, 2014, at 4:19 PM, Thomas Kimmich wrote:
What about your own dev? Let’s start to make this pretty?
Naturally yes - it’s about to find an editor - but if it’d be my project, I’d choose redactor (and serve my family one week nothing else than potatoes - but don’t tell them).
All I can do is to offer to take one fourth of the middle (199$) if it is enough - more is currently not affordable. But it’s worth - the Editor is the living core of a CMS project.
Right now, I am using Prototype for Inlay, but my eventual goal is to remove it entirely and use nothing but plain JS throughout, so it can be used in either idiom without conflict. I realize that jQuery “won” the mindshare race, even my beloved Rails switched over several years ago, but my JavaScript programmer’s brain is heavily influenced by Prototype, and I find it really quite difficult to switch over. The difference between the two reminds me of that old canard about the English and the Americans – two countries, divided by a single language.
Walter as mentioned above and shown in the vid… I have stumped up the cash for a commercial redactor license and yes that is a jQuery based Richtext editor. After a lot oof testing I found it so much nicer than any of the others.
The way I have got around the editor working in a non jQuery library based environment is by creating three identical based editor wrappers which are driven by the three big libraries
jQuery
Mootools
Protoype
this alone has cost me a small fortune in time and money!!!
These three wrappers look and function identically. Then all the actual editors eg menu, image or richtext editors are pulled in via an iframe. within the window. This allowed me to keep all the existing jQuery based scripts that were used in the original (popup window) based version of WebYep For example the menu ‘sort script’ in the menu editor was jQuery based. The choice of an iframe also allowed me to introduce and use the redactor editor as well.
I don’t know if this method is suitable or not but I thought I would mention that’s how i got around the conflicting library requirements and Redactor editor choice.
Looking forward to seeing inlay… Freeway is desperate need for more choice when it comes to cms’s I know there’s the Joomla actions, minicms and EE actions but its good to see that expanded if you need any other info from me then let me know.
all the best max
