When I use GWT 2.7RC1 with GTW-PhoneGap and run the codeserver I get the
following output from the code server:
Turning off precompile in incremental mode.
Super Dev Mode starting up
workDir:
/var/folders/xh/1xkfq26532j97q23qw5pdhs4gn/T/gwt-codeserver-7573159147938212004.tmp
Does this
Hi,
I have just update to RC1 and now if I click refresh button (Chrome),
code change on disk is not detected and recompile (increment compile) is
not performed. We also have compile link on our start page to perform SDM
recompile (base on Brien suggestion from GWT.create) and it still works
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
Turning off precompile in incremental mode.
Super Dev Mode starting up
workDir:
/var/folders/xh/1xkfq26532j97q23qw5pdhs4gn/T/gwt-codeserver-7573159147938212004.tmp
Does this mean anything? Is it a problem if precompile is turned off or
does it mean that incremental compile is
I assume you have deployed an old module.nocache.js file. Try a clean
start by deleting your /war/modulename folder and restart DevMode. A new
module.nocache.js file should be generated (could take a bit as the
CodeServer needs to start before this file gets generated) which
automatically
It is also possible that there is a stale copy of .java resources on your
classpath, such as in target/classes/ for a maven project - we've seen that
get in the way as well. Make sure that either target/classes/ isn't on your
classpath, or that it doesn't have another (stale) copy of whatever you
On Wednesday, October 29, 2014 8:58:07 PM UTC+1, Daniel Kurka wrote:
Jens and I talked offline.
Since gwttars are only relevant for the prod compile and do not impact SDM
compile times, we don't really need them anymore. They are not used within
Google and we do not want to maintain them
I think we should not provide these files as of yet. If someone wants to
make the transition right now they can easily use the converter with these
files and convert them to gss themselves.
I think we want to make that transition once GSS is default (or about to be
default) inside of Google as a
I think I already proposed it some time ago (after someone told me that
Google doesn't actually use them) and got some feedback that they make
their build faster.
A quick search in the groups gave me
https://groups.google.com/d/msg/google-web-toolkit/O8HaPzExxhc/X16AnKZI2JAJ,
but
ok. I will do that in an external third party library
On Thu Oct 30 2014 at 6:19:58 PM 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
I think we should not provide these files as of yet. If someone wants to
make the transition right now they can
On Thu, Oct 30, 2014 at 7:51 AM, Julien Dramaix julien.dram...@gmail.com
wrote:
If GSS was the default, we would have shipped only .gss files.
That's not true. We will still have a release where GSS is default and css
is supported but deprecated that requires css files to be there.
What I
There seems that some assertions in UnifyAST are not being satisfied in
incremental SDM but it runs fine (and correctly) if you turn off assertions.
On Wed, Oct 29, 2014 at 10:53 PM, jay j...@thegindins.com wrote:
I grabbed the RC and switched to use it from my IntelliJ project.
When starting
Jens Colin
Thank you for your help. The problem is really module.nocache.js file (or
batter - generated js files), the behaviour is for my a litter strange :
1) my Ant file looks like this :
target name=superdevmode_main depends=javac description=Run Super Dev
Mode
java failonerror=true
Jens Colin
Thank you for your help. The problem is really module.nocache.js file (or
batter - generated js files), the behaviour is for my a litter strange :
1) my Ant file looks like this :
target name=superdevmode_main depends=javac description=Run Super Dev
Mode
java failonerror=true
I'll give that a try...
Will the issue be handled before the final release?
jay
On Thursday, October 30, 2014 11:47:54 AM UTC-7, Roberto Lublinerman wrote:
There seems that some assertions in UnifyAST are not being satisfied in
incremental SDM but it runs fine (and correctly) if you turn
I compared my GWT-PhoneGap written in GWT 2.6.1 which switching to GWT
2.7beta. Here are my experience. I feel that loading of data especially
images are much slower in GWT 2.7 than in GWT 2.6.1. I tested it on an
iPhone 5. Due to the delay in loading the app feels slow and scrolling does
not
@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
Yes. Will be fixed before final release.
On Thu, Oct 30, 2014 at 2:23 PM, jay j...@thegindins.com wrote:
I'll give that a try...
Will the issue be handled before the final release?
jay
On Thursday, October 30, 2014 11:47:54 AM UTC-7, Roberto Lublinerman wrote:
There seems that some
Release notes are here:
http://www.gwtproject.org/release-notes.html#Release_Notes_2_7_0_RC1
--
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
I am not aware of any changes in 2.7 that should effect performance
loading images. Are you running on iOS7 or iOS8? Daniel would probably
be best able to help you. Are you talking about SuperDevMode loading
performance, or fully optimized compile loading performance?
On Thu, Oct 30, 2014 at
20 matches
Mail list logo
