It deserve it's fantastic qualifier. It's the first wysiwyg editor I test that works correctly with iPad. Excellent work.
I would love to make it simpler to insert iPad images. Basically make the upload intermediate step not visible. Unfortunately it is not possible to upload images from the iPad.
edit: unfortunately copy past doesn't work on iPad. The selection is difficult and the copy is simply ignored. Past inserts whatever is in the clipboard.
I had two issues: you have to click on the top of an empty textarea to start editing (guessing the first input position), and text entry stopped working after pressing the bold button.
One fairly important thing I couldn't figure out how to do was move the image around. I guess I expected it to work like Wordpress or Blogger's post editor where you can drag the image around to adjust its location in the text. Instead I could only resize the image using click and drag, not move it.
I'd love to see a drag-and-drop editor that doesn't require the image be absolutely positioned and can have text interact with the image. Somewhat like iBooks Author, but without fixed page sizes.
The image options needs a little bit of work, maybe a button in in the corner to edit the float position (left/right), a little transforming box to change the size when is selected (those little squares in the corners like Photoshop) and the ability to drag it from any other part.
There's a reason why W3C didn't just replace <b> and <i> with <strong> and <em>. A lot of people think they're just equivalent, but a lot of other people disagree. "Please display this in italic" arguably sends a different message from "Please emphasize this", and in some settings they may not be interchangeable.
In HTML5, <i> and <b> now have the deliberately vague semantic definitions of "alternate voice" and "stylistically offset" – this could cover emphasis, book/film names, key words, foreign phrases, etc. Incorrect use of the more specific semantic tags (eg. generating <em> when the user sets a film title to "italic") is worse than a lack of semantic detail.
HTML5 was designed with the understanding that not all web content can be authored by someone who knows the correct use of semantic HTML tags like <cite>, <em>, <strong>, <mark>, etc. Application-level copy can use those tags, but a rich text editor (for normal people) can't know which one is appropriate, so it should always default to the vague ones, <b> and <i>.
I just added bootstrap-wysihtml5 to a project and I'm liking it. My only problem is it won't let me type comments in the HTML view and I can't figure out how to dynamically resize the text area. Redactor seems to let you do this. Looking forward to trying this out as well.
Edit: Redactor looks like it retains formatting for the HTML. That's enough to make me switch.
This is ok... although there are lots of better alternatives. Some issues:
- No way of adding headings? * edit: sorry it's under styles.
- Clicking bold, italic etc should expand the selection to the word that the cursor is in.
- Setting formatting should restore the cursor to the editing area
- Clicking into a formatted area should toggle the buttons in the toolbar that apply
- image alignment a little clunky. Why not add a simple overlay for align centre|left|right on mouseover?
On the plus side image resizing is done well.
One thing that annoys me no end is that all editors I've ever used apply block level formatting (h1,2,3 etc) for an entire paragraph when only a sentence is selected. The most intuitive approach would be to break the sentence out of the paragraph and style only it. As a user I expect what I have highlighted to change not all of the surrounding text as well!
These things aren't easy to get right, especially cross browser. I recently put together an editor to exactly suit my needs (uses contenteditable instead of an iframe), but it's chrome, firefox and ie9+(? i think) only. Trying to get something usable across legacy browsers is ridiculously hard.
I played with such javascript things a few years ago.
They were indeed hard to create and (at least then) relied on a detailed know of the browser and platform's characteristics.
But given the varying tasks which call for that kind of editor, what I'd really like to see is a small semi-standard tool or framework for the construction of such editors. As it is now, one must either use an existing tool having too many or too few features or go to the great lengths of modifying one.
I don't like the fact that when I resize the editor the content disappears until I complete the resize. During the resize (click on the tab at the bottom and drag), the content disappears.
I wonder why people make so much different rich text editor. while i only use Markdown format for my projects. I wonder about the Rich Text to HTML compatibility (some rich text editor have problem with interpreting formatted text into the HTML, since then i afraid to use rich text editor and more using it).
Markdown is great for projects where the users don't mind writing using code. WYSISYG editors are nice for people who are not technical at all to manage their website and things like that.
They do sometimes produce really terrible HTML though, especially because people copy/paste from MS Word and it results in a bunch of garbage.
The fullscreen mode is a nice touch, as is the image resizing, provided the cursor doesn't leave the image boundary. It's frustrating that, like other editors, it doesn't differentiate so well between line and block actions. Also, I was very disappointed that I couldn't drag the image to reposition it.
Looks nice, but I was unable to stretch the image back to its original size after shrinking it. It kind of inches a little bit and then stops. It's irritating to see the page announce itself as "fantastic" when it's clearly not properly finished.
Interesting. It's seem to be the issue with capturing mouse events. If you move the mouse out of the image quickly, it'll lose it and the resize will stop. But if you move the mouse slowly so that it always stays over the image, it'll resize it. It's a workaround to use for now (but sure, it's a problem with the implementation).
It is maybe nice, but not good, because it is not generating same output in all browsers. Also copying from word (most needed) is not filtered properly and same in all browsers.
Can anyone recommend an editor with a really good API for making custom buttons? My admittedly shallow research hasn't uncovered anything that is particularly joyful to use.
Great work, really nice to use. Would love to see this as a WordPress plugin (sick of the default editor) but that would require plugin support, as per the roadmap.
[+] [-] chmike|14 years ago|reply
I would love to make it simpler to insert iPad images. Basically make the upload intermediate step not visible. Unfortunately it is not possible to upload images from the iPad.
edit: unfortunately copy past doesn't work on iPad. The selection is difficult and the copy is simply ignored. Past inserts whatever is in the clipboard.
[+] [-] ricardobeat|14 years ago|reply
[+] [-] d0mine|14 years ago|reply
[+] [-] chj|14 years ago|reply
[+] [-] NathanKP|14 years ago|reply
[+] [-] alecperkins|14 years ago|reply
[+] [-] godDLL|14 years ago|reply
[+] [-] jQueryIsAwesome|14 years ago|reply
[+] [-] tzury|14 years ago|reply
Shouldn't it be <strong></strong> ?
[+] [-] kijin|14 years ago|reply
[+] [-] callum85|14 years ago|reply
In HTML5, <i> and <b> now have the deliberately vague semantic definitions of "alternate voice" and "stylistically offset" – this could cover emphasis, book/film names, key words, foreign phrases, etc. Incorrect use of the more specific semantic tags (eg. generating <em> when the user sets a film title to "italic") is worse than a lack of semantic detail.
HTML5 was designed with the understanding that not all web content can be authored by someone who knows the correct use of semantic HTML tags like <cite>, <em>, <strong>, <mark>, etc. Application-level copy can use those tags, but a rich text editor (for normal people) can't know which one is appropriate, so it should always default to the vague ones, <b> and <i>.
[+] [-] stesch|14 years ago|reply
[+] [-] MechanisM|14 years ago|reply
[+] [-] nabilt|14 years ago|reply
Edit: Redactor looks like it retains formatting for the HTML. That's enough to make me switch.
[+] [-] skyhook_mockups|14 years ago|reply
- No way of adding headings? * edit: sorry it's under styles.
- Clicking bold, italic etc should expand the selection to the word that the cursor is in.
- Setting formatting should restore the cursor to the editing area
- Clicking into a formatted area should toggle the buttons in the toolbar that apply
- image alignment a little clunky. Why not add a simple overlay for align centre|left|right on mouseover?
On the plus side image resizing is done well.
One thing that annoys me no end is that all editors I've ever used apply block level formatting (h1,2,3 etc) for an entire paragraph when only a sentence is selected. The most intuitive approach would be to break the sentence out of the paragraph and style only it. As a user I expect what I have highlighted to change not all of the surrounding text as well!
These things aren't easy to get right, especially cross browser. I recently put together an editor to exactly suit my needs (uses contenteditable instead of an iframe), but it's chrome, firefox and ie9+(? i think) only. Trying to get something usable across legacy browsers is ridiculously hard.
[+] [-] joe_the_user|14 years ago|reply
They were indeed hard to create and (at least then) relied on a detailed know of the browser and platform's characteristics.
But given the varying tasks which call for that kind of editor, what I'd really like to see is a small semi-standard tool or framework for the construction of such editors. As it is now, one must either use an existing tool having too many or too few features or go to the great lengths of modifying one.
[+] [-] phleet|14 years ago|reply
[+] [-] jabo|14 years ago|reply
[+] [-] JiPi|14 years ago|reply
This seems really promising at first. Would love to try it soon but it really needs a public repo. English documentation would be a great plus too! :)
[+] [-] jejacks0n|14 years ago|reply
Full disclosure, I'm the primary author.
[+] [-] websirnik|14 years ago|reply
[+] [-] fidz|14 years ago|reply
[+] [-] jakejake|14 years ago|reply
They do sometimes produce really terrible HTML though, especially because people copy/paste from MS Word and it results in a bunch of garbage.
[+] [-] alecperkins|14 years ago|reply
[+] [-] tvon|14 years ago|reply
[+] [-] antiterra|14 years ago|reply
[+] [-] kalininalex|14 years ago|reply
[+] [-] haydenchambers|14 years ago|reply
[deleted]
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] MechanisM|14 years ago|reply
[+] [-] dybskiy|14 years ago|reply
[+] [-] aichi|14 years ago|reply
[+] [-] rquantz|14 years ago|reply
[+] [-] godDLL|14 years ago|reply
[+] [-] matthewking|14 years ago|reply
Ran into a bug though, if you insert a table then return twice after it, all content below the table is removed..
[+] [-] josscrowcroft|14 years ago|reply