Timer and Scheduler.scheduleDeffered would not be expected to be
equivalent. They have two different semantics.
Scheduler.scheduleDeffered - runs after the browser event loop returns.
new Timer().schedule(1000) - runs 1000 ms after being scheduled.
You can not expect
It is clear that Timer and Scheduler are different.
My concern is that Scheduler.scheduleDeffered behaves so differnent on
different platforms.
What is the best way to handle this?
Am Mittwoch, 26. November 2014 16:11:01 UTC+1 schrieb Jonathon Lamon:
Timer and Scheduler.scheduleDeffered
@confile it is not possible to run your example because it is missing
dependencies.
From reading the code, the problem you are having is probably not caused by
the Scheduler but by the time taken to resolve test.jpg. After modifying
an element it is not necessary to pause before calling
Richard what do you suggest to solve this problem?
Am Mittwoch, 26. November 2014 19:01:02 UTC+1 schrieb Richard Wallis:
@confile it is not possible to run your example because it is missing
dependencies.
From reading the code, the problem you are having is probably not caused
by the
Guessing but you can probably use image addLoadHandler() to wait for the
image to load before checking the height.
A more complex alternative is to download the image using a getRequest and
then transform it into a base64 dataUrl and use that as the src for your
image.
On Wed, Nov 26, 2014 at
Have you forgot to use the -XjsInterop parameter when starting SDM?
-- J.
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
@Jens you where right I was missing the -XjsInterop in SDM I had it only
set for compile. Thank you.
Am Sonntag, 2. November 2014 20:00:19 UTC+1 schrieb Jens:
Have you forgot to use the -XjsInterop parameter when starting SDM?
-- J.
--
You received this message because you are
1) gwt-jscore is a small Implementation of DOM Element and JS functionality
standard, this is a test, This project will not be Necessary When is
Implemented Elements 2.0, but for the moment I need this.
Many things about this project can change as conforming JsInterop.
For example:
The
I have been testing JsInterop for a while, and is very promising ...
The issue of static functions is something I have asked, and we have to
wait Java support 8 and the new JSNI too.
@confile, if you want to look at a couple of projects on which I am working:
- gwt-jscore
@Christian:
1. What does gwt-jscore do?
2. as Ray Cromwell suggested in this post In general, native DOM elements
== no $wnd prefix, JS libraries loaded in host page == $wnd prefix
This means your JQueryElement
Great thank you Katharina. It works fine.
When my code server starts I get the following output:
Turning off precompile in incremental mode.
Super Dev Mode starting up
workDir:
/var/folders/xh/1xkfq26532j97q23qw5pdhs4gn/T/gwt-codeserver-7987266074037967516.tmp
What does it mean?
Compilation takes about 0,099s when there is nothing to recompile. It still
takes a lot of time to send the files to my phone. In my case Safari
console showns that 12,7MB are transferred after each reload.
Am Montag, 27. Oktober 2014 17:17:10 UTC+1 schrieb Katharina Fahnenbruck:
Hi,
here
Compilation takes about 0,099s when there is nothing to recompile. It
still takes a lot of time to send the files to my phone. In my case Safari
console showns that 12,7MB are transferred after each reload.
The size is normal as no optimizations are done. Maybe you are better off
using
For me it turns out that GWT 2.7 is much faster in compiling but much
slower in loading the app than GWT 2.6.1.
Am Montag, 27. Oktober 2014 18:42:33 UTC+1 schrieb Jens:
Compilation takes about 0,099s when there is nothing to recompile. It
still takes a lot of time to send the files to my
One option is to get source-map support improved
directly in Eclipse/IntelliJ, so that the Javascript-based developer
tools are not used, rather, the IDEs connect to the Browsers via
remote debugging protocols, but the SourceMap/indexing/navigation is
done by Eclipse/IntelliJ.
A
Our application is roughly the same size (3.5mb) and I have never been able
to debug using source maps in firefox. It freezes when it has to load them.
I have also tried remote javascript debugging with super devmode from
IntelliJ. I can typically step over a couple of breakpoints and then it
Thank you for that, but right know my main target is to move our projects
to GWT 2.7 and migrate our developers to SDM.
Regards,
Matic
On Tuesday, October 21, 2014 8:50:01 PM UTC+2, Brandon Donnelson wrote:
Ah, thanks for sharing. I just wanted to double check. By the way if
you're
Hi Brandon,
The GWTP plugin has GPE as a dependency. Can you send me a link to the
preview please.
On Wed, Oct 22, 2014 at 5:16 PM, Matic Petek maticpe...@gmail.com wrote:
Thank you for that, but right know my main target is to move our projects
to GWT 2.7 and migrate our developers to SDM.
Post 2.7, we're going to look into pruning down the incremental
output. However, this won't solve poor sourcemap implementations in
other browsers. One option is to get source-map support improved
directly in Eclipse/IntelliJ, so that the Javascript-based developer
tools are not used, rather, the
Good point. When I tried remote js debugging with sourcemaps from intellij I
thought about the irony og the setup.
You have the source in your IDE. Then you push the source and mappings to the
compiled output into the browser, and then you remote control the debugger from
the IDE.
It would be
We're planning to do some work (link time pruning) to reduce incremental
output size some time before the end of the year.
On Wed, Oct 22, 2014 at 9:33 AM, Rene Hangstrup Møller rhmol...@gmail.com
wrote:
Good point. When I tried remote js debugging with sourcemaps from intellij
I thought about
I have superdevmode-launcher-legacy.jar in classpath and it is not
compatible with GWT 2.7.
Regards,
Matic
On Friday, September 5, 2014 5:40:55 PM UTC+2, Brandon Donnelson wrote:
I suspect the sdk isn't what you think it is if its not working. Can you
check the classpath and see if it was
You shouldn't put never that .jar in your classpath.
GPE takes care of adding it to the launcher classpath when you run
superdevmode and your gwt is not 2.7.
On Tue, Oct 21, 2014 at 2:31 PM, Matic Petek maticpe...@gmail.com wrote:
I have superdevmode-launcher-legacy.jar in classpath and it is
Manolo is correct, the superdevmode-launcher-legacy.jar is not needed with
GWT 2.7. It can be used with GWT 2.5.x and 2.6.x.
Did you add that to the classpath?
Brandon
On Tuesday, October 21, 2014 6:03:14 AM UTC-7, Manuel Carrasco Moñino wrote:
You shouldn't put never that .jar in your
Yes, it was my mistake when I upgrade from 2.6 to 2.7 snapshot. Not it is
working. I just want to write it in forum if someone else would have the
some problem... Thank you for help.
Regards,
Matic
On Tuesday, October 21, 2014 6:41:11 PM UTC+2, Brandon Donnelson wrote:
Manolo is correct,
Ah, thanks for sharing. I just wanted to double check. By the way if you're
interested in the GPE preview, I've got that handy if you want to try it
out.
On Tuesday, October 21, 2014 10:00:54 AM UTC-7, Matic Petek wrote:
Yes, it was my mistake when I upgrade from 2.6 to 2.7 snapshot. Not it
Thanks! I will try both ways!
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this
Hi,
we currently have a jenkins job that checks out the gwt code from github,
applies the patch and build GWT.
FYI, we did not have any issue regarding this patch for more than a year.
It would be awesome to be using an official release of GWT.
Thanks
Le mercredi 8 octobre 2014 20:49:02 UTC+2,
Build GWT from source if you want to play around with it. You need to:
1.) mkdir gwt cd gwt
2.) git clone https://gwt.googlesource.com/gwt trunk
3.) svn checkout http://google-web-toolkit.googlecode.com/svn/tools tools
4.) cd trunk ant dist-dev
This builds GWT without samples and you can then
We are making steady progress towards GWT 2.7. At this point we are not
accepting any new patches, but we still have a list of issues that we would
like to include in the upcoming release. This is no guarantee that all of
them are going to make it but we are trying our best. Also we are holding
On Thursday, October 9, 2014 3:25:37 PM UTC+2, Daniel Kurka wrote:
We are making steady progress towards GWT 2.7. At this point we are not
accepting any new patches, but we still have a list of issues that we would
like to include in the upcoming release. This is no guarantee that all of
Any chance that Patch 9450 https://gwt-review.googlesource.com/#/c/9450/ for
speeding up the intial start time of SDM will make it?
On Thursday, 9 October 2014 15:04:21 UTC+1, Thomas Broyer wrote:
On Thursday, October 9, 2014 3:25:37 PM UTC+2, Daniel Kurka wrote:
We are making steady
Lots of Elemental patches have been merged in the last few days, but we do
still have a short list that would be nice to get included.
https://gwt-review.googlesource.com/#/c/9098/
https://gwt-review.googlesource.com/#/c/9099/
https://gwt-review.googlesource.com/#/c/9095/
The code appears to
I think this is okay as long as it doesn't cause tests to fail. Elemental
is quite separate from everything else so it seems low risk. Daniel?
On Thu, Oct 9, 2014 at 8:57 AM, Leif Åstrand legi...@gmail.com wrote:
Lots of Elemental patches have been merged in the last few days, but we do
still
I think this call is up to the elemental maintainers (manolo thomas), if
it breaks any tests I will roll it back since we need a green build to be
able to branch.
-Daniel
On Thu, Oct 9, 2014 at 6:57 PM, 'Brian Slesinsky' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com
Well, actually there is no official maintainer for elemental, so Ray would
be the most suitable since he introduced elemental to GWT, but as Goktug
said in this thread, he might not have enough time.
What I've tried to do in my patches is to make the existent elemental test
suite run and pass.
On Thursday, October 9, 2014 10:43:38 PM UTC+2, Roberto Lublinerman wrote:
I think we will better exclude the following three patches from the
release 425e0bb 2b2d81c 920ba90
I will either revert them or fix them with a better alternative. Java
RegExp implementation is really rough
+1 for John's patch 9450 https://gwt-review.googlesource.com/#/c/9450/ (
sorry to devolve the thread into +1's )
On 9 October 2014 14:04, Thomas Broyer t.bro...@gmail.com wrote:
On Thursday, October 9, 2014 10:43:38 PM UTC+2, Roberto Lublinerman wrote:
I think we will better exclude the
On Thu, Oct 9, 2014 at 7:04 AM, Thomas Broyer t.bro...@gmail.com wrote:
On Thursday, October 9, 2014 3:25:37 PM UTC+2, Daniel Kurka wrote:
We are making steady progress towards GWT 2.7. At this point we are not
accepting any new patches, but we still have a list of issues that we would
Hi Daniel,
this issue (
https://code.google.com/p/google-web-toolkit/issues/detail?id=8938) should
be included in GWT 2.7.
Best
Michael
Am Mittwoch, 1. Oktober 2014 21:15:26 UTC+2 schrieb Daniel Kurka:
Hi all,
we just settled on a GWT 2.7 release plan:
- We *code freeze* on *October
Hi,
thank you all for your hard work. We have been using GWT and SDM with great
success in a big financial software company :).
There is one major feature that is still not merged : NavigableMap
https://gwt-review.googlesource.com/#/c/3650/
Will it be possible to have it in the 2.7 realease ?
There are a few things we need to do. I will talk with Andrei and see if we
can make it.
On Wed, Oct 8, 2014 at 7:54 AM, hypn...@donarproject.org wrote:
Hi,
thank you all for your hard work. We have been using GWT and SDM with
great success in a big financial software company :).
There is
On Wednesday, October 8, 2014 6:49:30 PM UTC+2, Marcio Alves wrote:
Hi!,
Is there a easy way to download the GWT 2.7 SDK to help with the tests?
Thanks!
There are snapshots deployed nightly (when the build is green) to
https://oss.sonatype.org/content/repositories/google-snapshots/
If you need an Historian implementation that uses pushstate, have a look
at https://gist.github.com/tbroyer/1883821
Used in production for quite some time in a project at work (though limited
to Firefox ESR clients; it's in an intranet/extranet context)
On Friday, October 3, 2014 6:51:51 PM
I tested JSInterop a lot. According to the design document
https://docs.google.com/document/d/1tir74SB-ZWrs-gQ8w-lOEV3oMY6u6lF2MmNivDEihZ4/edit#you
could do something like:
@JsType
interface MyJsInterface {
void callMeLater(@Entry Callback x);
}
But, the @Entry annotation is not
Will you update to Jetty 9.2 (with JVM 8 support)?
Any link to branch version?
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
1.- History mechanism has changed in 2.7 to fulfil modern standards
https://gwt-review.googlesource.com/#/c/5356/. BTW: you should't use
HistoryImpl and in general any Impl class, in general they are private API
2.- Use -XjsInteropMode ONLY in the case that you have a need for
exporting gwt
Well, I need to override HistoryImpl to enable HTML5 pushstate api.
Am Freitag, 3. Oktober 2014 16:01:31 UTC+2 schrieb Manuel Carrasco Moñino:
1.- History mechanism has changed in 2.7 to fulfil modern standards
https://gwt-review.googlesource.com/#/c/5356/. BTW: you should't use
There is no plans to upgrade Jetty. It implies some changes in
JettyLauncher and WebServer, I have already a patch for that but not
committed yet because I have not tested enough. If someone else demands it
we could consider to upgrade it.
Anyway I think it should be nice not to bundle jetty in
On Fri, Oct 3, 2014 at 4:05 PM, confile michael.gorsk...@googlemail.com
wrote:
Well, I need to override HistoryImpl to enable HTML5 pushstate api.
HistoryImpl is now a private class inside History, maybe we could discuss
whether to change its visibility. Maybe @Daniel could help here.
Am
On Friday, October 3, 2014 4:09:33 PM UTC+2, Manuel Carrasco Moñino wrote:
On Fri, Oct 3, 2014 at 4:05 PM, confile michael.gorsk...@googlemail.com
wrote:
Well, I need to override HistoryImpl to enable HTML5 pushstate api.
HistoryImpl is now a private class inside History, maybe we
Well if you do not use Places for example when you use GWTP you need the
HistoryImpl to make GWT-pushstate working.
Am Freitag, 3. Oktober 2014 17:11:35 UTC+2 schrieb Thomas Broyer:
On Friday, October 3, 2014 4:09:33 PM UTC+2, Manuel Carrasco Moñino wrote:
On Fri, Oct 3, 2014 at 4:05
Hi Thomas,
Please can you link to the discussion where you decided it was ok to break
compatibility with deferred binding implementations of the HistoryImpl.
On Fri, Oct 3, 2014 at 5:15 PM, confile michael.gorsk...@googlemail.com
wrote:
Well if you do not use Places for example when you use
It would be great if you describe a workaround not having HistoryImpl and
using gwt-pushstate when not using places.
Am Freitag, 3. Oktober 2014 17:25:10 UTC+2 schrieb Richard Wallis:
Hi Thomas,
Please can you link to the discussion where you decided it was ok to break
compatibility with
Hi Thomas,
Please can you link to the discussion where you decided it was ok to break
compatibility with deferred binding implementations of the HistoryImpl.
See comments in https://gwt-review.googlesource.com/#/c/6403/
-- J.
--
You received this message because you are subscribed to
Ok so gwt 2.7 is going to provide pushstate functionality so we don't need
the 3rd party libraries?
On Fri, Oct 3, 2014 at 5:47 PM, Jens jens.nehlme...@gmail.com wrote:
Hi Thomas,
Please can you link to the discussion where you decided it was ok to
break compatibility with deferred binding
It would be great if you describe a workaround not having HistoryImpl and
using gwt-pushstate when not using places.
There is no real workaround other than building a class on your own that
either uses GWT History for hash fragments or pushState if available. With
GWT Places that would be
Ok so gwt 2.7 is going to provide pushstate functionality so we don't need
the 3rd party libraries?
It only uses pushState internally and does not expose any API for it. So
no, you would still need a library or JSNI to use pushState.
-- J.
--
You received this message because you are
Can you not define an interface for HistoryImpl so that we can replace it
while you still keep your implementation private?
On Fri, Oct 3, 2014 at 5:52 PM, Jens jens.nehlme...@gmail.com wrote:
Ok so gwt 2.7 is going to provide pushstate functionality so we don't need
the 3rd party libraries?
On Friday, October 3, 2014 6:19:30 PM UTC+2, Richard Wallis wrote:
Can you not define an interface for HistoryImpl so that we can replace it
while you still keep your implementation private?
No, because we specifically don't want to make it a public API where we
have to maintain backwards
On Friday, October 3, 2014 5:15:51 PM UTC+2, confile wrote:
Well if you do not use Places for example when you use GWTP you need the
HistoryImpl to make GWT-pushstate working.
As far as I can see form the code, GWTP's PlaceManager is pluggable
(sort-of) and could probably replaced with a
Okay I get your point. Could you please provide some kind of workaround?
Thank you
Michael
Am Freitag, 3. Oktober 2014 18:26:18 UTC+2 schrieb Thomas Broyer:
On Friday, October 3, 2014 5:15:51 PM UTC+2, confile wrote:
Well if you do not use Places for example when you use GWTP you need the
On Friday, October 3, 2014 4:06:01 PM UTC+2, Manuel Carrasco Moñino wrote:
There is no plans to upgrade Jetty. It implies some changes in
JettyLauncher and WebServer, I have already a patch for that but not
committed yet because I have not tested enough. If someone else demands it
we
Ok the Historian interface looks like it will solve our issues. I'll
rewrite GWTP's PlaceManagerImpl to use it and update my pushstate
implementation.
On Fri, Oct 3, 2014 at 6:34 PM, Thomas Broyer t.bro...@gmail.com wrote:
On Friday, October 3, 2014 4:06:01 PM UTC+2, Manuel Carrasco Moñino
Thanks for the info Thomas, I din't realise that patch.
On Fri, Oct 3, 2014 at 6:34 PM, Thomas Broyer t.bro...@gmail.com wrote:
On Friday, October 3, 2014 4:06:01 PM UTC+2, Manuel Carrasco Moñino wrote:
There is no plans to upgrade Jetty. It implies some changes in
JettyLauncher and
@Richard Wallis Could you please publish your updated pushstate
implementation?
Thank you
Michael
Am Freitag, 3. Oktober 2014 18:51:51 UTC+2 schrieb Richard Wallis:
Ok the Historian interface looks like it will solve our issues. I'll
rewrite GWTP's PlaceManagerImpl to use it and update my
Ok, I'll be publishing it here: https://github.com/rdwallis/gwt-pushstate
probably early next week.
On Fri, Oct 3, 2014 at 6:53 PM, confile michael.gorsk...@googlemail.com
wrote:
@Richard Wallis Could you please publish your updated pushstate
implementation?
Thank you
Michael
Am Freitag,
Hi,
There are a bunch of Elemental patches which fix some issues, some of them
manifested when running its test suite which was not enabled, and the
others to use elemental json as a replacement of the controversial
org.json. I know elemental 2.0 would be redesigned or rewritten for 3.0,
but I
On Thu, Oct 2, 2014 at 12:41 AM, Manuel Carrasco Moñino man...@apache.org
wrote:
Hi,
There are a bunch of Elemental patches which fix some issues, some of them
manifested when running its test suite which was not enabled, and the
others to use elemental json as a replacement of the
How can JsInterop be activated in GWT 2.7? What flag does it?
Am Donnerstag, 2. Oktober 2014 03:22:56 UTC+2 schrieb Brian Slesinsky:
It's experimental and hidden behind a flag, but it's there.
On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csri...@gmail.com
javascript: wrote:
-
-XjsInteropMode JS
On Thu, Oct 2, 2014 at 2:46 PM, confile michael.gorsk...@googlemail.com
wrote:
How can JsInterop be activated in GWT 2.7? What flag does it?
Am Donnerstag, 2. Oktober 2014 03:22:56 UTC+2 schrieb Brian Slesinsky:
It's experimental and hidden behind a flag, but it's
I miss the following sources in the current GWT 2.7 SnapShot:
com.google.gwt.user.client.impl.HistoryImpl
Why is this missing?
Am Mittwoch, 1. Oktober 2014 21:15:26 UTC+2 schrieb Daniel Kurka:
Hi all,
we just settled on a GWT 2.7 release plan:
- We *code freeze* on *October 7th* and
What is the difference between -XjsInteropMode JS and -XjsInteropMode
CLOSURE?
Am Donnerstag, 2. Oktober 2014 23:49:17 UTC+2 schrieb John Stalcup:
-XjsInteropMode JS
On Thu, Oct 2, 2014 at 2:46 PM, confile michael@googlemail.com
javascript: wrote:
How can JsInterop be activated in
Code size explodes when using GWT 2.7 with -XjsInteropMode JS
I compiled the same code with GWT 2.6.1 and GWT 2.7 with argument strict
code size GWT 2.6.1 1.351 MB
code size GWT 2.7 1.361 MB
Then I compiled the same code with -XjsInteropMode JS flag on GWT 2.7
code size 1.601 MB
Why does
- JsInterop Preview is part of the release?
El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió:
Hi all,
we just settled on a GWT 2.7 release plan:
- We *code freeze* on *October 7th* and branch for GWT 2.7.
- As soon as we have the *remaining patches submitted*, we
It's experimental and hidden behind a flag, but it's there.
On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csrina...@gmail.com
wrote:
- JsInterop Preview is part of the release?
El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió:
Hi all,
we just settled on a GWT
No problem, we are on Java 7 for quite some time. I would not even object
to Java 8 for the client side only, but I guess that can wait for 3.0.
GWT/GUI development is really screaming for lambda's with all the event
handling and async callbacks.
On Fri, Sep 12, 2014 at 6:23 AM, Mohammed
Hi,
Even though most people have moved to Java 7 already there is still some
interest in using Java 6. As this closure compiler version would be the
sole reason for requiring Java 7, I would be interested in putting in some
effort to see if we can get the lastest closure compiler backported
Ok so I'm the only one how thinks this might be a problem for us.
We're using GWT in a real large company environment (core banking system)
and to create a baseline we have to use our companies build server. These
are currently running on Java6. I've already reached out to get an
information
On Thursday, September 11, 2014 8:26:37 PM UTC+2, Christian Kütbach wrote:
Java 6 is out of public support since Feb 2013:
https://blogs.oracle.com/henrik/entry/java_6_eol_h_h
There are other JDKs than the one from Oracle.
OpenJDK 6 is still supported for instance (under the leadership of
Java7 is just fine for me...
On Thursday, September 11, 2014 7:50:53 PM UTC+2, Daniel Kurka wrote:
Hi all,
while bringing GSS support into GWT, I discovered that the closure
styleheets compiler actually requires Java7.
This means that we either have to do a back port of the compiler (I
Java7 is fine for development
On 11 September 2014 15:13, Koen Maes k...@koma.be wrote:
Java7 is just fine for me...
On Thursday, September 11, 2014 7:50:53 PM UTC+2, Daniel Kurka wrote:
Hi all,
while bringing GSS support into GWT, I discovered that the closure
styleheets compiler
I think Jave 7 and JRE7 is fine.
Java 6 is out of public support since Feb 2013:
https://blogs.oracle.com/henrik/entry/java_6_eol_h_h
Christian
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop
GWT must go forward. 2.7 Java 7, 3.0 Java 8. Specially when it only effect
development environment.
Regards,
Matic
On Thursday, September 11, 2014 7:50:53 PM UTC+2, Daniel Kurka wrote:
Hi all,
while bringing GSS support into GWT, I discovered that the closure
styleheets compiler actually
I think its fine we require Java 7 for GWT 2.7
On Thursday, September 11, 2014 11:20:53 PM UTC+5:30, Daniel Kurka wrote:
Hi all,
while bringing GSS support into GWT, I discovered that the closure
styleheets compiler actually requires Java7.
This means that we either have to do a back port
I suspect the sdk isn't what you think it is if its not working. Can you
check the classpath and see if it was updated?
On Monday, September 1, 2014 6:09:18 AM UTC-7, Matic Petek wrote:
Hi,
I would like to test new compile per file option, but we run our project
from Eclipse and we don't
For now, I can run my app in Eclipse hosted mode with GWT 2.6.1 and run SDM
server with GWT 2.7 snaphost. It look nothing has change in GWT-RPC
protocol so it is working.
Regards,
Matic
On Monday, September 1, 2014 3:09:18 PM UTC+2, Matic Petek wrote:
Hi,
I would like to test new compile
87 matches
Mail list logo
