It looks like you're not getting your onChange event to fire at all, since it's failing to even display your alerts.
This would appear to be a CKEditor issue rather than a SmartGWT issue per se.
Obviously that's really a question to bring to the CKEditor folks but from a quick google search it appears you need to install the onChange add-on to make this work, if you haven't already.
Note that if you are able to get onChange to fire for your CKEditor outside of the SmartGWT integration, but somehow the process of wrapping it in a SmartGWT widget is breaking things, we could possibly take a look. We'd essentially need to see a little sample we could run on our end demonstrating the failure case (probably with a sample demonstrating the working case as well so we can analyze what is going wrong).
Other than that - if you ultimately can't get a proper change notification from CKEditor to fire at all, you could also take another approach to determine when to update the form value.
A couple of possibilities that come to mind: You could use a "blur" notification to store out the value when the user takes focus from the editor, if that is available.
Or you could modify your UI to (for example) show the CKEditor in a pop up modal window, and have the user click a standard SmartGWT "Done" button to complete their edit, which would both dismiss the editor and fire the "storeValue()" method, updating the form values.
This would appear to be a CKEditor issue rather than a SmartGWT issue per se.
Obviously that's really a question to bring to the CKEditor folks but from a quick google search it appears you need to install the onChange add-on to make this work, if you haven't already.
Note that if you are able to get onChange to fire for your CKEditor outside of the SmartGWT integration, but somehow the process of wrapping it in a SmartGWT widget is breaking things, we could possibly take a look. We'd essentially need to see a little sample we could run on our end demonstrating the failure case (probably with a sample demonstrating the working case as well so we can analyze what is going wrong).
Other than that - if you ultimately can't get a proper change notification from CKEditor to fire at all, you could also take another approach to determine when to update the form value.
A couple of possibilities that come to mind: You could use a "blur" notification to store out the value when the user takes focus from the editor, if that is available.
Or you could modify your UI to (for example) show the CKEditor in a pop up modal window, and have the user click a standard SmartGWT "Done" button to complete their edit, which would both dismiss the editor and fire the "storeValue()" method, updating the form values.
Comment