Thoughts on <form> interoperability

[Todd Vierling]

Looks like CKEditor() puts the new instance into a (private)
FormPanel, which prevents keeping it in a real FormPanel and
interoperating with HTML forms.

Since CKEditor is meant to replace (and insert text into) a <textarea>
element, maybe CKEditor should make a FlowPanel be the <div>, and
expose some methods to pass through to the inner TextArea (e.g.,
HasName.*Name()).

(I am happy to contribute changes via svn, if you like. I am working
on integrating ckeditor with a social website that has on-demand
translation ability via Google Translate. I do plan on adding support
for file uploads in the future.)

[Damien Picard]

Hi Todd,

Yes, CKEditor is on a FormPanel, in order to intercept the submit event when clicking on the "Save" button. This is probably possible to avoid it, or optionnaly disable using this FormPanel when the user wants to.

Something like :

CKConfig c = new CKConfig();
c.useFormPanel(false);

Would lead to use a SimplePanel or a FlowPanel instead of FormPanel in the CKEditor instance.
Does this solution match with your needs ?

For the second point, yes, it is scopped to implements GWT's interfaces in order to be more convenient. Could you add this enhancement request to the Google Code issue tracker ?

If you want to contribute, could you send me a sample of your code, for example, could you implements HasName interface and send me it ? After review, I will add you to the contributors to allow you to send your modifications on the Subversion.

Thank you.

2010/2/24 Todd Vierling <t...@duh.org>

--
Damien Picard
Open Source BPM : http://code.google.com/p/osbpm