Interesting: just saw another post about stripping formatting from RichTextArea: http://groups.google.com/group/google-web-toolkit/browse_thread/thread/4dbf4aa4f7b455a1
The idea in that post is to catch Ctrl+V KeyDownEvent -- that would work in some cases and on some platforms, but would not catch all paste events, e.g. ContextMenu paste. Does anyone have a 100% reliable method of stripping formatting on pastes into a RichTextArea ? On Nov 4, 9:54 am, Bryan <[email protected]> wrote: > I also want only plain text to be pasted so that I can apply my own > styles to the text. > > The reason that I am looking at RichTextArea instead of a plain > TextArea is because I want the ability to show emoticons and TextArea > does not support anything like images with the text. > > I don't see a "PasteHandler" in RichTextArea -- is there some way to > catch the past operation and turn it into plain text? > > On Nov 4, 7:21 am, tskaife <[email protected]> wrote: > > > One problem I always had with RichTextArea was they way they handled > > text that was copied from a word processor. Word was specifically > > terrible adding 2000 characters of style for text that was 50 > > characters long. And it's ability to do crazy things like actually > > have scrolling marquees, that actually happened to us where someone > > made a marquee in word and pasted it into the RichTextArea and it > > actually worked. So cleaning up pasted text is a concern as well. We > > just end up using normal text areas because we want all styling to be > > consistent and not have yellow text with 40 pt font with a magenta > > background. > > > On Nov 3, 10:40 am, Martin Trummer <[email protected]> wrote: > > > > yes, this would eliminate the unification-step > > > > but some of the problems of integrating an external editor > > > (like my example of using TinyMce) will remain: > > > * not the native GXT look and feel > > > e.g. changing the GXT theme will not change the editors look > > > * integrating an editor to work nicely with GXT-Form-Layouts > > > is tricky and sometimes the layout is completely messed up > > > * the communication between GXT-Form-Fields needs do be done > > > > I guess most of these problems can be solved (or worked around) > > > if you dig deep enough into GXT > > > > however, it is of course a nice alternative for anyone who is > > > using plain GWT > > > > On Nov 3, 12:53 pm, Thomas Broyer <[email protected]> wrote: > > > > > On 3 nov, 12:25, Martin Trummer <[email protected]> wrote: > > > > > > If you are using or are planing to use GWTs RichTextArea (or GXTs, > > > > > which is basically the same), then the following blog post may be > > > > > interessting for > > > > > youhttp://martin-trummer.blogspot.com/2009/11/wysiwyg-gotchas.html > > > > > > I am already keen to get to know your point of view about > > > > > * this topic > > > > > * the problems, that I've outlined > > > > > * any proposals, improvements or > > > > > * or better solutions than mine > > > > > Use CKEditor? from what I've read (haven't used it yet), you have a > > > > total control over the "serialization" (at the expense of not relying > > > > on the browser's innerHTML) and it already unifies the HTML produced > > > > by the rich text area. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
