[gwt-contrib] GWT & Closure library

[Mihai Stanciu]

Hi

We are looking at using OpenLayers3 js library that is now build using 
Closure framework.
We will use this in a GWT app using the new JsInterop to map the 
OpenLayers3 api.

   1. Is it possible to compile the OpenLayers(or any closure library) 
   based on GWT output, or compile the Java and JS together? 
   2. I see there is a closureFormattedOutput what would be the diference 
   between this and enableClosureCompiler?
   

Thanks 
Mihai

-- 
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/cf95aa6f-1d2f-41e3-9675-604ebb3496e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Officially deprecating Opera permutation

[Mihai Stanciu]

"Google uses a server-side selection script based on the User-Agent request 
header, rather than the *.nocache.js using navigator.userAgent on the 
client-side)"

This sounds like a very nice optimisation. Do you know if there is any 
plugin for doing this in a servlet container /jsp?
How could find/generate  the mapping for "user.agent" -> permutation

Sorry for being offtopic.


On Sunday, May 11, 2014 1:27:37 AM UTC+3, Thomas Broyer wrote:
>
> Opera on Linux is basically dead.
> There's not been a non-security-only or non-crash-fix-only release for 18 
> months (http://www.opera.com/docs/changelogs/unified/1210/)
> Opera has moved to Chromium for more than a year and still not released 
> anything on Linux. Either they waited for the Aura port (first appearance 
> in the latest Opera release, so maybe there'll be a Linux release soon, at 
> last) or they just don't care.
>
> That said, Google Groups and Google Flight Search fallback to the gecko1_8 
> permutation in Opera 12 (with a warning message that it might break), so we 
> should probably make it possible at least (Google uses a server-side 
> selection script based on the User-Agent request header, rather than the 
> *.nocache.js using navigator.userAgent on the client-side)
> Would you mind opening an issue about it?
> Maybe there's a workaround though: it might be as easy as defining a 
> "unknown" (the value returned by the property generator) value for the 
> "user.agent" property that falls back to gecko1_8 (just like ie9 falls back 
> to ie8): i.e.  fallback-value="gecko1_8" />; and then you could use deferred-binding 
> specifically for that "unknown" value to display a warning message, and you 
> could collapse "unknown" and "gecko1_8" values into the same permutation.
> Worth a try IMO if you care about it.
>
> On Friday, May 9, 2014 8:14:55 PM UTC+2, Robert J. Carr wrote:
>>
>> This just burned me.  Just curious why you couldn't have it load the file 
>> from firefox or webkit instead of just doing nothing?  Better to deal with 
>> potential errors than to be a total non-starter.
>>>
>>>

-- 
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/ec6b6be5-2c0e-4524-8f40-da6c557db576%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Last call for GWT 2.6.1

[Mihai Stanciu]

Hi Daniel,

We cannot update to 2.6 due to 
Issue 8585
:
and in a smaller degree byRegression in 2.6 re. webapp class loading in 
DevMode

Issue 8526
: GWT 2.6.0 prevents configuring Jetty via jetty-web.xml

Both of them depends on 
 https://gwt-review.googlesource.com/#/c/6651/ 

Hope this will make the release.

Thank you
Mihai


On Monday, April 7, 2014 12:28:19 PM UTC+3, Daniel Kurka wrote:
>
> As a reminder, we are going to start building GWT 2.6.1 from the GWT 2.6 
> release branch (
> https://gwt-review.googlesource.com/#/q/status:open+project:gwt+branch:release/2.6)
>  
> this Friday (11th April).
> If you want to get your changes into GWT 2.6.1, they need to get in before 
> Friday.
> There's still some time to propose and submit patches, but it's down to 
> days remaining now. Don't fret if you miss the deadline: there will be more 
> releases in the future!
>

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Next Contributor Hangout

[Mihai Stanciu]

Hi

Any news about 2.6.1 plans?

Thanks.

On Monday, March 24, 2014 6:18:57 PM UTC+2, Bhaskar Janakiraman wrote:
>
> Hi Folks,
> The next contributor hangout will be on Wednesday, March 26, from 10.45am 
> to 11.30am PST. As before, please send me email (bjanakiraman at google) if 
> you have something to discuss and want to participate in person, and I'll 
> send you an invite. 
>
> Agenda:
> GWT 2.6.1: Status and Plans (Thomas, Daniel)
> On-going patches & discussion
>
> The session will be recorded and made available via the GWT G+ 
> page
> . 
>
> Thanks,
> Bhaskar
>

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/d/optout.