15 Jan
2008
15 Jan
'08
12:45 p.m.
I would suggest to have extjs implemented for ajax.
Reasons already mentioned below.
File size is not an issue as it needs to be loaded only once.
I have done some work on albatross skin to replace the default template
layout with extjs border layout for my local wiki.
One thing you need to take care is that there may be some other js files
whose execution might conflict with ext-base.js execution.
For my implementation I had to comment out all the other js that were
getting loaded.
Also another cool thing would be to integration extjs with jquery. This
combination can lead to some rich UI.
I have not yet tested the gwt web interface with xwiki, but not sure if
anyone has combined extjs with gwt, also from the version 2.0 of extjs I
don't see any adapter for gwt.
Thanks
Sachin
----------------------------------------------------------------------
Message: 1
Date: Mon, 14 Jan 2008 21:31:38 +0100
From: "Luis Arias" <kaaloo(a)gmail.com>
Subject: Re: [xwiki-devs] upgrade to gwt 1.4
To: "XWiki Developers" <devs(a)xwiki.org>
Message-ID:
<26d206520801141231y6a673686r27f168685efd2a3d(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi J?r?me,
You might also consider MyGWT:
http://mygwt.net/
if you're worried about the ext.js lib. It's a native implementation.
For Curriki, there may be some issues with gwt-html-editor which in
its 1.4 branch just brings up Fck Editor. I had some issues using
gwt-html-editor trunk in 1.4.61.
Luis.
On Jan 14, 2008 9:55 AM, Jerome Velociter <jerome(a)xwiki.com> wrote:
--
Luis Arias
+33 6 14 20 87 93
skype : kaaloo
------------------------------
> 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