Luis.
 On Jan 14, 2008 9:55 AM, Jerome Velociter <jerome(a)xwiki.com> wrote:
   Hi all,
 we want to upgrade XWiki Web gwt to gwt 1.4 for the 1.3 version so, 
 since
  gwttk does not have a version for gwt 1.4 and we
depend on it for 
 creating
  modal dialogs, we need to replace tk with
something else. A good 
 option is
  gwt-ext, which also can replace gwt-widgets and
provides some more 
 nice ui
  objects and client functionality (like date
parsing -- which we get 
 from
  gwt-widgets for the moment).
 The trouble with gwt-ext is that it requires ext javascript library to
 run, which means that any gwt application needs to import, besides the
 gwt.js file, some ext javascript files. Since the modal dialogs are
 defined in the web-gwt module (so our gwt-ext dependency is there) and 
 we
  cannot import the ext javascript files at that
level, the only 
 solution is
  to rely on the application using web-gwt to
include right all required
 files. It doesn't seem to me as good practice but I cannot figure out 
 how
  big of an issue it is (since that application
already has some rules 
 to
  obey, js files to include, etc to have gwt
working).
 
 IMO,
 Pros for migrating to ext, vs. sticking to gwttk:
 - larger community, visibility on roadmap
 - lots of widgets/functionnalities available (datepickers, form
 validation, etc.)
 - gwt 1.4 already compatible
 Cons:
 - every app has to import ext JS scripts in addition to gwt.js
 - increases total JS size
 It would be great to have opinions from the Curriki development team on
 the topic.
 Regards,
 Jerome.
  WDYT?
 _______________________________________________
 devs mailing list
 devs(a)xwiki.org
 
http://lists.xwiki.org/mailman/listinfo/devs
 
 _______________________________________________
 devs mailing list
 devs(a)xwiki.org
 
http://lists.xwiki.org/mailman/listinfo/devs
  
 --
 Luis Arias
 +33 6 14 20 87 93
 skype : kaaloo
 _______________________________________________
 devs mailing list
 devs(a)xwiki.org