Thank you for the sponsorship Rishi :). I hope you're okay with the clarified direction here - upgrading Kama. Our designer should have some free time and does great icon work, so it is very viable for us to go in that direction.

Happy to be part of this :)
Yes, this direction is fine, though I'll want to learn how to switch between skins so that I can compare both, see how they are on the eyes.

Potentially we can add it to the new WYSIWYG tutorial, how to switch out skins. The office skin they have is very nice too.

We should do retina for our own icons, but may need changes in ckeditor for it:
http://dev.ckeditor.com/ticket/12932

I've had a play with skins. Switching skins is pretty easy already. I tried a few and like kama (what we have now), moono, and moonocolor. On testing the office skin looked out of place.

1) place the skin files in data/ckeditor/skins/
2) edit the WYSIWYG_SETTINGS.tpl template change..
var editor_settings={
to:
var editor_settings={
skin: 'moono',

(i.e. add a line, obviously use the correct skin name)

3) empty the template cache manually if you didn't do the template edit from within Composr (JAVASCRIPT_EDITING.tpl needs decacheing).

We've done the superset of this.

The new default theme will be moono.

We have submitted Retina support for Kama upstream:
http://dev.ckeditor.com/ticket/12918

Generally we've worked on improved documentation, including how to switch skins. So the new Kama could be dropped in when upstream releases it.

I don't want us to fork CKEditor to get the improved Kama in immediately, I'd rather do this via a cooperative model.

Thanks Chris. I followed the instructions above for using moono, however the area comes up blank. No editor interface at all.

Ah. It's a version issue. Your CkEditor is 3.6, the earliest Moono release is 4.0. Once we deliver all the editor updates in one go, we'll do it with a reasonably recent CKEditor version too.