I agree, CLeditor is wonderful, and I'm very happy to see what you
have planned next. All very great features.
1) <font> removal
Hip hip hooray. For my application, I'll be turning off the features
that cause this until your next release (here's looking at you, text
2) <p>s and <br>s
I support your vision here. Does this mean all of the <div>s will no
longer be inserted? Right now we end up with a lot of markup like
"Hello, <div><br></div><div>My name is Sven</div>" -- which is awfully
3) Youtube plugin
I'm interested to see what the community comes up with. Could be
4) Paste as Word
HELLS YES. Such a problem for my users. In order to kill the beast, we
must play along with its shenanigans for now.
5) button init callback
Not sure what the implications are of this.
1) queryCommandState logic for the buttons
A much desired UX tweak. It's disconcerting to not know if you've
selected something unless you start typing again.
2) keyboard shortcuts
This would be wonderful. If possible, replace Control with Command for
we Mac users.
3) resize grip
4) Icon plugin redesign
Don't use this and can't speak to it.
5) Image upload
This would be delicious. But. It needs to be very configurable on the
backend. Everyone probably wants to upload images differently. I want
to upload mine to Amazon S3. Patrick might want a blob in his
database. Unless I'm mistaken, no matter how you do this it's going to
require some interesting ajax acrobatics (tell me if I'm wrong!). So,
perhaps the best option would be:
* Make a configuration option called something like imageUploadPostURL
* Setting this option will enable the feature (without it set,
clicking the 'Image' button in the toolbar results in the current
* CLeditor will post the file specified by the user to the URL
specified in the imageUploadPostURL parameter
* CLeditor displays a loader wheel
* CLeditor receives a JSON response from the backend with an error
message if upload failed ("Only .jpg, .png, or .bmp files, por
favor!") or the image's URL if upload succeeded
* CLeditor displays the error message the user or inserts "<img
src=[returnedURL] />" into the document
This would be great. I haven't used i18n outside of Rails, though, and
I'm not sure how other folks tackle the problem. Rails has a config/
locales directory with files like "en.yml" and "es.yml" that all of my
to this directory, though... I don't know. I'll be interested to see
how the community tackles this.
Pretty pretty please move the project to Github? Personally, I'm more
familiar with Git, but I think we can *all* agree that Github is a
much nicer website than Gode. Also, anyone can clone the entire repo,
make modifications, and send you a pull request. Honestly, I'm not
familiar with Subversion and so I can't articulate why Git is better,
but I know some very good software developers who switched to Git and
And finally, thank you!
You're doing fantastic work here, and I'm very pleased to see the
direction you're taking it in. Spot-on. I am feeling well taken-care-
of in your hands, and I'll gladly lend you mine if I have the time and
know how to tackle something.