The documentation said that you should not use JSInterop in production.
Could you specify what can be used in production and what part cannot?
Thank you
Michael
Am Mittwoch, 29. Oktober 2014 16:44:42 UTC+1 schrieb Ray Cromwell:
Whether you use $wnd.SomeJsObject or SomeJsObject depends on the
Jens,
Thank you. Now it's working. SDM documentation should really be updated
- http://www.gwtproject.org/articles/superdevmode.html
Regards,
Matic
On Thursday, October 30, 2014 9:38:02 PM UTC+1, Jens wrote:
Instead of -workDir you should use -launcherDir which contains all public
I use iOS7 and Super dev mode as described by Daniel here
http://blog.daniel-kurka.de/2012/07/mgwt-super-dev-mode.html. I
use -strict -XjsInteropMode JS and output style detailed to compile the
code for the PhoneGap container.
Am Freitag, 31. Oktober 2014 01:02:58 UTC+1 schrieb Ray Cromwell:
You are comparing apples and oranges here. SDM compiles are not optimized,
thus much bigger. If you want to compare performance you will need to do an
optimized compile.
The SDM setup in my blog post is now outdated, here is how you use SDM with
Phonegap in 2.7:
Hi Daniel,
this (https://github.com/mgwt/mgwt/wiki/SuperDevMode-with-PhoneGap) is what
I did. Super dev mode is working. I get a recompile after reload that is
working.
In my app I have a long list with images. When I scroll down the app
freezes when the scrolling reaches a point where new
Are you comparing prod compiles or SDM compiles?
On Fri, Oct 31, 2014 at 10:22 AM, confile michael.gorsk...@googlemail.com
wrote:
Hi Daniel,
this (https://github.com/mgwt/mgwt/wiki/SuperDevMode-with-PhoneGap) is
what I did. Super dev mode is working. I get a recompile after reload that
is
SDM 2.6 was not incremental, it actually pruned code. If you want the
same behavior in 2.7, you'll have to disable incremental compilation
in SDM. This will increase compile times, but probably make the JS
smaller.
However, prod compiles in 2.6 vs 2.7 should have no performance
regression, if
@Daniel Sorry for my stupid question but what is the difference? How do I
do prod compiles or SDM compiles?
Am Freitag, 31. Oktober 2014 10:32:39 UTC+1 schrieb Daniel Kurka:
Are you comparing prod compiles or SDM compiles?
On Fri, Oct 31, 2014 at 10:22 AM, confile
prod = production = optimized.
SDM in incremental code does not do any optimizations. Normal GWT compiles
optimize a lot.
On Fri, Oct 31, 2014 at 10:36 AM, confile michael.gorsk...@googlemail.com
wrote:
@Daniel Sorry for my stupid question but what is the difference? How do I
do prod compiles
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 added a tracking item for updating SDM docs before 2.7.0
On Fri, Oct 31, 2014 at 8:00 AM, Matic Petek maticpe...@gmail.com wrote:
Jens,
Thank you. Now it's working. SDM documentation should really be updated
- http://www.gwtproject.org/articles/superdevmode.html
Regards,
Matic
On
Hi
When trying to build my project with GWT 2.7, I run into issues with
Restlet.
I have opened an issue
here https://github.com/restlet/restlet-framework-java/issues/965
This is the stacktrace :
java.lang.NoSuchMethodException:
Ah okay I see what you mean. I used SDM for my test.
Am Freitag, 31. Oktober 2014 11:26:08 UTC+1 schrieb Daniel Kurka:
prod = production = optimized.
SDM in incremental code does not do any optimizations. Normal GWT compiles
optimize a lot.
On Fri, Oct 31, 2014 at 10:36 AM, confile
With SDM, when using the -noserver argument.
Do we have to manually run the SDM code server, and continue to use the
bookmarklets?
This would be helpful information in the docs also.
On Friday, 31 October 2014 11:25:31 UTC, Daniel Kurka wrote:
I added a tracking item for updating SDM docs
With SDM, when using the -noserver argument.
Do we have to manually run the SDM code server, and continue to use the
bookmarklets?
DevMode -noserver means that no embedded Jetty server will be started to
serve your war directory. It will still start the SDM CodeServer and put a
special
On Friday, October 31, 2014 3:05:29 PM UTC+1, Jens wrote:
With SDM, when using the -noserver argument.
Do we have to manually run the SDM code server, and continue to use the
bookmarklets?
DevMode -noserver means that no embedded Jetty server will be started to
serve your war
On Friday, October 31, 2014 10:22:41 AM UTC+1, confile wrote:
Hi Daniel,
this (https://github.com/mgwt/mgwt/wiki/SuperDevMode-with-PhoneGap) is
what I did. Super dev mode is working. I get a recompile after reload that
is working.
In my app I have a long list with images. When I
Which kind of memory do you mean? Compile works fine it has -Xmx1024m.
Am Freitag, 31. Oktober 2014 15:49:16 UTC+1 schrieb Thomas Broyer:
On Friday, October 31, 2014 10:22:41 AM UTC+1, confile wrote:
Hi Daniel,
this (https://github.com/mgwt/mgwt/wiki/SuperDevMode-with-PhoneGap) is
Hi Daniel,
while working with GWT 2.7RC1, GWTP and GWT-PhoneGap I found the following
problem. In my application I use the REST module from GWTP. SDM works, but
when I change one line to trigger a recompile I get the following error. I
can be sure that there is no error in my code because
Thomas is talking about memory on the mobile device. Safari on iOS
only has about 512mb of heap to work with IIRC. You could be loading
in 50-100Mb of generated JS, slowing down the mobile browser a lot.
I would develop using SDM and Chrome emulation in the desktop browser,
or use XCode's iOS
I finally had some time to think about JsInterop and how to abstract
browser APIs.
I will try to summarize my thought process and different options that I
have played with so that you could get a better understanding where I'm
coming from and I hope it will provide good documentation for future.
21 matches
Mail list logo