Soon to Be Released CKEditor 4 Features New Skin And Inline Editing

← Back to Stories (view on slashdot.org)

Soon to Be Released CKEditor 4 Features New Skin And Inline Editing

Posted by Unknown on Wednesday October 10, 2012 @04:52AM from the crawling-out-of-1999 dept.

PsxMeUP writes "CKEditor, one of the world's most popular WYSIWYG HTML editors, is getting a new default skin. The winner, Rafal Bromirski, will also receive $1000. The new design is going with the trendy monochrome look. The skin will be used with the soon-to-be-released CKEditor 4, which will feature inline editing." I recommend checking out the inline editing demo. Who needs textarea any more?

39 of 69 comments (clear)

Min score:

Reason:

Sort:

More Gray?? by Anonymous Coward · 2012-10-10 05:06 · Score: 2, Insightful

Seriously, what is wrong with color in a UI?
Monochrome by LihTox · 2012-10-10 05:07 · Score: 1

I for one will be glad when monochrome is passé; I'm surprised Google still has its multicolor logo, for all its embraced this trend. Vive les couleurs!
1. Re:Monochrome by SomePgmr · 2012-10-10 05:42 · Score: 1
  
  It seems the theme you use is entirely optional, and there's a bunch of very colorful ones there. ;)
Cool by pinkeen · 2012-10-10 05:07 · Score: 1

That's very good to know. It's about time this editor gets a decent look (the old incarnations were ugly to say the least).

In other news - I can see people misusing the inline editing feature. Tons of bugs and user frustration commencing in 3...2...1...
Slashvertisment? by Aguazul2 · 2012-10-10 05:08 · Score: 1

Trendy monochrome -- do they mean like my VT100? That's so trendy they'll still be imitating it 50 years from now.
Re:Slashvertising. by Anonymous Coward · 2012-10-10 05:09 · Score: 4, Informative

To simplify Open Source community involvement and development, CKEditor 4 is now hosted on GitHub, the popular git community site.
OK.
Re:Slashvertising. by Anonymous Coward · 2012-10-10 05:11 · Score: 5, Informative

It's an open-source project, fool, and a pretty darn good one.
Oh no! by FalMunir · 2012-10-10 05:15 · Score: 2

"Who needs textarea any more?" I do. I am writing this comment in VIM using the "I's All Text" extension for Firefox. I use my tool of choice (VIM) for almost everything I write, and I am not overjoyed with "solutions" trying to enforce other tools and behavior than the ones that help me the most. Freedom of choice is, at lest for me, very valuable.
1. Re:Oh no! by monkeyhybrid · 2012-10-10 10:06 · Score: 1
  
  Textareas do have the advantage of being accessible too, to those using screen readers and the like.
  Inline editing has lots of advantages too though, so maybe the perfect CMS way of doing things would be to have both options - inline editing for typical end users, and textarea (both plain and WYSIWYG replacements) for accessibility purposes.
CKEditor is like TinyMCE by Anonymous Coward · 2012-10-10 05:20 · Score: 1

CKEditor is like TinyMCE. Tiny has a lot better documentation and CK, formerly known as FCK, changed their inner workings a couple of years ago without having a solid stable branch. We changed to Tiny.
Noooooooooo! by sootman · 2012-10-10 05:27 · Score: 1, Insightful

Thank $DEITY this is an option. (It is an option, right?) A bit of color is a GOOD thing. With monochromatic icons, you need to inspect each icon carefully to discern its shape. With color, your eyes can quickly jump to the right one, especially if you've used it for a while. It just becomes automatic, like muscle memory.
The old icons were great. The ones that were just for text were black (bold, ital, underline, left/right/center). Text+decoration were black and colored (lists, indent, super/subscript). Separate functions (import from Word, clean up, spellcheck, table) were colorful. (As were "text color" and "highlight", FFS.)
This is NOT progress. :-|
Side note: Today I learned that "Noooooooooo" in a subject is OK, but one more "o" results in "Lameness filter encountered. Post aborted! Filter error: Too much repetition." Remember: Ten "O"s, kids. It's not just a good idea, it's the law.

--
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
1. Re:Noooooooooo! by interval1066 · 2012-10-10 05:39 · Score: 4, Insightful
  
  With color, your eyes can quickly jump to the right one...
  Which is great for people with color sight. As a colorblind person I can testify that this is of no use to me whatsoever. Now, before you 'color' (<- clever, no?) me an activist lemme just say that this is not a big deal to me, I'm comfortable in my disability and am not advocating some kind of radical, PETA-esque change in society. But your very first statement; "With monochromatic icons, you need to inspect each icon carefully to discern its shape.", well, sorry but I just don't find this to be too much of a burden. Yes, I do it as a matter of course. But do you REALLY need the extra help?
  
  I like the trend to less chromatic styles, its helps me and I believe it lends itself to a more streamlined, uniform look for all of us. Its hardly anything to get activist about, but like the 2nd law I tend to less complexity anyway.
  
  --
  Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
2. Re:Noooooooooo! by flimflammer · 2012-10-10 06:43 · Score: 2
  
  Well, the fact of the matter is that far more people are not colorblind than are. Those who are not can use these extra color hints to do what we want to do quicker. Do we absolutely need color? No, we don't, but that doesn't mean we should just forego color altogether when there is a proven benefit to it because ~9% of others can't discern the same differences. I know you said you aren't trying to make the whole societal change argument; I merely am responding to the piece of text suggesting we don't need the extra hints.
  I say this with the most respect to those who are colorblind. It's early in the morning (for me), so if anything I said reads as offensive, please understand that was entirely not my intent.
3. Re:Noooooooooo! by sootman · 2012-10-10 07:52 · Score: 3, Insightful
  
  I knew someone would bring this up. No, it's not much of a burden, but if color makes it better for fully-sighted people (who, by the way, greatly outnumber people with any amount or kind of color blindness -- not that we're therefore more important, it's simply a question of what does the most good for the most people) then why not leave it in? Plus it's not like I'm advocating making a TV louder, which would help a hearing-impaired person watch a show but would cause discomfort for others. If something helps one group and has no impact on another, why not do it?
  Totally blind people can't see icons at all. Does that mean the icons should be replaced with BOLD ITALIC UNDERLINE STRIKETHROUGH NUMBERED LIST BULLETED LIST INDENT OUTDENT SUBSCRIPT SUPERSCRIPT TEXT COLOR HIGHLIGHT COLOR MAKE LINK BREAK LINK LEFT ALIGN CENTER RIGHT ALIGN so you have the same experience a blind person has with a screen reader? After all, it's not much of a burden on you, right?
  That's what separates something that is merely "usable" from things that are truly "good" -- a thousand little details, all adding up to a better experience. Is this the end of the world? No. Is it a step backwards? Yes.
  
  --
  Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
4. Re:Noooooooooo! by sootman · 2012-10-10 07:58 · Score: 1
  
  > Try taking one of your existing colourful setups, randomise the icon
  > positions, then see how quickly you get used to the new layout. I'd
  > wager there wouldn't be much difference between that and getting
  > used to the new grey icons.
  I've already done that, effectively, and color is indeed key. I work with several rich text editors daily (personal blog, work CMS, school's LMS, and more, plus random web forms, blog comment forms, etc., in addition to Word, Excel, and other local apps) and each has a different layout. Having colors definitely helps me get around better. Switch them all to grey and I'd go nuts.
  
  --
  Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
5. Re:Noooooooooo! by monkeyhybrid · 2012-10-10 10:12 · Score: 1
  
  Yes, it's just an option. The monochrome theme is just one you can choose from and presumably the default as of this new version. You can choose a colour theme if you prefer, or make your own. Try the demo linked to in the summary, it uses a colour theme.
  The focus of this story shouldn't be the new theme (it looks nice to me but not really a big deal) but the new functionality this version brings, mainly being the inline editing.
6. Re:Noooooooooo! by interval1066 · 2012-10-11 02:48 · Score: 1
  
  Totally blind people can't see icons at all.
  Specious argument. The totally blind don't even figure into this caclulus, so I'm going to completely disregard your little "fit" and again argue that simplicity is a better way to go. Might as well get the shoe to fit as many people as possible in my opinion.
  
  --
  Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
7. Re:Noooooooooo! by sootman · 2012-10-11 06:07 · Score: 2
  
  You want things to be equally bad for everyone, whereas I want things to be as good as possible for as many as possible. Sorry, but your way makes no sense. Presenting colorful icons to colorblind users does not harm them in any way, but its an enhancement for fully-sighted users. Colorful icons don't "not fit" colorblind users. (Sorry for the double negative there -- not proper English but there's not a word that's the opposite of "fit".) This isn't like the difference between sounds that are too loud or not loud enough, or words that are long and confusing versus short and clear. There is no downside to using colorful icons, but there is an upside, therefore they should be used, if you're going for maximum usability.
  
  --
  Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
Aww man.. by Splat · 2012-10-10 05:37 · Score: 1

You're telling me I need to stop using HotDog to manage my websites?!
Re:Wrong. It's A Steaming Pile of Hell. by Anonymous Coward · 2012-10-10 05:40 · Score: 3, Informative

I'd MUCH rather use Notepad - not even Notepad2 or Notepad++, vim, pico, nano

This is an inline replacement for textarea. It has nothing to do with those.
Who needs it? by jez9999 · 2012-10-10 05:50 · Score: 1

Who needs textarea any more?
Slashdot?

--
== Jez ==
Do you miss Firefox? Try Pale Moon.
Re:Wrong. It's A Steaming Pile of Hell. by Dracos · 2012-10-10 05:50 · Score: 1

Every web WYSIWYG produces garbage markup, that's why I hate them. They're supposed to make HTML easier for plebians, but in reality they're given the power to make incomprehensible messes. Like handing a loaded shotgun to a toddler.
At least what CK produces (and FCK before it) is less fubar'd than what TinyMCE vomits out.
Inline editing is a recipe for an infinite amount of "I edited the page, and now it's broken" support requests. Only rabidly masochistic developers would even think of deploying it anywhere that a non-developer could access it.
Long live the textarea!
So what do I use on the Desktop? by Jonah+Hex · 2012-10-10 05:52 · Score: 1

Sometimes I just want to write a longer piece on my desktop before moving to the web and see a WYSIWYG HTML view. Right now I stick to PSpad on the desktop, WordPress HTML mode (not WYSIWYG), and Google Docs depending on what I'm typing up. I feel I'm missing an editor on Windows that handles HTML/CSS and publishing (preferably to WordPress) better than PSpad. - HEX

--
Horror & SciFi Erotic Nudes
1. Re:So what do I use on the Desktop? by CrashNBrn · 2012-10-10 10:47 · Score: 2
  
  CodeLobster PHP is the best that I've found. The editor itself is free, the devs charge a small fee if you want access to their plugins --- which include WordPress, Joomla, Drupal, among others.
  
  Some Features: code-highlighting, code-folding, auto-complete, tag-matching, regex search/replace.
  
  Default View is "code" but it also includes "Preview Mode" (WYSIWYG) and Inspector -- a mix between CodeView/Preview/FileView : personally I don't find Inspector all that useful, but the rest is decent.
  
  CLPHP can (as other editors I'm sure) quickly open a file with your browser of choice as well.
  
  The Open-Source Editors I've looked at for dealing with HTML/CSS/PHP are either plain buggy, not updated, missing significant features or just clearly don't do what they claim to at all. As well many of the best "text-editors" that are recommended for dealing with WebDevelopment don't do much more than code-highlighting - when it comes to the specifics of html/css/php et al.
  
  Adobe's Brackets (editor) looks interesting, but I haven't had time to mess around with it yet.
The inline editor is awesome! by dazedsnowboarder · 2012-10-10 05:58 · Score: 2

As an avid implementer of CKEditor, I've had several clients ask for the ability to edit content directly on a page. This new inline editor will make that possible. Can't wait for the release.
1. Re:The inline editor is awesome! by Lennie · 2012-10-10 14:51 · Score: 1
  
  I think the reason why this does not yet exist is because the builders of websites which support it don't want their images in the middle of the text. Browsers which support HTML5 do support drag&drop so I wouldn't be surprised if it is possible al though I'm not yet sure how that would integrate (well).
  
  --
  New things are always on the horizon
Re:Slashvertising. + Grammar Fail by Anonymous Coward · 2012-10-10 06:49 · Score: 2, Funny

Never heard of CKEditor and I could care less....
"could NOT care less". Please, if you're going to troll, do it properly.
Re:Wrong. It's A Steaming Pile of Hell. by houghi · 2012-10-10 06:59 · Score: 2

Inline editing is terrible if you give them ALL options.
First it has nothing to do with development. It has to do with content.
What we did was first disable anything that could be abused. This included almost anything. What was left was bullets, bold, the colors black and red and links. Also placing images was allowed.
Next we explained everybody how to use those things and had the amount of users limited. Never had an issue.
If it can break anything, then the developer did a shoddy job.

--
Don't fight for your country, if your country does not fight for you.
Very nice tool by dbk25 · 2012-10-10 07:58 · Score: 1

People where I work have been using CKEditor since before the name change to make it English-friendly. (That change made it much easier to describe to upper management.) It's very nice, and I'm looking forward to checking out the newest version.

Still, I can't help but look at the latest trend to blocky monochrome icons and flash back to Mac 64 and Windows 2.
Re:Louis CK has an editor? by dbk25 · 2012-10-10 08:01 · Score: 1

It happened when the editor's author, Frederico Caldeira Knabben, did not work so well as a product name in English.
Re:Louis CK has an editor? by dbk25 · 2012-10-10 08:07 · Score: 1

Um, I meant to say "his initials did not work so well...'
CKEditor smells like Cowboy Neal by Dogtanian · 2012-10-10 09:15 · Score: 1

When did this happen?
Much as I appreciate your humorous intentional misunderstanding, some people *might* think you're being serious and get the wrong idea. So let's clear this up...

"CKEditor" is the latest fragrance from Calvin Klein, the people who brought you "CKOne".

There- I hope that corrects any misleading impression given.

--
"Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
Re:Oh. Right. And I care because? by monkeyhybrid · 2012-10-10 09:43 · Score: 1

It can be persisted in exactly the same way as a WYSIWYG textarea replacement within a tradiitonal CMS does it - using Javascript and AJAX to pass the content to your backend. Makes very little difference whether the data comes from a textarea or from another DOM element / Javscript variable.
Lovely by TheCouchPotatoFamine · 2012-10-10 14:41 · Score: 1

LOVELY! your work is going to be everywhere, shortly. HTML5 is the future, afterall. You guys rock!

--
CS majors know the time/space tradeoff, but they never get taught the 3rd, crucial, tradeoff of the set: comprehension!
Re:Wrong. It's A Steaming Pile of Hell. by Lennie · 2012-10-10 14:47 · Score: 2

It is actually the browser that creates most of the garbage. The editor mostly uses an API to tell the browser that a certain part of the page is editable.

--
New things are always on the horizon
What does this do that Amaya doesn't? by Herve5 · 2012-10-10 21:26 · Score: 1

This is a sincere question, by a naive end-user...
http://www.w3.org/Amaya/
open-source, and efficient even to me...

--
Herve S.
1. Re:What does this do that Amaya doesn't? by Anonymous Coward · 2012-10-10 22:33 · Score: 1
  
  it runs in a browser
  amaya runs on the client
Re:Oh. Right. And I care because? by Tom · 2012-10-10 22:01 · Score: 1

And I've looked around their beta site for documentation showing me how to do it. Because, you know, CKEditor just might be most interesting to developers, who kind of like to see code and understand how the integration is going to work and all that.
But no. Lots of demos, no example of showing you how to do the AJAX calls. Uh... they DO have a built-in functionality for that, don't they? If I have to code all that up by hand, then please explain to me how this new feature makes it in any way better than using the current version and Jeditable ?

--
Assorted stuff I do sometimes: Lemuria.org
Re:Image drag and drop? by snadrus · 2012-10-11 08:09 · Score: 1

A quick test of the sample CKEditor 4 says no, it still visits your image in a "forward" like manner in Chrome (the browser first offering GMail attachment adds via drag-n-drop). The concept doesn't even work with inline editing since your editor disappears onBlur when you go get your image.

--
Science & open-source build trust from peer review. Learn systems you can trust.