[gwt-contrib] Re: Need help with test case

Thank you, that helped a lot. /Rene Den tirsdag den 17. november 2015 kl. 10.28.55 UTC+1 skrev Jens: > > At the top is a "reply" button. When you enter text in the corresponding > text box it is a general reply for the CL. You can also add comments for a > file or for a line of source code. To

Re: SEO Google Crawlable experience ?

> > It should be in Elemental 2.0 (I suppose); there's no need to bring an > abstraction on top, JsInterop should suffice. @Thomas, thanks, looking forward to it.​ -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and

Re: [gwt-contrib] Re: New JsInterop document

Your example is correct, this is the way to do. You can also add some logic to your object (for initialization for instance) by using overlay methods @JsType(isNative=true,namespace=JsPackage.GLOBAL,name="Object") public class Options { public String option1; public int option2; @JsOverlay

Re: [gwt-contrib] Re: New JsInterop document

> Options options = new Options().init("some string", 24); > Its not directly mentioned in the new spec document but I hope static methods are also valid for @JsOverlay? E.g. Options options = Options.create("some string", 24); -- J. -- You received this message because you are subscribed

Re: GWT app shows wrong on iPad/Safari?

Hi, in the meantime I found that the solution for IOS made the GUI unusable for Android. The display is shrinked to fit on the screen. There are no scrollbars anymore. Isn't there a solution for this? Or could you limit the viewport tag for ios devices only? Thanks Magnus -- You received

Re: [gwt-contrib] Re: GWTCon 2015 keynote question

I think I need to make a few clarifications. We (we as in Google) are not planning to go on delete any code from GWT-SDK after 2.8 release. Yes, we believe Widget, GWT-RPC, RF etc. reached end of its useful life and we will not invest on them anymore however if there is enough interest/demand

Re: [gwt-contrib] Re: New JsInterop document

Instance methods, static methods and compile time constants can be marked with JsOverlay. Feel free to send a patch for updating the javadoc if it is not already there :) On Tue, Nov 17, 2015 at 4:18 AM, Jens wrote: > > Options options = new Options().init("some

Re: [gwt-contrib] Re: New JsInterop document

Seems to be work ;-) On Tuesday, November 17, 2015 at 1:18:27 PM UTC+1, Jens wrote: > > > Options options = new Options().init("some string", 24); >> > > Its not directly mentioned in the new spec document but I hope static > methods are also valid for @JsOverlay? E.g. > > Options options =

Re: GWT app shows wrong on iPad/Safari?

Hi Magnus, Doesn't the screen go back to non-zoomed mode if you double tap on it? I guess that one way of preventing the auto zoom feature for input fields in IOS is to add user-scalable=no like this: However, that will completely disable zooming and that may not be what you want. I have

Re: [gwt-contrib] Re: New JsInterop document

If the type is native, we don't generate code for the class we assume it exists somewhere. If it is not native, we generate code for the class like we do for every other class. The best way to think about how jsinterop works is thinking with ES6 classes. @JsTypeclass X { static void m() { .. }

Re: [gwt-contrib] Re: GWTCon 2015 keynote question

Exactly, although future releases of GWT will still allow you to create your UI components (you have access to the DOM tree), the point is to reuse external widget collections instead of reinvent the wheel. Obviously nowadays UI designers are much more comfortable writing components using html +

Re: [gwt-contrib] Re: GWTCon 2015 keynote question

On Monday, 16 November 2015 18:52:50 UTC, Jens wrote: > > > I'm not talking about a re-write here, I'm talking about new projects. For >> new projects, I can't see a compelling reason for picking GWT, if the devs >> are going to have to understand JS to use GWT then it is better to invest >>

Re: Mojo's maven-gwt-plugin or Thomas's maven-gwt-plugin?

On Tuesday, November 17, 2015 at 10:11:36 AM UTC+1, Michael Zhou wrote: > > I'm trying to build a Java application with GWT, using maven as the build > system. I'm trying to decide which maven-gwt-plugin to use. > Major differences are: - Mojo's one is tied to a specific version of GWT. To

[gwt-contrib] Re: Need help with test case

I am still a bit puzzled by the gerrit interface. What is the correct way to add a comment to a patch set, or reply to a comment from a reviewer? Den mandag den 16. november 2015 kl. 22.32.18 UTC+1 skrev Rene Hangstrup Møller: > > I would also like a tip on how to run that testcase alone. > >

Re: [gwt-contrib] Re: GWTCon 2015 keynote question

Keep in mind at Google, we write lots of large Web projects, and even the ones that are pure JS (G+, Gmail, Docs, Maps, etc) use Closure Compiler and lots of typing. We find it invaluable. But the world is going mobile, and going forward, you need to support Android, iOS, and Web, and you need to

Re: SEO Google Crawlable experience ?

​@Thomas: besides the fallback hash support, will pushState not be supported at all in the gwt core in the future ? -- 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

Re: SEO Google Crawlable experience ?

On Tuesday, November 17, 2015 at 11:08:02 AM UTC+1, Ed wrote: > > ​@Thomas: besides the fallback hash support, will pushState not be > supported at all in the gwt core in the future ? > It should be in Elemental 2.0 (I suppose); there's no need to bring an abstraction on top, JsInterop should

[gwt-contrib] Steering committees stance on J2CL and the future of GWT?

Based on the videos from the last meetup, and the notes from the steering committee, many of us got the impression that GWT was moving towards being a pure Java-to-Javascript transpiler, and that the official recommendations from the GWT team was for developers to plan ahead for this. *GWT 2.8

[gwt-contrib] Re: Need help with test case

At the top is a "reply" button. When you enter text in the corresponding text box it is a general reply for the CL. You can also add comments for a file or for a line of source code. To do so navigate to the desired patch set (top right drop down) and open the file. At the top middle is a small

Re: SEO Google Crawlable experience ?

On Monday, November 16, 2015 at 5:13:35 PM UTC+1, Ed wrote: > > @Thomas: thanks for your input. Yes, I remember I also looked at your > Html5Historian code as example. > Do you know if or how, the Html5 pushState will be supported in the gwt > core? > I think it should be possible to support

Re: [gwt-contrib] Re: New JsInterop document

Ok I can confirm that the issue was my fault. After moving everything to a JsTyp annotated classes, everything works fine. I have a last question regarding code size and the use if isNative=true. I guess isNative=true is preferred and will make sure that code size stays low by not exposing

Mojo's maven-gwt-plugin or Thomas's maven-gwt-plugin?

I'm trying to build a Java application with GWT, using maven as the build system. I'm trying to decide which maven-gwt-plugin to use. The project's directory structure doesn't follow Maven convention, so I guess I will run into some problems with Thomas' plugin? -- You received this message

Re: Mojo's maven-gwt-plugin or Thomas's maven-gwt-plugin?

Thomas. I have no luck in forcing your plugin (or/and tomcat7-maven-plugin) to work with spring application without web.xml. Whatever I tried I've got INFO: No Spring WebApplicationInitializer types detected on classpath Do you or someone else have any experience with this? -- Tomek Kanka

Re: [gwt-contrib] GWT & Closure library

On Tue, Nov 17, 2015 at 8:36 AM, Mihai Stanciu wrote: > 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