On 01/29/2010 09:46 PM, Norbert Sándor wrote:
> Hello,
>
> I'm experimenting with the RichTextArea (RTA) in a separate application,
> not in XWiki.

Hi Norbert,

That is great, we've been waiting for other applications to try and 
integrate the editor, since so far only in theory can it be reused by 
external applications, nobody tried it. We hope that this goes smoothly 
and nothing serious prevents the integration, and we'll help each other 
to fix any issues.

> I checked out the xwiki-gwt-dom and xwiki-gwt-user, and RTA seems to
> work well. (Until now I've created only a small demo application, with
> an RTA and some buttons to execute various commands.)

We'd appreciate some feedback for this, like how much time did you spend 
so far, do you think it was easy or not to go this far, is the 
documentation good enough?

I'm not a developer of the WYSIWYG, so I won't be able to answer your 
questions, but Marius will help you as soon as he can.

> My questions are:
>
>     1. Pressing ENTER creates a BR element by default, is it possible to
>        create a P instead?
>        (The behaviour of the ENTER key inside a P can be set by executing
>        the insertbronreturn command, but the default document always
>        contains a BR, and if I set the initial content to<p></p>, I
>        cannot navigate the cursor inside the P...)
>
>     2. Is there a way to listen to selection events?
>        (I want to enable/disable some buttons based on the current
>        selection.)
>
>     3. Are there any extensions to the default RTA in the other parts of
>        XWiki?
>        (I mean for example commands and controls for editing TABLEs
>        visually, toolbars that are enabled/disabled based on the content
>        of the RTA, etc. - I haven't looked at all the source code yet,
>        it's huge :)
>
> That's for a starter :)
> Thanks for your help in advance!
>
> Best regards:
> --
> Norbert Sándor

I looked at your blog, and I saw this entry which I think we could 
benefit from in our build, since compiling the GWT code is the most 
resource consuming step in the build, except for running the integration 
tests.

Marius, could you take a look at
http://jvminside.blogspot.com/2010/01/gwt-2-debugging-and-compiling-faq.html 

I think that -XdisableCastChecking will improve runtime performance, and 
-draftCompile could be used in the default build profile for faster compile.

> http://jvminside.blogspot.com/

-- 
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to