Hello,

>  We'd appreciate some feedback

I worked with the trunk versions of xwiki-gwt-dom and xwiki-gwt-user.
After checking them out, I slightly modified their poms (eg. removed the 
parent declaration), then I could use them in my small example project 
without problems.

I have much more difficulties with xwiki-web-wysiwyg, it seems to be 
more tightly coupled with xwiki functionalities. It's sad because the 
RichTextEditor and the plugin system would be very useful in external 
projects as well.
If you would split it to two projects, with the RichTextEditor and the 
plugin system in one of them, the resulting code base would be very well 
usable in external project as well. And seeing what you have already 
developed, it's a waste (in the good sense of meaning of course :) that 
this great editor is used only in xwiki. For example I think that many 
Java projects that use fckeditor (some of my projects as well) would 
happily switch to a gwt-based editor (and a cleaner Java-based plugin 
system). But I understand that it would need much work to support 
additional external requirements...

Best regards:
Norbi


2010.01.30. 6:03 keltezéssel, Sergiu Dumitriu írta:
> 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/
>>      
>    
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.733 / Virus Database: 271.1.1/2655 - Release Date: 01/29/10 
> 10:08:00
>
>    

_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to