Re: DataGrid header style has problem in IE8
Please apply column width of datagrid.setColumnWidth method it will set header fix and white space will not display. Example datagrid.setColumnWidth(projectCode, columWidth + px); On Tuesday, 4 December 2012 13:48:17 UTC+5:30, tong123123 wrote: as shown in the attachment, in IE8, in datagrid header, even I set the thead element background color to #bcee68, the result is just separate th in the thead is change background color, not the whole thead I found this problem only occur in IE8, but not in firefox. also, this problem will not occur when first load the page or the datagrid's row has contents, the problem only shown when the search button is pressed and no result return. How to solve it? I try to set the background color of table element inside datagrid, but this will cause the background color of the label record not found changed also. -- 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: WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
Thanks Honza, works for me. On Friday, June 13, 2014 11:54:14 AM UTC+5:30, Honza Rames wrote: One more thing to note. On 64-bit systems you need to create a key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft\Prefs. I didn't even have to change any permissions to make the message go away, just create the key. Honza On Sunday, June 8, 2014 11:30:33 PM UTC+2, Mark Vlcek wrote: Thanks everyone, just encountered this same problem and this solved my issue as well! On Saturday, June 15, 2013 1:01:22 PM UTC-7, John V Denley wrote: Just had the same problem myself, and found that to fix it I had to do what you suggested, but I also had to manually create a Prefs key under JavaSoft too, as mentioned here: http://www-01.ibm.com/support/docview.wss?uid=swg21496098 On Friday, 14 June 2013 02:02:26 UTC+1, QingFeng Du wrote: well well, 4 years later, I came across the same problem. here's my solution: open regedit.exe ( really hate Microsoft and their regedit.reg). change the permission of key: HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft.Right click the icon, then change the permission to full operation. On Saturday, June 27, 2009 3:03:20 PM UTC-4, Farinha wrote: The subject has it all. Eclipse 3.4.2 GWT Eclipse Plugin Windows 7 Thanks in advance for the help. -- 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: GWT distributed builds
Well, we fully rebuild our application because it's quite big, and is developed more or less actively. So if we have enough resources (and we do have them), we can build it in parallel and the question is, does anybody has success story? воскресенье, 6 июля 2014 г., 21:28:50 UTC+4 пользователь Paul Robinson написал: Do you really need all 23 permissions several times per hour? Building in parallel is a good idea, but avoiding unnecessary permissions is easy and makes a big difference while developing. Paul -- 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: GWT distributed builds
Well, we fully rebuild our application because it's quite big, and is developed more or less actively. So if we have enough resources (and we do have them), we can build it in parallel and the question is, does anybody has success story? Not sure what kind of a story you want to hear? If you have 23 permutations and 23 hosts available then its like just compiling one permutation + some overhead because of data distribution and fetching. But during development nearly everybody works with a single permutation only. Full builds are most likely done on a CI server as a nightly job or when you do a release. The wiki page gives you all the information you need to distribute the GWT compilation. How you design your distributed build environment is up to you. Could be as easy as a set of shell scripts + scp + ssh remote script execution. There are some projects building on top of what GWT provides but I don't know how well they work. You will easily find them using google search. -- J. -- 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: Making browser save userneme password
After a great deal of work, I finally have the whole browser-save-password
code working on all browsers I can find (Chrome, IE, Firefox, Safari). The
code graciously provided by Saumar Hajjar in this thread does work. You
do, however, have to understand it in order to use it in your application.
Given the state of HTML and browser technology, as well as the various
specific browsers, this code is incredibly fragile and sequence dependent.
It took me many days of debugging and trial-and-error coding to get it all
working. Now that it does work and I have some degree of understanding, I
thought I would share some of the important points I discovered. I hope
this can be helpful to others. I apologize in advance to those of you who
find my observations obvious.
Notice the line that has Window.Location.reload(). That critical line
makes the whole thing work differently than anything you would have
expected. That line causes the whole page to reload from scratch losing
all state information (including JavaScript variables, GWT instance and
static variables, etc.) _except_ session data. You will notice that his
backend code utilizes session data in order to keep track of the fact that
he'd been there before (the user logged in). This is the reason the first
thing he has to do is call a backend service - to find out which state he
is in (user logged in or not). The system must re-load like this
(according to him) in order for all browsers to execute their save-password
operation. Password saving happens at that reload point.
Interestingly, his note states that the reload call is only necessary for
Chrome. Unfortunately, that one line dictates most of the architecture.
In other words, if that line wasn't required, a far simpler approach could
be used.
As has been stated all over the place, the browser will only save the
password if the password stuff is in the original HTML file - not GWT added
controls. This means that you will likely want to make the login HTML
disappear after they log-in, and re-appear when they log out. I did that
by wrapping the whole HTML body in a div like this:
div class=login-page id=login-page style=display: none; /div
I could then control its visibility with:
private void hideLoginPage() {
RootPanel.get(login-page).setVisible(false);
}
private void showLoginPage() {
RootPanel.get(login-page).setVisible(true);
}
private void reloadLoginPage() {
Window.Location.reload();
}
In my case, I set style=display: none; on the div to prevent it from
showing at first. Something I needed. If you want to show it right away,
just remove that. Importantly, I discovered that showLoginPage() can only
be called _after_ all of the calls to the various wrap() methods have been
called.
Another thing I noticed, my call to reloadLoginPage() (in order to get the
browser to save the password) only worked in response to a backend call -
as part of the response handler as he does below. During testing, if I
eliminated the backend call, the reloadLoginPage() would not cause the
browser to save the password.
This is all I can think of. I hope it is helpful.
Blake McBride
On Mon, Jun 9, 2014 at 12:39 AM, Saumar Hajjar sau...@gmail.com wrote:
Working example
*PleaseSaveMyPassword.html:*
!doctype html
html
head
meta http-equiv=content-type content=text/html; charset=UTF-8
titlePlease Save My Password/title
script type=text/javascript language=javascript
src=pleasesavemypassword/pleasesavemypassword.nocache.js/script
style
h1 {font-size: 2em; font-weight: bold; color: #77; margin: 40px 0px
70px; text-align: center;}
#gwt, table {width: 100%;}
.loginPanel {width: 300px; margin: 0 auto; border: 1px solid #ccc;
border-radius: 5px;}
input {width: 200px; float: right;}
button {width: 80px; float: right;}
.loggedInPanel {width: 300px; margin: 0 auto; font-size: 1.5em;}
.gwt-HTML {float: left;}
a {float: right;}
/style
/head
body
h1Please Save My Password/h1
div id=gwt/div
div id=login style=display: none;
form id=login_form action=javascript:;
input type=text name=username id=login_username /
input type=password name=password id=login_password /
button type=submit id=login_submit/button
/form
/div
/body
/html
*PleaseSaveMyPassword.java:*
package com.sh.pleasesavemypassword.client;
import com.google.gwt.core.client.EntryPoint;
import com.google.gwt.core.client.GWT;
import com.google.gwt.event.dom.client.ClickEvent;
import com.google.gwt.event.dom.client.ClickHandler;
import com.google.gwt.user.client.DOM;
import com.google.gwt.user.client.Window;
import com.google.gwt.user.client.rpc.AsyncCallback;
import com.google.gwt.user.client.ui.Anchor;
import com.google.gwt.user.client.ui.Button;
import com.google.gwt.user.client.ui.FlexTable;
import com.google.gwt.user.client.ui.FlowPanel;
import com.google.gwt.user.client.ui.FormPanel;
import
Re: GWT distributed builds
Use collapse-all-properties / in your gwt.xml when making development builds. Or use superdev mode. On Wednesday, July 9, 2014 1:56:54 PM UTC-7, Jens wrote: Well, we fully rebuild our application because it's quite big, and is developed more or less actively. So if we have enough resources (and we do have them), we can build it in parallel and the question is, does anybody has success story? Not sure what kind of a story you want to hear? If you have 23 permutations and 23 hosts available then its like just compiling one permutation + some overhead because of data distribution and fetching. But during development nearly everybody works with a single permutation only. Full builds are most likely done on a CI server as a nightly job or when you do a release. The wiki page gives you all the information you need to distribute the GWT compilation. How you design your distributed build environment is up to you. Could be as easy as a set of shell scripts + scp + ssh remote script execution. There are some projects building on top of what GWT provides but I don't know how well they work. You will easily find them using google search. -- J. -- 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: Best approach from consuming REST(Jetty) webservice
Or use Errai JAX-RS https://docs.jboss.org/author/display/ERRAI/Errai+JAX-RS On Tuesday, July 8, 2014 7:12:06 AM UTC-7, Thomas Broyer wrote: On Tuesday, July 8, 2014 10:11:11 AM UTC+2, Santhosh Thadaka wrote: I have my backend with EJB and REST webservice and I want to consume the REST service with GWT as a front end can any one suggest with which is the best approach RPC RequestFactory RequestBuilder and I am not allowed to use any external api's. Please let me know what all should be taken care. GWT-RPC is an RPC protocol and API, and RequestFactory is a protocol too. If you want to consume REST services, you'll have to use either RequestBuilder or XMLHttpRequest (the former wraps the latter). If the data you exchange is JSON, then you can either use JsonUtils and overlay types (unfortunately only works for parsing for now –stringify is being added as I write–, but you can defer to JSONObject for serialization), JSONParser and friends, or AutoBeans. -- 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: GWT Developer Plugin
Firefox ESR 24.6 has portable version, so you can use it specifically for devmode http://portableapps.com/apps/internet/firefox-portable-esr On Monday, July 7, 2014 9:19:26 AM UTC-7, Rade Martinović wrote: AFAIK is internet slang for As Far As I Know :) -- Rade On Thursday, July 3, 2014 4:15:23 PM UTC+2, Francesco Viscomi wrote: What do you mean, can please be more accurate? SuperDevMode is another plugin with the same functionality? AFAIK what is that and where i can find it? thanks really a lot 2014-07-03 15:18 GMT+02:00 manstis michael...@gmail.com: Or use SuperDevMode Support for DevMode browser plugins is, AFAIK, coming to an end... On Wednesday, 2 July 2014 16:18:37 UTC+1, Francesco Viscomi wrote: Hi all i need to use GWT Developer Plugin and I have windows 8 at 64bit either chrome and firefox i'm not able to use the plugin; when i try to download it i get: (firefox) Sorry, the GWT Developer Plugin only supports Firefox 3.0 - 26.0. Perhaps download Firefox 24 http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/24.3.0esr/? (chrome) start to download but a pop up inform me that the installation has been disabled because it is necessary plugin NPAPI; how i can resolve this issue? thanks a lot Francesco -- You received this message because you are subscribed to a topic in the Google Groups Google Web Toolkit group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/t1N2wpHjD54/unsubscribe . To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-we...@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- Ing. Viscomi Francesco -- 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: Best server communication
Try Errai JAX-RS, it works perfectly for my development. On Saturday, June 21, 2014 10:50:19 AM UTC-7, mamadou lakhassane cisse wrote: Hi people I'm a newbie in GWT. I've made some apps but still using RPC. I was wondering now if there were a better way than that for server communication. Thanks in advance. -- 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.
[gwt-contrib] gwt ant build
Hi folks, I checked out GWT code and followed steps mentioned @ http://www.gwtproject.org/makinggwtbetter.html#checkingout However, ant is giving me following error: pranay@pranay-NewCo:~/Documents/GWT/trunk$ ant Buildfile: /home/pranay/Documents/GWT/trunk/build.xml build: dev: buildtools: build: doctool: compile: BUILD FAILED /home/pranay/Documents/GWT/trunk/build.xml:125: The following error occurred while executing this line: /home/pranay/Documents/GWT/trunk/build.xml:27: The following error occurred while executing this line: /home/pranay/Documents/GWT/trunk/build.xml:58: The following error occurred while executing this line: /home/pranay/Documents/GWT/trunk/build.xml:27: The following error occurred while executing this line: /home/pranay/Documents/GWT/trunk/build.xml:120: The following error occurred while executing this line: /home/pranay/Documents/GWT/trunk/build_tools/build.xml:16: The following error occurred while executing this line: /home/pranay/Documents/GWT/trunk/build_tools/build.xml:10: The following error occurred while executing this line: /home/pranay/Documents/GWT/trunk/build_tools/doctool/build.xml:9: Directory /home/pranay/Documents/GWT/trunk/build/out/build_tools/doctool/bin creation was not successful for an unknown reason Total time: 2 seconds pranay@pranay-NewCo:~/Documents/GWT/trunk$ pranay@pranay-NewCo:~/Documents/GWT/trunk$ ant -version Apache Ant(TM) version 1.9.3 compiled on April 8 2014 I am not sure what went wrong. Any help would be highly appreciated. Cheers, Pranay -- 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 discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/5c43de9a-8efd-4193-93eb-8a26ca3aade3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
