Re: [ANN] (Unofficial) Elemental2 2.24 release
> On Wed, Jun 12, 2019 at 8:29 AM Peter Donald > wrote: > >> On Wed, Jun 12, 2019 at 7:31 AM John Huss > > wrote: >> >>> Out of curiosity, how did you get this project to build successfully? >>> >>> When I try to build it I see this: >>> >>> $ ./bazel_build_test.sh >>> >>> *ERROR: */Users/john/repos/elemental2/third_party/BUILD:21:1: no such >>> target '@com_google_javascript_closure_compiler//:externs': target >>> 'externs' not declared in package '' defined by >>> /private/var/tmp/_bazel_john/b729f51825638d22c4a92cfea6e4556d/external/com_google_javascript_closure_compiler/BUILD >>> >>> and referenced by '//third_party:es6_collections' >>> >>> >>> >> My guess is that you need to do something like this >> >> bazel clean --expunge >> >> This will remove all downloaded repositories (i.e. the closure-compiler >> source code as well as the other remote dependencies) and rebuild them. I >> believe after that it should build cleanly. >> > > That said I just ran this and it seems to be running against the last > binary release of closure compiler ... not the current git repository ... > which will not produce the same jar as I generated as the closure externs > are outdated. I will need to poke around to figure out how to work arouns > this. > That worked, thanks! -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/5b43869e-8228-4649-a98b-8adab3bbe074%40googlegroups.com.
Re: [ANN] (Unofficial) Elemental2 2.24 release
Out of curiosity, how did you get this project to build successfully?
When I try to build it I see this:
$ ./bazel_build_test.sh
*ERROR: */Users/john/repos/elemental2/third_party/BUILD:21:1: no such
target '@com_google_javascript_closure_compiler//:externs': target
'externs' not declared in package '' defined by
/private/var/tmp/_bazel_john/b729f51825638d22c4a92cfea6e4556d/external/com_google_javascript_closure_compiler/BUILD
and referenced by '//third_party:es6_collections'
On Sunday, June 2, 2019 at 8:56:47 PM UTC-5, Peter Donald wrote:
>
> Elemental2 provides type checked access to browser APIs for Java
> code. This is done by using closure extern files and generating
> JsTypes, which are part of the new JsInterop specification that
> is implemented in both GWT and J2CL.
>
> https://github.com/google/elemental2
>
> This is an unofficial release to Maven Central under a different groupId.
> Please don't bug the original authors. Versions are released on demand.
>
> API Changes relative to Elemental2 version 2.23
>
> elemental2-core:
> API Differences:
> https://jsinterop.github.io/api-diff/?key=elemental2-core&old=2.23&new=2.24
> - 39 non breaking changes.
> - 19 potentially breaking changes.
> - 49 breaking changes.
> elemental2-dom:
> API Differences:
> https://jsinterop.github.io/api-diff/?key=elemental2-dom&old=2.23&new=2.24
> - 85 non breaking changes.
> - 68 potentially breaking changes.
> - 165 breaking changes.
> elemental2-indexeddb:
> API Differences:
> https://jsinterop.github.io/api-diff/?key=elemental2-indexeddb&old=2.23&new=2.24
> - 1 non breaking changes.
> elemental2-svg:
> API Differences:
> https://jsinterop.github.io/api-diff/?key=elemental2-svg&old=2.23&new=2.24
> - 1 breaking changes.
> elemental2-webassembly:
> API Differences:
> https://jsinterop.github.io/api-diff/?key=elemental2-webassembly&old=2.23&new=2.24
> - 1 potentially breaking changes.
>
> The complete set of Elemental2 API differences is available at
>
> https://jsinterop.github.io/api-diff/?key=elemental2&old=2.23&new=2.24
>
> The Maven dependencies can be added to your pom.xml via
>
>
> org.realityforge.com.google.elemental2
> ${artifact-id}
> 2.24
>
>
> where artifact-id is one of
>
> * elemental2-core
> * elemental2-dom
> * elemental2-promise
> * elemental2-indexeddb
> * elemental2-svg
> * elemental2-webgl
> * elemental2-media
> * elemental2-webstorage
> * elemental2-webassembly
>
> Hope this helps,
>
> Peter Donald
>
--
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 google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/a7ddd14d-d72d-4f45-ab43-cecb13c267a0%40googlegroups.com.
Re: plugin failed to connect to hosted mode server at...
You can try regenerating the jar index by running this command: jar i gwt-maps.jar -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/8_AvliNl8TcJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 1.52 Compile error
You can try regenerating the jar index by running this command: jar i some-jar-file.jar -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/TkdaLOGtQDAJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Launching dev mode does not overwrite nocache.js
This is a problem I've had in the past. But now it seems to be working, so that's great. Sorry for bothering you! If I have any issues again, I'll let you know. Thanks. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Launching dev mode does not overwrite nocache.js
I will investigate some more. Yes, I have the url parameter. I'm not using a strange linker, but I do have a non-standard (non-J2EE) setup (I'm using WebObjects). I'm using Safari. Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Compiling from Ant - need SDK path
I'm trying to figure out the best (easy) way to do compilation. I figured using the "GWT Compile Project" button would at least be a place to start since that is what it does. But this appears to be pretty much useless because it doesn't allow me to specify the 3rd party libraries that I have, and the settings there are not permanent. So, I can compile using Ant (which is really a better idea anyway), but I'd like to still be able to use my built-in GWT SDK that is installed in Eclipse. So I thought, there must be variable or something that points to this location. Is there? I know I can hard-code the path to the SDK by figuring it out and entering it manually but it really seems like there should be a variable for it. Ideas? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Launching dev mode does not overwrite nocache.js
If I run a compile and then run dev mode it will use the compiled version of the app and will never connect to dev mode since it does not overwrite any of the existing files. So there is no error message. I've worked around the problem for now by creating my own main class for dev mode that deletes the output folder and then starts the regular dev mode main class. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Launching dev mode does not overwrite nocache.js
So does everyone do this same thing (deleted the compiled output before running dev mode), or is there a better way? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Launching dev mode does not overwrite nocache.js
I use the same directory for running dev mode and for doing a regular gwt compile. If I compile first and then try to run dev mode, it won't connect to dev mode because it doesn't overwrite the compiled output with a new nocache.js file. Am I doing something wrong, or is this just how it is supposed to work? I have to delete the compiled output in order to run in dev mode again. Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Debugging css selector problem in UIBuilder
look at the html -> head -> style tag On Jan 13, 12:52 pm, huherto wrote: > I am using the inspector in Chrome. But I cannot see why a css > selector is not working for a specific tag. Is there a way to see how > the is translated from the chrome browser? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
ANN: gwt-mapquest - a MapQuest wrapper for GWT
I've started a project for wrapping the MapQuest API for use in GWT applications. There is already a lot done. So if you're interested in using MapQuest, check it out. Or if you'd like to get your feet wet with learning how to wrap an external Javascript API (or replace it with a native GWT implementation) please consider contributing to the project. Writing wrapper code is very simple and easy to learn. Visit the project link below: http://code.google.com/p/gwt-mapquest/ John -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=.
IE and Buttons without a form
I have a few TextBoxes and some Buttons that are NOT in a or a FormPanel. I have a ClickHandler for the buttons that reads the fields and updates the UI. Additionally I added KeyPressHandlers to the TextBoxes to catch ENTER and then fire the button's action. This works fine in all browsers except IE. In IE, one of the Button wrongly gets hightlighted, presumably because it is the default button, and when I press ENTER the key is not captured by the TextBox but instead something else happens - if I remember correctly it reloads the page. Anyway, my handlers are never executed. So is there any way to: 1) Disable the highlighting of the "default" button 2) Prevent the browser from stealing the ENTER key from the TextBoxes Thanks, John --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Custom Field Serialization
I put together some details about using a CustomFieldSerializer at this page: http://code.google.com/p/wogwt/wiki/CustomFieldSerializer If you still have more questions, ask again. John On Feb 3, 12:05 pm, Vitor Costa wrote: > Hi, > > I would like to know if it is possible to control the serialization of > some fields of an object, so that when it's being deserialized in the > client (when it comes from the server) I can apply some > transformations to that field, and also when it's being serialized in > the client (when it is being sent to the server) I can apply the > reverse transformation to it. > > I've seen some discussions about CustomFieldSerializer but I can't > find any documentation or example on how to do that. > > Thanks in advance, > Vitor. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Adding emulation class
Actually, I created a new project with just this code and it WORKS.
The difference is my real project isn't using RemoteServiceServlet.
I'm just using the RPC class directly as described in it's javadoc; I
have a function:
public String processCall(String payload) throws
SerializationException {
try {
RPCRequest rpcRequest = RPC.decodeRequest(payload, this.getClass
());
return RPC.invokeAndEncodeResponse(this, rpcRequest.getMethod(),
rpcRequest.getParameters());
} catch (IncompatibleRemoteServiceException ex) {
return RPC.encodeResponseForFailure(null, ex);
}
}
I'm wondering if it is using the default serialization policy instead
of a generated one. I tried creating a custom SerializationPolicy
class that allows everything and passed it to
RPC.invokeAndEncodeResponse but it didn't change anything. How can I
tell what policy is being used?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---
Adding emulation class
I'm trying to add some emulation classes for integration with WebObjects. For example, the class NSTimestamp extends java.sql.Timestamp, which is already emulated. I've written the emulation class and the CustomFieldSerializer (the class implements java.io.Serializable). The CustomFieldSerializer is mostly copied from the Timestamp one. The class works on the client with no serialization. But when I do an RPC request using it I get this error: [ERROR] This application is out of date, please click the refresh button on your browser. com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: This application is out of date, please click the refresh button on your browser. at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived (RequestCallbackAdapter.java:204) at com.google.gwt.http.client.Request.fireOnResponseReceivedImpl (Request.java:254) at com.google.gwt.http.client.Request.fireOnResponseReceivedAndCatch (Request.java:226) at com.google.gwt.http.client.Request.fireOnResponseReceived (Request.java:217) Stepping through it a bit, I see that the preceding exception is "SerializationException: com.webobjects.foundation.NSTimestamp" which seems to mean that there was a problem serializing that class. I've verified that the custom serializer's serialize method is getting called and works. What else is needed to support serialization? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
