I dunno man, this looks a lot like blogspam - lots of posts in a short amount of time, esp since these are all quite outdated or just wrong. GWT 2.4 is just over three years old now, this feature hasn't been new in a long time. Plus, the whole third paragraph is a quote (uncited) from http://www.gwtproject.org/doc/latest/DevGuideUiBinder.html, and doesnt link to it, but instead links to the old (dead) content at developers.google.com/web-toolkit.
(The others have issues too, addHandler+sinkEvents is easier to use as just addDomHandler, and iterating through panels is not too bad since any panel implements Iteratable<Widget>
, you can just do a java for-each.)
Can you at least meter them out a bit, not several in an hour, not always link to your own blog, and make sure to update this stuff a bit more before sending it out?
It seems like you are still confused about GWT client-side vs server-side.
GWT cilent-side is the only place where you are limited in what you can import and use. That is the code that gets converted to JavaScript and is run in the browser.
Your server-side is completely full Java and you can use anything you want. That is where your database work will be. You will use RPC to send messages from the client to the server to perform these transactions. The server-side code will run on the server, not in the browser.
It is really simple. You can find all the documentation here: http://www.gwtproject.org/doc/latest/DevGuideServerCommunication.html#DevGuideHttpRequests
and that's the code you need
import com.google.gwt.http.client.*; ...
String url = "http://www.myserver.com/getData?type=3"; RequestBuilder builder = new RequestBuilder(RequestBuilder.GET, URL.encode(url));
try { Request request = builder.sendRequest(null, new RequestCallback() { public void onError(Request request, Throwable exception) { // Couldn't connect to server (could be timeout, SOP violation, etc.) }
public void onResponseReceived(Request request, Response response) { if (200 == response.getStatusCode()) { // Process the response in response.getText() } else { // Handle the error. Can get the status text from response.getStatusText() } } }); } catch (RequestException e) { // Couldn't connect to server }
Is it to optimize your compiled CSS?
You could take a look at this: http://dev.arcbees.com/gsss/mixins/
Where most used methods are used. If you look at the sources, you may find the answer you seek. AND This piece of documentation will explain how to use conditional logic into GSS files: http://www.gwtproject.org/doc/latest/DevGuideGssVsCss.html
This is just RC1. They typically make an announcement when the 2.6 final is cut.
UPDATE: I stand corrected. I originally just glanced at: http://www.gwtproject.org/release-notes.html but should've checked https://gwt.googlesource.com/gwt/