Google Web Toolkit: 2014

Wednesday, December 31, 2014

@RyanSeacrest tweeted: in bed already??? #rockineve #uk

Ryan Seacrest

@RyanSeacrest

in bed already??? #rockineve #uk pic.twitter.com/ID6Vb5AmJD

Followed by Emily Stoll, Nick Cannon and AshleyTisdaleFrench .

Britney Spears

@britneyspears

To show my appreciation, this exclusive t-shirt is available unsigned for any $50+ donation! britney.lk/nccf pic.twitter.com/6c5lhcYZam

Followed by Nick Cannon, AshleyTisdaleFrench and Demi Lovato.

Just Jared

@JaredEng

Slide down the new year with new beginnings! 🎢🎢🎢 #HappyNewYear @Jaime_King @kyle_newman pic.twitter.com/vqmOkFcp61

Followed by AshleyTisdaleFrench .

What The F*** Facts

@WhatTheFFacts

These 15 insults are the best insults in the history of the internet! bit.ly/1wGZU0W pic.twitter.com/SYh9h3ZBza

View on Twitter

Followed by Emily Stoll.

IGGY AZALEA

@IGGYAZALEA

Also I have the most sparkled tasseled metallic outfit ever for NYE!!! Hahahaha.

View on Twitter

Followed by Demi Lovato.

Harry Styles.

@Harry_Styles

Be nice to everyone and do it five minutes early. Hope everyone has a lovely new year. Thank you for an amazing 2014. All the love .x

View on Twitter

Followed by Demi Lovato.

Not what you're looking for?

Well there's more to see on Twitter! Click here to discover more interesting Tweets.

Explore

Re: how not to cache background image?

Magnus,

Since you want the image cached, but not cached, and to always have the same URL, you're got very contradictory requirements.

Have you considered passing state to your app at startup with information like the proper image URL to use and then dynamically setting it that way? Then you can just use a DB column, quartz job, JMX bean, etc to update this image property as needed and all users will get the proper image on next page load. Personally, I use a root index.jsp page that's cached with a TTL that inlines these parameters into the page and then the GWT entrypoint fetches then when initializing on startup, thus skipping that extra XHR since it's essentially constant information until it changes.

-Joe

--
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+unsubscribe@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 - Get dom element's value from another page

RequestBuilder will return you the text of the response body. If, as you say, A.jsp generates it's content via GWT, then you'll not find the elements of interest. GWT is a client side JS technology. The content for A.jsp will not be rendered, you'll only be getting the raw HTML created by A.jsp.

Why don't you use an XHR request to fetch the needed data from an endpoint instead? Further, it's best to no depend on fetching elements from a different page as this goes against most browser security policies.

-Joe

Re: GWT for Web Development (again)

Can you cite an example metric of the "SEO penalty" you're experiencing? For more than a 18mo now, if you use Google Webmaster Tools and Fetch as Google, you'll see your fully rendered GWT page with the async content loaded and displayed. Given this is the Google spider, it follows that this is what's being used to index your site and that GoogleBot understands your GWT app just fine. Note: this is for sites I manage that don't even implement escape fragment.

-Joe

Re: What's the future of GWT

On Wednesday, December 31, 2014 5:08:59 AM UTC+1, DevMode wrote:

Hi everyone,

I'm evaluating GWT for a project. I using a MAC and noticed that developer plugin doesn't work for the current versions of Chrome (39.0.2171.95), Firefox (34.0), Safari (8.0.2).

This is a bit concerning and raises a few questions:
1. How soon are plugins updated to keep up with the browser updates for Macs?

Never. DevMode has been superseded by SuperDevMode: http://www.gwtproject.org/articles/superdevmode.html

2. What's the reason for the dev plugin not working w/ any of my Mac browsers? Is it because dev plugins are being replaced with Super Dev Mode?

Browser makers have made changes that make the plugin impossible to update.

3. Is the support good for Windows browsers?

AFAICT, Microsoft hasn't broken the plugins yet, so IE still works with "classic dev mode".

4. I have heard that GWT is going to be phased out soon in favor of JS frameworks like Angular (and not developed anymore)? Is there any truth to that?

No: http://gmailblog.blogspot.com.es/2014/11/going-under-hood-of-inbox.html

The biggest problem is that Google uses GWT more and more, and can't keep up with the external users' needs; this is why the Steering Committee was created a few years back, and I don't think things have changed on Google's side since then.

GWT - Get dom element's value from another page

Suppose I have two pages A.jsp and B.jsp. I have few elements on both the pages which has been generated through GWT code. Now I want to get the value of a element which is there on A.jsp while I'm sending a request through B.jsp and I want to pass that value into the request header. I'm generating a request with:

RequestBuilder rb = new RequestBuilder(RequestBuilder.GET, queryUrl);

I have tried using getElement() getElement however it is giving the elements which are there on that.

I want to access elements from other pages. Is it possible?

Tuesday, December 30, 2014

Re: .nocache.js generated with same timestamp as .gwt.xml

Thanks Thomas.

On Wednesday, December 31, 2014 2:33:59 AM UTC+8, Thomas Broyer wrote:

This is actually a known issue with a proposed patch: https://gwt-review.googlesource.com/10520

On Tuesday, December 30, 2014 5:04:05 PM UTC+1, Dop Sun wrote:
Hi,

In previous versions, e.g. 2.6.1, <module>.nocache.js file generated with timestamp when the files generated. But in version 2.7.0, the <module>.nocache.js file generated with the same timestamp of <module>.gwt.xml.

Is this by design?

I'm raising this question because it causes Safari ignores latest compiled <module>.nocache.js (which is same timestamp as <module>.gwt.xml), and using previously cached file, which is compiled by 2.6.1, and causing application not working in Safari.

And yes, suggestions of this page, section [Perfect Cache] can help. Change .htaccess file with suggested expiry settings.

I'm using Mac OS X Yosemite.

Thanks,
Regards,
Dop

What's the future of GWT

Hi everyone,

I'm evaluating GWT for a project. I using a MAC and noticed that developer plugin doesn't work for the current versions of Chrome (39.0.2171.95), Firefox (34.0), Safari (8.0.2).

This is a bit concerning and raises a few questions:

1. How soon are plugins updated to keep up with the browser updates for Macs?

2. What's the reason for the dev plugin not working w/ any of my Mac browsers? Is it because dev plugins are being replaced with Super Dev Mode?

3. Is the support good for Windows browsers?

4. I have heard that GWT is going to be phased out soon in favor of JS frameworks like Angular (and not developed anymore)? Is there any truth to that?

Thanks in advance for any info.

Re: Calling getVersion() to get the GWT version from a Linker

Checkout com.google.gwt.dev.About and About.properties in the same package. That is what Eclipse GPE uses to figure out the GWT version of the GWT SDK.

-- J.

Calling getVersion() to get the GWT version from a Linker

I'd like to get the GWT version from inside a linker (say the link() method) which in client code can be done via GWT.getVersionI(), however, nothing I've tried appears to work. You can't use the client version of GWT as that leads to a runtime Java exception since the method getVersion() cannot be found:

java.lang.UnsatisfiedLinkError: com.google.gwt.core.client.GWT.getVersion0()Ljava/lang/String;
     [java]     at com.google.gwt.core.client.GWT.getVersion0(Native Method)
     [java]     at com.google.gwt.core.client.GWT.getVersion(GWT.java:191)
               :

which is understandable since we're not in client code, but I also can't use the ServerGwtBridge via something like: ServerGwtBridge.getInstance().getVersion(), as that just returns the string "unknown". Indeed it's hardcoded as "unknown" in the source so I'm not sure what good it is - unless something else is supposed to inject a valid version string. Finally, if I import the class com.google.gwt.core.shared.GWT and call GWt.getVersion() on that, then it will run (unlike when you try to refer to the "client" package), but the result is null. Nice, right?

All I can think of at this point is using something like System.getenv() to try to read GWT_HOME, but that seems wrong. Is there no working getVersion() I can call?

Re: GWT for Web Development (again)

I am working on a site that will result in the same hurdle. Take a look at Google's solution to this problem:

https://developers.google.com/webmasters/ajax-crawling/docs/getting-started

On Wednesday, December 24, 2014 11:12:43 PM UTC-8, Adolfo Rodriguez wrote:

Hi, I suppose the question has been discussed many times but I will like to reopen the issue.

Since I discovered GWT, aprox. 5 years ago, I do not want any other framework. It gives me the right tool to get a good productivity, forget about passing HTTP params back and forward, enjoy lots of libraries, and last times, with bootstrap I have added the best of design to my GWT projects. So, I feel having collected a great toolkit for development.

There is only a problem: search engines. Search engines, in my experience do not like GWT. Even when you have the _escaped_fragment_ thing, I guess google does not treat you the same that with pure HTML code. I know that GWT is not intended for web but is really a shame not enjoying the full potential of the framework on web environments. I have noticed that most of companies that start in GWT migrates to common Java/HTML frameworks as soon as they are successful or they get funding, just because the SEO penalty.

So, is there anything, at all, that could be done, in future releases, to claim GWT being also a framework for Web environments? I mean, not allowing google even know that your webapp was created with GWT. I know about the dynamic content generation but I guess something could be done about it. I think adoption would multiply by thousands.

Thanks

Re: .nocache.js generated with same timestamp as .gwt.xml

This is actually a known issue with a proposed patch: https://gwt-review.googlesource.com/10520

On Tuesday, December 30, 2014 5:04:05 PM UTC+1, Dop Sun wrote:

Hi,

In previous versions, e.g. 2.6.1, <module>.nocache.js file generated with timestamp when the files generated. But in version 2.7.0, the <module>.nocache.js file generated with the same timestamp of <module>.gwt.xml.

Is this by design?

I'm raising this question because it causes Safari ignores latest compiled <module>.nocache.js (which is same timestamp as <module>.gwt.xml), and using previously cached file, which is compiled by 2.6.1, and causing application not working in Safari.

And yes, suggestions of this page, section [Perfect Cache] can help. Change .htaccess file with suggested expiry settings.

I'm using Mac OS X Yosemite.

Thanks,
Regards,
Dop

Re: Strange Behavior from scheduleIncremental

Scheduler.scheduleIncremental() should be independent of any user input actions. Put some logging statements into your command and watch your console. I am pretty sure you will see log output even if the user will not perform any input actions.

-- J.