> I have no opinion so far since I've not used GWT yet.
>
> My only opinion: make sure to choose a framework that has a good
> community (# of different committers), active (check mailing list
> activity), good support (check mailing list activity), and that is the
> de facto choice of people using GWT.
>
> However before changing, it seems that GWT TK support GWT 1.4, see
> http://groups.google.com/group/gwt-tk/browse_thread/thread/8025767946742c52

Is a nightly build with no planned / announced release ok to use as
dependency in a platform module?

However, it seems that gwttk does not match all the the framework
requirements you have mentioned above so it might not be a bad idea to get
rid of it anyway...

>
> Thanks
> -Vincent
>
> On Feb 26, 2008, at 11:20 PM, [EMAIL PROTECTED] wrote:
>
>> Hi devs,
>>
>> We have planned the GWT 1.4 upgrade for the next XWatch milestone at
>> the
>> end of march. For this, we need to make a decision regarding the web-
>> gwt
>> dependencies (for the moment, the xwiki gwt dialogs rely on the gwt-tk
>> library that does not yet have a release for gwt 1.4) so we must
>> choose
>> from:
>> - using another library to provide this functionality, particularly
>> the
>> MyGwt library
>>      pros: nice looks and good API + the possibility of using the library
>> components in including projects.
>>      cons: code changes required by the clean switch (updating all
>> involved
>> classes to use library API instead of GWT API), the lack of a maven
>> repository with all available MyGwt versions (only 0.5.0 rc). As well,
>> while testing, I experienced a couple of rendering issues (caused,
>> seemingly by the use of the strict or xhtml DTD).
>> - using the native gwt modal dialogs introduced in 1.4:
>>      pros: not styled (we totally control the styling process and can
>> build an
>> uniform look); widgets consistency, at least at this level. A big
>> advantage is that the web-gwt module will not depend on any other
>> library
>> anymore.
>>      cons:  not styled, the usual GWT API (which can be poor in some
>> situations); GWT also has some problems caused by the standard mode
>> interpretation in browsers (caused by the doctype declaration) but in
>> this situation the code seems to be stable.
>>
>> What do you think?
>
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>


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

Reply via email to