Re: Getting rid of Dev mode for future GWT releases
In the past, I had encountered situations that the code works fine under Dev-Mode, but things went wrong in production mode, or acted differently in production mode. At the beginning I had a hard time to switch from Dev-Mode to SDM. It took me "forever" to trace the bugs in my code. I found that things got a lot easier when I start new project from the very beginning using SDM. More Java code in the Browser-end means more stuff GWT needs to convert into JavaScript. With using SDM, it encourages me to use more HTML / CSS / JavaScript instead of using GWT-Java only. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: How to Remote Logging without using RPC?
Thank you. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
How to Remote Logging without using RPC?
In the GWT application that I am working on, it is setup to remote-logging with any uncaught exceptions via SerializableThrowable RPC StackTraceDeobfuscator ... Is there any documentation on how to do it without using RPC? I have search the Internet but is seems most of the documentation are using RPC. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Development Mode will not be supported in Firefox 27+
The stack-trace in Super Dev Mode is the only major issue that I have. It would be nice if the UncaughtException in SDM can tell me which line in java source is causing the problem, instead of giving me those JavaScript stack-trace messages... So far I like SDM. My current project is running a lot faster in SDM compare to Development Mode plugin. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: JavaFX 2.2 WebView support - possible new User Agent?
Just wondering how would the JavaFX WebView if you change the style from
GWT, instead from CSS file. For instance:
public static void setFxPadding(com.google.gwt.user.client.Element element)
{
element.getStyle().setProperty(FxPadding, 0px 0px 0px 22px);
}
On Wednesday, November 6, 2013 10:33:33 AM UTC-5, Michael Prentice wrote:
I've posted this question to StackOverflow here:
http://stackoverflow.com/questions/19816129/how-do-i-left-pad-a-div-in-a-javafx-webview
On Tuesday, November 5, 2013 6:40:08 PM UTC-5, Michael Prentice wrote:
Thank you for the idea about escaping the first dash. It made the CSS
editor in GWT Designer a bit happier (no longer red). But it didn't end up
fixing the issue. I tried the following without any luck as well (all
worked great in Chrome):
.foo-bar-values {
padding: 0px 0px 0px 22px;
}
.foo-bar-values {
margin: 0px 0px 0px 22px;
}
.foo-bar-values {
margin-left: 22px;
}
.foo-bar-values {
padding-left: 22px;
\-fx-label-padding: 0px 0px 0px 22px;
}
.foo-bar-values {
padding-left: 22px;
\-fx-padding: 0px 0px 0px 22px;
}
As far as migration to JavaFX, we did not see a smooth migration path
there. We can't run our Swing screens in a browser and we can't convert
everything to JavaFX in a single release. We also don't want to have half
of our app run in the browser and half in a Swing application. We don't use
Java WebStart for deployment and we aren't able to change the installation
of our client to require users to browse to a certain site to install the
application. It is pushed out Enterprise wide via Enterprise level
installers.
Using web technologies (GWT) hosted in a JavaFX WebView allows for us to
replace a screen at a time (or more) within our current Swing application
without needing to completely change the deployment/installation strategy.
It also minimizes the end user training with each release. Eventually (2-3
years), we will be in a situation where we can replace the last of the
Swing screens and go to a completely web based solution. We are hoping that
Chromium runtime will be available by then so that we can switch straight
to it (installed as part of our app and not by the user or IT) rather than
having to depend on older versions of IE installed throughout the
Enterprise.
*Some other info about JavaFX WebView:*
- In order to handle Confirmation and Alert dialogs, you must
implement handlers for these in your WebEngine JavaFX code. It isn't hard
and it is quite customizable, but it doesn't come out of the box.
- Deploying and testing within the WebView is quite a pain. FireBug
Lite provides for some limited debugging, but with GWT we don't get
anything useful on the Script tab (Access to restricted URI denied.)
So debugging has to be done in DevMode in Chrome or in the WebView via
alert() dialogs (like debugging with printf's ages ago). This is
minimized
by the fact that so far our only code that would need to be debugged in
the
WebView is the navigation code that talks between GWT and Swing via JSNI
and JavaFX.
Michael Prentice
GDG Space Coast
http://gdgspacecoast.org
On Tuesday, November 5, 2013 6:06:53 PM UTC-5, Oliver Krylow wrote:
If the CSS snippet you have shown happens to reside in a uibinder file,
try escaping prefixed rules with a \ .
\-fx-label-padding ...
The CSS parser of gwt used to have trouble with those .
Thank you for reporting your experience with the javafx webview. It has
been an interesting read.
Could you explain your decision to migrate to web technologies instead
of migrating to javafx and deploying it in the browser
http://docs.oracle.com/javafx/2/deployment/deployment_toolkit.htm ?
On Nov 5, 2013 10:44 PM, Michael Prentice spla...@gmail.com wrote:
I've been working on a project for the last few months which involves
creating new screens for our Swing application. We wanted to start moving
towards a web based interface, but we cannot re-do hundreds of screens in
a
single release/year. So after doing some testing and being satisfied with
the HTML5 / CSS 2.1 support in the JavaFX 2.2 Webview, we decided that
this
was a possible migration path. I am currently working on the first leg of
this path and things have gone quite well so far. I chose GWT to build the
front-end of the app due to our team's experience with WindowBuilder/Swing
and it's focus on Enterprise web applications. Our application is a
complex
Enterprise app that must be maintained over many years by different
people.
*Here are some of the results and issues:*
*Success:*
- General GWT development has been very productive (learning and
architecting the app took considerable time).
- Performance running in the WebView has been acceptable on
machines with decent GPUs which includes all of our client machines (8
MB
video card servers don't do well).
Re: Thoughts on GWT 3.0 re: Java 8 and IE 8/9
If IE7support is removed from GWT, will GWT run correctly on IE in Intranet? (IE will default to IE7 Browser mode for Intranet Website) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Re: Thoughts on GWT 3.0 re: Java 8 and IE 8/9
In Intranet environment, that META tag can only change IE Document Mode (such as how IE layout the web page), but it cannot change IE Browser Mode (such as IE's JavaScript Engine). It is because the Browser Mode is loaded (Intranet is detected) before IE parse the HTML. Even with the meta http-equiv=X-UA-Compatible content=IE=edge,chrome=1 tag, in the Intranet environment IE 9 can display HTML5 sites in appearance only, but using IE 7's JavaScript engine, which does not support HTML5 feature like canvas... etc. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Re: Thoughts on GWT 3.0 re: Java 8 and IE 8/9
On Monday, October 28, 2013 3:49:19 PM UTC-4, Jens wrote: In Intranet environment, that META tag can only change IE Document Mode (such as how IE layout the web page), but it cannot change IE Browser Mode (such as IE's JavaScript Engine). It is because the Browser Mode is loaded (Intranet is detected) before IE parse the HTML. Even with the meta http-equiv=X-UA-Compatible content=IE=edge,chrome=1 tag, in the Intranet environment IE 9 can display HTML5 sites in appearance only, but using IE 7's JavaScript engine, which does not support HTML5 feature like canvas... etc. I guess you have to uncheck the checkbox Display intranet sites in compatibility view in IE's compatibility view settings. -- J. My concern is even if the users are using IE9 or IE10, in Intranet the application can be broken because IE7 Browser Mode is being used, and the users or developers may not aware of what is going on. P.S: In my opinion, it is great for GWT moving forward, and personally I hate dealing with IE. However, just heads-up for those who are stuck with Intranet + IE. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Re: Thoughts on GWT 3.0 re: Java 8 and IE 8/9
I have tried your filter, and the IE Browser Mode has changed, however: For IE8, I got Internet Explorer 8 Compatibility View, and the user agent is: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; .NET CLR 1.1.4322; InfoPath.3) For IE9, I got Internet Explorer 9 Compatibility View, and the user agent is: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; BRI/1) I am not sure if your filter solves the issue; I would expect to see MSIE 8.0 for IE8 in the user agent. On Monday, October 28, 2013 4:11:44 PM UTC-4, Colin Alworth wrote: Chak, take a look again at my post - while the meta tag definitely does not work to tell IE8 to behave when in intranet mode, loading the exact same html content and sending the same ua-compat details over a HTTP header *does* solve this. On Monday, October 28, 2013 3:08:47 PM UTC-5, Chak Lai wrote: On Monday, October 28, 2013 3:49:19 PM UTC-4, Jens wrote: In Intranet environment, that META tag can only change IE Document Mode (such as how IE layout the web page), but it cannot change IE Browser Mode (such as IE's JavaScript Engine). It is because the Browser Mode is loaded (Intranet is detected) before IE parse the HTML. Even with the meta http-equiv=X-UA-Compatible content=IE=edge,chrome=1 tag, in the Intranet environment IE 9 can display HTML5 sites in appearance only, but using IE 7's JavaScript engine, which does not support HTML5 feature like canvas... etc. I guess you have to uncheck the checkbox Display intranet sites in compatibility view in IE's compatibility view settings. -- J. My concern is even if the users are using IE9 or IE10, in Intranet the application can be broken because IE7 Browser Mode is being used, and the users or developers may not aware of what is going on. P.S: In my opinion, it is great for GWT moving forward, and personally I hate dealing with IE. However, just heads-up for those who are stuck with Intranet + IE. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Re: Elegant handling of user experience when new GWT application is deployed.
On Tuesday, January 8, 2013 12:16:54 PM UTC-5, DrG wrote: Is there an elegant solution to handle when a new release is deployed while you are in the GWT app? E.g. we want the application to notice a new version of itself and automatically do a full page refresh? Ideas? In the project I am working on: If new version is detected, store the state of the application locally in browser as cookies before refreshing the page. When the page is refreshed, read the cookies and restore the state of the application, and then delete those cookies. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/1g1bI1BxwUwJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Compilation Time Performance Improvement
Instead of compiling one permutation at a time, there is an option to
compile multiple permutations at the same time by mutli-process.
Here is the parameter I used in the Ant build.xml file (sorry, I don't use
maven), all you needed to add -localWorkers within gwtc target tag:
target name=gwtc depends=javac description=GWT compile to JavaScript
(production mode)
java failonerror=true fork=true
classname=com.google.gwt.dev.Compiler
classpath
pathelement location=src /
path refid=project.class.path /
pathelement location=C:/gwt-2.5.0.rc1/validation-api-1.0.0.GA.jar /
pathelement
location=C:/gwt-2.5.0.rc1/validation-api-1.0.0.GA-sources.jar /
/classpath
!-- add jvmarg -Xss16M or similar if you see a StackOverflowError --
!-- jvmarg value=-Xmx256M/ --
jvmarg value=-Xmx1024M /
arg line=-war /
arg value=war /
!-- Additional arguments like -style PRETTY or -logLevel DEBUG --
arg line=${gwt.args} /
!-- Number of process to compile --
arg value=-localWorkers /
arg value=2 /
arg value=-optimize /
arg value=9 /
arg value=-strict /
!-- arg value=-XenableClosureCompiler / --
arg value=mta.itrac.Itrac /
/java
/target
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/hhytunHdDYsJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT/GXT File-Upload Example
Have you try using FileUpload object from GWT? http://google-web-toolkit.googlecode.com/svn/javadoc/2.4/com/google/gwt/user/client/ui/FileUpload.html On Wednesday, August 15, 2012 5:13:52 AM UTC-4, Sascha Hoffmann wrote: Hi everybody I have only a little question. Is anybody here who knows a good example how to upload a file with gwt oder gxt? I found two in the net but they don't work. I would apreciate it if someone could help me. Sascha -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/PopX3YWRgWUJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.0.0 DevMode: Strange warning when RPC with some object as parameter
I am assuming you are using GWT SDK In the Ant file build.xml, don't forget to update the path of GWT. !-- Configure path to GWT SDK -- property name=gwt.sdk location=C:/gwt-2.4.0 / You may also need to validation-api-1.0.0.GA.jar, validation-api-1.0.0.GA-sources.jar point to the right location. Just create a new project using 2.4.0, and compare the build.xml with the 2.0.0 ones and see what is missing. On Thursday, August 9, 2012 9:19:01 AM UTC-4, Vitaliy K wrote: Hi all, when I updated my project from GWT 2.0.0 to 2.4.0, noticed that in window GWT Development Mode at Jetty tab there is a warning: [WARN] Server class 'junit.framework.AssertionFailedError' could not be found in the web app, but was found on the system classpath [WARN] Adding classpath entry 'file:/C:/eclipse.Indigo/plugins/org.junit_4.8.2.v4_8_2_v20110321-1705/junit.jar' to the web app classpath for this session I found it appears when RPC method that takes an object, such as java.util.Date (not String and not null) or some my class. How to get rid of this warning? I do not think is a good idea to copy junit.jar into the directory war\WEB-INF\lib. (OS: Windows 7; IDE: Eclipse Indigo) Thank you in advance -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/fIEdgQa6XDgJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Regarding GWT with the upcoming Windows 8 and Internet Explorer 10
It has been confirm that the release date for Windows 8 is October 26, 2012. Windows 8 also includes the next version of its browser: Internet Explorer 10. Will GWT 2.5 (final release) support IE10? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/sPWhL2fCRq8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Regarding GWT with the upcoming Windows 8 and Internet Explorer 10
Thank you for the reply. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/EgXriYXO_hsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Firefox 13 DevMode Plugin
Thank you very much. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/gQ16KwAqCLcJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: XSRF Initial Token Generation
You may just set the cookie using the methods in
com.google.gwt.user.client.Cookies
For example:
public void onModuleLoad()
{
Cookies.setCookie(JSESSIONID, Any value you like for the XSRF Token
creation);
}
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/efFlaKFK0XcJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: R: Re: Re: Can't install Google Web Toolkit Developer Plugin under Chrome
You may want to try the offline installation Firefox - https://dl.google.com/dl/gwt/plugins/firefox/gwt-dev-plugin.xpi Chrome - https://dl.google.com/dl/gwt/plugins/chrome/gwt-dev-plugin.crx Safari - https://dl.google.com/dl/gwt/plugins/safari/gwt-dev-plugin.dmg -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/mscUYIFIjwoJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
