You could let them write Java code instead and run it in the server only
using BeanShell2. Then the syntax and interoperability issues go away. But
you have to send results to the client rather than calculating directly on
the client.
HTH
Paul
--
You received this message because you are subscri
Thax you very much Thomas, I understand now cos we already generate gwt
Java code into Javascript so we don't need them right. Ok I got it
On Sunday, May 11, 2014 7:22:24 AM UTC+10, Thomas Broyer wrote:
>
>
>
> On Friday, May 9, 2014 2:28:37 PM UTC+2, Tom wrote:
>>
>> Hi Thomas, I got gwt-dev.jar
On Friday, May 9, 2014 2:28:37 PM UTC+2, Tom wrote:
>
> Hi Thomas, I got gwt-dev.jar & gwt-user-2.5.0.jar in
> myApp\war\WEB-INF\lib. The reason is that is i don't have these 2 jar files
> in myApp\war\WEB-INF\lib, then everytime I run myApp in Eclipse, eClipse
> warning that it can find class
Thank you. I appreciate the time that you and others put into this group
(and GWT in general).
It took some more bumbling around, but I found it worked with two additions
(highlighted below):
...
cargo {
containerId = 'jetty9x'
port =
deployable {
file = tasks.draftWar.archivePa
I am writing a GWT app that will be usable by multiple customers. I'd like
for my customers to be able to customize the app, both on the server side
and client side by writing JavaScript. In other words, they could do things
like:
- Set some configuration for their site, like its name, their we
