Re: Old issues in the RichTextEditor
On 6 feb, 22:50, Sumit Chandel wrote:
> Hi Vicente,
> Thanks for bumping this up. In aggregate, it seems that there are a few
> developers that are waiting for these enhancements to RichTextEditor, so
> these are definitely important to consider as we roll out future releases.
nice...
> I particularly bumped up Issue #1433 so the team gets to take a look at
> investigating it before a final 1.6 release. It seems like having support
> for setting innerHTML would solve the most use cases in one fix.
I agree.
> Finally having said that, you know our motto, "Patches welcome!".
I know. I started adding
public void insertHtml(String html) {
execCommand("InsertHtml", html);
}
in RichTextAreaImplStandard that works in Mozilla, but sadly I don't
have resources/capacity to do and test the same in other browsers.
Thanks Sumit,
Vicente
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---
Re: Old issues in the RichTextEditor
Hi Vicente, Thanks for bumping this up. In aggregate, it seems that there are a few developers that are waiting for these enhancements to RichTextEditor, so these are definitely important to consider as we roll out future releases. I particularly bumped up Issue #1433 so the team gets to take a look at investigating it before a final 1.6 release. It seems like having support for setting innerHTML would solve the most use cases in one fix. That said, the reason why some issues go stale for as long as you pointed out in this thread is due to prioritizing the hardest hitting bugs and new features first, and dedicating effort to make sure those get shipped on time. I'm glad that you brought up this thread since it gives the community a chance to cast votes for RTE issues, a metric that we depend on for prioritizing bugs/features. Finally having said that, you know our motto, "Patches welcome!". If anyone who does encounter these issues comes up with a good fix for their own purposes, it would be great to contribute that back to GWT to get quicker turnarounds on issues that the team might no have yet had a chance to work on. Cheers, -Sumit Chandel On Wed, Feb 4, 2009 at 4:12 AM, vruiz.jur...@gmail.com < vruiz.jur...@gmail.com> wrote: > > Hi, > > I write to ask if the dev team can put some attention in the old > issues of the RichTextEditor (RTE): > > http://code.google.com/p/google-web-toolkit/issues/list?can=2&q=RichtextArea > and also to ask if others can vote/star these issues. > > For instance, we fill this bug in july-2007: > http://code.google.com/p/google-web-toolkit/issues/detail?id=1433 > > related with: > http://code.google.com/p/google-web-toolkit/issues/detail?id=2425 > > and without InsertHtml, and without set/getCurPosition like in > TextAreas: > http://code.google.com/p/google-web-toolkit/issues/detail?id=1127 > http://code.google.com/p/google-web-toolkit/issues/detail?id=2182 > > you can't insert neither a simple #historytoken href: > http://code.google.com/p/google-web-toolkit/issues/detail?id=3318 > in a text you are editing. > > Neither, any html elements. Just simple plain and > without > any styling or attribute. > > Other important issues from my point of view related to RTE: > http://code.google.com/p/google-web-toolkit/issues/detail?id=1052 > http://code.google.com/p/google-web-toolkit/issues/detail?id=3123 > > From the outside, seems like the code of the RTE is very stalled these > years. > > TIA, > > > Vicente J. Ruiz Jurado > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Old issues in the RichTextEditor
Hi, I write to ask if the dev team can put some attention in the old issues of the RichTextEditor (RTE): http://code.google.com/p/google-web-toolkit/issues/list?can=2&q=RichtextArea and also to ask if others can vote/star these issues. For instance, we fill this bug in july-2007: http://code.google.com/p/google-web-toolkit/issues/detail?id=1433 related with: http://code.google.com/p/google-web-toolkit/issues/detail?id=2425 and without InsertHtml, and without set/getCurPosition like in TextAreas: http://code.google.com/p/google-web-toolkit/issues/detail?id=1127 http://code.google.com/p/google-web-toolkit/issues/detail?id=2182 you can't insert neither a simple #historytoken href: http://code.google.com/p/google-web-toolkit/issues/detail?id=3318 in a text you are editing. Neither, any html elements. Just simple plain and without any styling or attribute. Other important issues from my point of view related to RTE: http://code.google.com/p/google-web-toolkit/issues/detail?id=1052 http://code.google.com/p/google-web-toolkit/issues/detail?id=3123 >From the outside, seems like the code of the RTE is very stalled these years. TIA, Vicente J. Ruiz Jurado --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
