Re: GWT 2.8.2 and Jetty Embedded - com.google.gwt.dev.jjs.InternalCompilerException: Error constructing Java AST
Thank you Thomas. This is super helpful.
Chris
On Tuesday, February 27, 2018 at 7:18:12 AM UTC-5, Thomas Broyer wrote:
>
> See https://github.com/tbroyer/gwt-maven-archetypes
> You'll have to update things a bit of course as these generate WARs that
> you run in development with the jetty-maven-plugin; for instance, using an
> embedded server would require a dependency:unpack{,-dependencies} and/or
> using the maven-assembly-plugin instead of using a war overlay.
>
> On Monday, February 26, 2018 at 8:53:57 PM UTC+1, Chris wrote:
>>
>> Thanks Thomas, can you point me to any examples of GWT projects split
>> into multiple maven modules?
>> I'll head that route.
>>
>> Thanks again.
>> Chris
>>
>>
>> On Monday, February 26, 2018 at 2:03:29 PM UTC-5, Thomas Broyer wrote:
>>>
>>> apache-jsp brings Eclipse JDT, which causes the conflict.
>>>
>>> As you're using Mojo's plugin for GWT,you can configure it to put GWT
>>> dependencies first in the classpath; that should fix the conflict.
>>>
>>> But you really should split this project into two or three modules, with
>>> separate dependency trees for client and server code. That would
>>> automatically clean all such conflicts.
>>>
>>>
--
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8.2 and Jetty Embedded - com.google.gwt.dev.jjs.InternalCompilerException: Error constructing Java AST
Thanks Thomas, can you point me to any examples of GWT projects split into multiple maven modules? I'll head that route. Thanks again. Chris On Monday, February 26, 2018 at 2:03:29 PM UTC-5, Thomas Broyer wrote: > > apache-jsp brings Eclipse JDT, which causes the conflict. > > As you're using Mojo's plugin for GWT,you can configure it to put GWT > dependencies first in the classpath; that should fix the conflict. > > But you really should split this project into two or three modules, with > separate dependency trees for client and server code. That would > automatically clean all such conflicts. > > -- 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 post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
GWT 2.8.2 and Jetty Embedded - com.google.gwt.dev.jjs.InternalCompilerException: Error constructing Java AST
I've got a real simple scaled down GWT application (to illustrate the issue) with Jetty Embedded Server (9.4.7.v20170914), it can be downloaded here: This works fine when running under 2.7.0. Unfortunately, when I upgrade to 2.8.2, I'm getting an error during the GWT compilation stage. See below. Any suggestions in how I can fix this? It seems like there is a conflict between Jetty deps and GWT 2.8.2 deps and I probably need some kind of exclude, but I'm not super familiar with maven enough to tell it how to exclude what it needs so this compiles. The simple application be be downloaded from: https://www.dropbox.com/s/1myj5o3dpq9bzxt/gwt_jetty.zip?dl=0 Really appreciate any help in this. Thanks, Chris Here is the GWTC output: *--- *gwt-maven-plugin:2.8.2:compile *(default)* @ my-app* ---* [*INFO*] Compiling module com.mycompany.app.MyWebApp [*INFO*] [ERROR] An internal compiler exception occurred [*INFO*] com.google.gwt.dev.jjs.InternalCompilerException: Error constructing Java AST [*INFO*] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.translateException(GwtAstBuilder.java:3997) [*INFO*] at com.google.gwt.dev.jjs.impl.GwtAstBuilder$AstVisitor.endVisit(GwtAstBuilder.java:1569) [*INFO*] at org.eclipse.jdt.internal.compiler.ast.MessageSend.traverse(MessageSend.java:1021) [*INFO*] at org.eclipse.jdt.internal.compiler.ast.Assignment.traverse(Assignment.java:260) [*INFO*] at org.eclipse.jdt.internal.compiler.ast.Block.traverse(Block.java:136) [*INFO*] at org.eclipse.jdt.internal.compiler.ast.IfStatement.traverse(IfStatement.java:281) [*INFO*] at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.traverse(MethodDeclaration.java:347) [*INFO*] at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1379) [*INFO*] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.processImpl(GwtAstBuilder.java:3933) [*INFO*] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.process(GwtAstBuilder.java:3971) Here is what my dependency tree looks like this: mvn dependency:tree -Dverbose=true [*INFO*] Scanning for projects... [*WARNING*] [*WARNING*] Some problems were encountered while building the effective model for com.mycompany.app:my-app:jar:1.0-SNAPSHOT [*WARNING*] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-resources-plugin is missing. @ line 173, column 21 [*WARNING*] [*WARNING*] It is highly recommended to fix these problems because they threaten the stability of your build. [*WARNING*] [*WARNING*] For this reason, future Maven versions might no longer support building such malformed projects. [*WARNING*] [*INFO*] [*INFO*] ** [*INFO*] *Building Maven Archetype for GWT 1.0-SNAPSHOT* [*INFO*] ** [*INFO*] [*INFO*] *--- *maven-dependency-plugin:2.8:tree *(default-cli)* @ my-app* ---* [*INFO*] com.mycompany.app:my-app:jar:1.0-SNAPSHOT [*INFO*] +- junit:junit:jar:4.11:test [*INFO*] | \- org.hamcrest:hamcrest-core:jar:1.3:test [*INFO*] +- org.eclipse.jetty:jetty-server:jar:9.4.7.v20170914:compile [*INFO*] | +- javax.servlet:javax.servlet-api:jar:3.1.0:compile [*INFO*] | +- org.eclipse.jetty:jetty-http:jar:9.2.14.v20151106:compile (version managed from 9.4.7.v20170914) [*INFO*] | | \- (org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile - omitted for conflict with 9.4.7.v20170914) [*INFO*] | \- org.eclipse.jetty:jetty-io:jar:9.2.14.v20151106:compile (version managed from 9.4.7.v20170914) [*INFO*] | \- (org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile - omitted for duplicate) [*INFO*] +- org.eclipse.jetty:jetty-annotations:jar:9.4.7.v20170914:compile [*INFO*] | +- org.eclipse.jetty:jetty-plus:jar:9.2.14.v20151106:compile (version managed from 9.4.7.v20170914) [*INFO*] | | +- (org.eclipse.jetty:jetty-webapp:jar:9.2.14.v20151106:compile - version managed from 9.4.7.v20170914; omitted for duplicate) [*INFO*] | | \- org.eclipse.jetty:jetty-jndi:jar:9.2.14.v20151106:compile [*INFO*] | | \- (org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile - omitted for duplicate) [*INFO*] | +- (org.eclipse.jetty:jetty-webapp:jar:9.2.14.v20151106:compile - version managed from 9.4.7.v20170914; omitted for conflict with 9.4.7.v20170914) [*INFO*] | +- javax.annotation:javax.annotation-api:jar:1.2:compile [*INFO*] | +- org.ow2.asm:asm:jar:5.0.3:compile (version managed from 5.1) [*INFO*] | \- org.ow2.asm:asm-commons:jar:5.0.3:compile (version managed from 5.1) [*INFO*] | \- org.ow2.asm:asm-tree:jar:5.0.3:compile [*INFO*] |\- (org.ow2.asm:asm:jar:5.0.3:compile - version managed from 5.1; omitted for duplicate) [*INFO*] +- org.eclipse.jetty:jetty-webapp:jar:9.4.7.v20170914:compile [*INFO*] | +- org.eclipse.jetty:jetty-xml:jar:9.2.14.v20151106:compile (version managed from 9.4.7.v20170914) [*INFO
Re: JsInterop Shared Model + REST API
Paul,
If I go with T Broyer's suggestion of making User extend JavaScriptObject
then would interop-utils be able to handle an array property User[] users
within User for deserialization?
I'm trying to work around the issue of having a list deserialized as its
correct type. Ultimately I'd like to get my User[] back in browser
JavaScript and be able to do
var users = ...deserialized User[]
users[0].getValue();
where getValue() is a @JsMethod
I'm realizing now that I can't do that unless @JsType(isNative = false
because overlay methods can't be accessed from JavaScript. Doing that
causes a casting issue when using gwt.interop.utils.client.JSON to parse my
incoming JSON string.
On Saturday, November 18, 2017 at 7:02:37 AM UTC-5, Paul Stockley wrote:
>
> gwt-interop-utils shows one way of doing it. This assumes you are OK using
> intermediate collection types.
>
> https://github.com/GWTReact/gwt-interop-utils/blob/master/DOCUMENTATION.md
>
>
>
> On Saturday, November 18, 2017 at 3:52:09 AM UTC-5, Chris L wrote:
>>
>> I'm trying to create a shared model in my GWT 2.8.2 application that I
>> can use both at the server and in GWT client code.
>>
>> My research/Google Fu tells me that this might be possible with JsInterop
>> but since I'm new to JsInterop I'm just not sure.
>> I've done some experiments but I've run into a couple of issues with the
>> biggest being that I can't have my model accessor methods if I make the
>> model native. The compiler tells me that they have to be native or
>> abstract.
>>
>> What I'd like to do with my model is:
>> @JsType
>> public class User {
>> private double id;
>> private String code;
>> private String name;
>>
>> @JsConstructor
>> public User() {
>> }
>>
>> @JsIgnore
>> public User(double id, String code, String name) {
>> this();
>>
>> this.id = id;
>> this.code = code;
>> this.name = name;
>> }
>>
>> ...
>> @JsProperty
>> public double getId() {
>> return id;
>> }
>>
>> @JsProperty
>> public double setId(double id) {
>> this.id = id;
>> }
>> ...
>> }
>>
>> Then in my GWT application I'd like to do this:
>>
>> public class JsTypes {
>>
>> public static native T getJsTypeObject(JavaScriptObject
>> result)/*-{
>> return result;
>> }-*/;
>> }
>>
>> //called after REST response from server
>> private void onCallback(String json) {
>> Console.log("JSON:" + json);
>> JavaScriptObject result = JsonUtils.safeEval(json);
>> User user = JsTypes.getJsTypeObject(result);
>> ...
>> //do something with user
>>}
>>
>> Any ideas or suggestions would be greatly appreciated.
>>
>
--
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
JsInterop Shared Model + REST API
I'm trying to create a shared model in my GWT 2.8.2 application that I can
use both at the server and in GWT client code.
My research/Google Fu tells me that this might be possible with JsInterop
but since I'm new to JsInterop I'm just not sure.
I've done some experiments but I've run into a couple of issues with the
biggest being that I can't have my model accessor methods if I make the
model native. The compiler tells me that they have to be native or
abstract.
What I'd like to do with my model is:
@JsType
public class User {
private double id;
private String code;
private String name;
@JsConstructor
public User() {
}
@JsIgnore
public User(double id, String code, String name) {
this();
this.id = id;
this.code = code;
this.name = name;
}
...
@JsProperty
public double getId() {
return id;
}
@JsProperty
public double setId(double id) {
this.id = id;
}
...
}
Then in my GWT application I'd like to do this:
public class JsTypes {
public static native T getJsTypeObject(JavaScriptObject
result)/*-{
return result;
}-*/;
}
//called after REST response from server
private void onCallback(String json) {
Console.log("JSON:" + json);
JavaScriptObject result = JsonUtils.safeEval(json);
User user = JsTypes.getJsTypeObject(result);
...
//do something with user
}
Any ideas or suggestions would be greatly appreciated.
--
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Re: Setting Width of a TextBox inside LayoutPanel
My original issue was that for textboxes, the call to
pnl.setWidgetLeftWidth(tb, 0, Unit.PCT, 100, Unit.Pct);
does not work. Other widgets are fine, but for some reason textbox is
different.
.LabelledTextBox {
-webkit-box-sizing: border-box;
-moz-box-sizing: border-box;
box-sizing: border-box;
width:100%;
height:100%;
}
> On Sep 13, 2016, at 9:52 AM, Eddy <eddy.jaqui...@gmail.com> wrote:
>
> Hello Chris,
>
> I am not an expert about GWT but I always added a panel into a layoutpanel
> before. After that I added my widgets into the panel.
> I am telling about SimplePanel for only one widget or FlowPanel for putting
> several widgets into.
>
> For example, I used a DockLayoutPanel (and think it is the same for
> layoutpanel), I set it in Unit.PX made a setSize("100%", "100%").
> Then I instanciated a flowPanel, with a setSize("100%", "100%") too, and
> added my widgets into (telling about the view into an MVP model).
> I ensured the view implements RequiresResize, ProvidesResize and implemented
> some resizes code on the widgets I want to resize.
> The behaviour is that when the user resize the browser, the container
> layoutPanel resize too and the panel take "dynamically" the size of the
> layoutpanel.
> => perhaps you could set the size of your texbox = size panel and see what
> happens.
The issue is not that the panels are incorrectly sized, but that the TextBox
inside the panel does not expand to take up 100% of its container width, even
though I call
pnl.setWidgetLeftWidth(tb, 0, Unit.PCT, 100, Unit.Pct);
Other non-textbox widgets seem to behave just fine. Not sure what is
different about TextBox.
I did get it to behave the way I wanted using the following workaround… not
fully programmatic, had to use CSS:
tb.setStylePrimaryName("LabelledTextBox");
and then putting this in the CSS:
.LabelledTextBox {
-webkit-box-sizing: border-box;
-moz-box-sizing: border-box;
box-sizing: border-box;
width:100%;
height:100%;
}
>
> Excuses me for my english but i am french :-)
>
> Hope it could help
>
> Eddy
>
> Le mercredi 20 juillet 2016 00:16:56 UTC+2, Chris Odd a écrit :
> Hello all,
>
> I have a LayoutPanel with one widget added to it (a TextBox). I want to
> make the TextBox's width equal to the LayoutPanel's width.
>
> I thought this would work, but it does not (the TextBox is much narrower than
> the LayoutPanel's width):
>
> LayoutPanel pnl = new LayoutPanel();
> TextBox tb = new TextBox();
> pnl.add(tb);
>
> pnl.setWidgetLeftWidth(tb, 0, Unit.PCT, 100, Unit.Pct);
>
> Any idea why it doesn't work? Or ideas for a better approach?
>
>
> 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
> <mailto:google-web-toolkit+unsubscr...@googlegroups.com>.
> To post to this group, send email to google-web-toolkit@googlegroups.com
> <mailto:google-web-toolkit@googlegroups.com>.
> Visit this group at https://groups.google.com/group/google-web-toolkit
> <https://groups.google.com/group/google-web-toolkit>.
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
--
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Setting Width of a TextBox inside LayoutPanel
Hello all, I have a LayoutPanel with one widget added to it (a TextBox). I want to make the TextBox's width equal to the LayoutPanel's width. I thought this would work, but it does not (the TextBox is much narrower than the LayoutPanel's width): LayoutPanel pnl = new LayoutPanel(); TextBox tb = new TextBox(); pnl.add(tb); pnl.setWidgetLeftWidth(tb, 0, Unit.PCT, 100, Unit.Pct); Any idea why it doesn't work? Or ideas for a better approach? 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 post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Remove client side javascript from server
Hi Everyone, For security reason, we don't want user be able to download client side javascript from web server. Instead, we want to package client side scripts into a chrome app (.crx) and hand it to user offline. So when visiting our web page, people who don't have this chrome app pre-installed will not work. Is this possible? How should I configure chrome app (manifest.json) and web application (web-inf/*)? Thanks a lot!! Chris -- 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 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.
no runtime error stacktraces showing up in devmode
I'm running devmode through maven plugin (only mention because I'm not sure it is related) and I can't seem to get any stack traces of errors encountered from the client code. When I run my GWT app, I don't see any third tab appearing like example here: http://www.gwtproject.org/doc/latest/images/DevelopmentShell2.png Source http://www.gwtproject.org/doc/latest/images/DevelopmentShell2.png (see it has a Hello (FF) tab). Nor, any nice stack traces like this: http://www.gwtproject.org/doc/latest/images/DevelopmentShell3.png Source: http://www.gwtproject.org/doc/latest/images/DevelopmentShell3.png Everything is hidden or behind a javascript error, for example I put this in my code: Integer i = null; i.intValue(); Which should obviously generate a null pointer, but rather than a nice stack trace, I see this in the Chrome console but nothing in devmode window or on the terminal console. [15:32:37.971] Wed Jul 22 15:32:37 GMT-400 2015 com.google.gwt.logging.client.LogConfiguration SEVERE: (TypeError) : i_0_g$ is nullcom.google.gwt.core.client.JavaScriptException: (TypeError) : i_0_g$ is null at Unknown.onModuleLoad2_0_g$(http://127.0.0.1) at Unknown.execute_64_g$(http://127.0.0.1) at Unknown.doExecuteCommands_0_g$(http://127.0.0.1) at Unknown.run_7_g$(http://127.0.0.1) at Unknown.fire_0_g$(http://127.0.0.1) at Unknown.createCallback_0_g$/(http://127.0.0.1) at Unknown.apply_0_g$(http://127.0.0.1) at Unknown.entry0_0_g$(http://127.0.0.1) at Unknown.entry_1_g$/(http://127.0.0.1) at Unknown.anonymous(Unknown) Any idea what I'm doing wrong, why can't I see stack traces anymore. I'm using GWT 2.7 with chrome and would really appreciate any help. It is difficult to debug without nice stack traces! Chris -- 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+unsubscr...@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: no runtime error stacktraces showing up in devmode
Thanks, this is really helpful... I'm actually using IntelliJ 14, but even when I setup with IntelliJ, I'm not getting any stack traces... Do I need to be using GWT 2.8 SNAPSHOT with IntelliJ too? When I run it with IntelliJ, I'm not getting any stack traces either, at least with GWT 2.7. Chris On Wednesday, July 22, 2015 at 5:37:02 PM UTC-4, Jens wrote: You are not doing anything wrong, the website is a bit outdated. By default GWT 2.7 DevMode now uses the so called SuperDevMode (SDM). SDM compiles all your Java source to JavaScript and thats why you see JavaScript exceptions inside your Chrome console instead of Java exceptions inside the DevMode window. The old, classic DevMode which actually executes your Java code as Java and thus produces Java exceptions is considered deprecated because it requires a browser plugin which does not work anymore in most recent browser versions. So you should get used to the JavaScript exceptions. If you can, I would recommend using GWT 2.8 SNAPSHOT which has quite some logging fixes. With these fixes you should always have a link next to each exception stack frame in Chrome console which points to the corresponding Java file + line number. If you click on the link then Chrome will show you the Java file. If you can not use GWT 2.8 SNAPSHOT then you could try using https://gist.github.com/jnehlmeier/cddbc476fd330b1d4999 to get links to Java files in JavaScript stack traces. There is also an Eclipse plugin on Github called SDBG which allows you to connect from Eclipse to your Chrome browser. Then all Chrome console output is redirected to your Eclipse console and you can also set break points inside Eclipse which will be synced with the browser. IntelliJ 14 supports this out of the box. -- J. -- 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+unsubscr...@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: no runtime error stacktraces showing up in devmode
Thank you... So this did the trick...
public void onModuleLoad() {
GWT.setUncaughtExceptionHandler(new SuperDevModeUncaughtExceptionHandler());
I still don't see the exceptions in IntelliJ, but least I'm getting
class/line number of errors found in the Javascript console, which is much
more helpful than the JS errors.
Thanks again.
Chris
On Wednesday, July 22, 2015 at 6:32:20 PM UTC-4, Chris wrote:
Thanks, this is really helpful... I'm actually using IntelliJ 14, but even
when I setup with IntelliJ, I'm not getting any stack traces... Do I need
to be using GWT 2.8 SNAPSHOT with IntelliJ too? When I run it with
IntelliJ, I'm not getting any stack traces either, at least with GWT 2.7.
Chris
On Wednesday, July 22, 2015 at 5:37:02 PM UTC-4, Jens wrote:
You are not doing anything wrong, the website is a bit outdated. By
default GWT 2.7 DevMode now uses the so called SuperDevMode (SDM). SDM
compiles all your Java source to JavaScript and thats why you see
JavaScript exceptions inside your Chrome console instead of Java exceptions
inside the DevMode window.
The old, classic DevMode which actually executes your Java code as Java
and thus produces Java exceptions is considered deprecated because it
requires a browser plugin which does not work anymore in most recent
browser versions.
So you should get used to the JavaScript exceptions. If you can, I would
recommend using GWT 2.8 SNAPSHOT which has quite some logging fixes. With
these fixes you should always have a link next to each exception stack
frame in Chrome console which points to the corresponding Java file + line
number. If you click on the link then Chrome will show you the Java file.
If you can not use GWT 2.8 SNAPSHOT then you could try using
https://gist.github.com/jnehlmeier/cddbc476fd330b1d4999 to get links to
Java files in JavaScript stack traces.
There is also an Eclipse plugin on Github called SDBG which allows you to
connect from Eclipse to your Chrome browser. Then all Chrome console output
is redirected to your Eclipse console and you can also set break points
inside Eclipse which will be synced with the browser. IntelliJ 14 supports
this out of the box.
-- J.
--
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+unsubscr...@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-contrib] Class literals for JsTypes in superdevmode
Roberto, if it's any hint to the underlying problem: you're right that that
the class is not reference anywhere else—it is used solely for the purpose
of type coercion.
Chris
On Tue, Jun 9, 2015 at 10:48 AM 'Ray Cromwell' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
Chris,
My change actually fixed a bug which may have obscured a problem. There
were duplicate class literals being generated. So you'd get
InterfaceFoo.class twice in the output, and it may be in SDM you'd be
covered, but in regular compiled mode you'd get the duplicates which were
causing closure compiler issues.
Roberto, Maybe this is an issue with
ControlFlowRecorder/RapidTypeAnalyzer and interface literals?
On Tue, Jun 9, 2015 at 9:43 AM, 'Chris DiGiano' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
@Ray, rolling back your change indeed fixed the problem (
https://gwt-review.googlesource.com/#/c/12311/). How do you recommend we
proceed? Anything I can do to help?
@Roberto, thanks for your suggestion, but I had already tried restarting
the code server and clearing the cache. This did not fix things.
Chris
On Mon, Jun 8, 2015 at 6:55 PM 'Roberto Lublinerman' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
This might be due to the way we handle class literals. Class literals
for interfaces if not referenced during the initial compile might cause
that error. The error should go aways if you restart SDM.
The offending sequence is
0) Suppose initially you have (interface A, class B and class C) and
start SDM.
1) Now edit class B to add a reference to A.class and recompile with SDM
(do not touch A at this time nor anything that makes it recompile) . This
should work fine because the literals that are referenced but whose classes
where not part of this compile will be generated in the epilogue.
2) Now edit class C in any way that does not make B or A recompile. Here
you will have an error like the one you described.
If you restart SDM at this point it should work.
I'll get a fix for this tomorrow.
On Mon, Jun 8, 2015 at 3:23 PM, 'Ray Cromwell' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
Ooops, wrong pointer (for external users) This one
https://gwt-review.googlesource.com/#/c/12311/
On Mon, Jun 8, 2015 at 3:14 PM, Ray Cromwell cromwell...@google.com
wrote:
Try rolling back this CL and see if it fixes it (
https://critique.corp.google.com/#review/92873682/depot/google3/third_party/java_src/gwt/svn/trunk/dev/core/src/com/google/gwt/dev/jjs/impl/GenerateJavaScriptAST.java
)
On Mon, Jun 8, 2015 at 3:04 PM, Chris DiGiano d...@google.com wrote:
I'm having trouble referencing a JsType interface when running under
superdevmode. I'm trying to pass the JsType as a class reference to a
method that uses the class to coerce the results into the expected type:
myelement.getCustomStampedElement(dialog,
PolymerDialog.class).open();
Unfortunately, in superdevmode (and only in SDM) I get this error:
Uncaught ReferenceError:
Lcom_google_ccc_groups_rosters_frontend_polymer_jstype_PolymerDialog_2_classLit_0_g$
is not defined
PolymerDialog is declared like this:
@JsType
public interface PolymerDialog {
void open();
}
and getCustomStampedElement is defined like this:
/**
* Returns the element specified in this custom element's
template that matches the given id
* with the result coerced to a non-vanilla element type.
Equivalent to Polymer's $ function.
*
* @see
* a href=
https://www.polymer-project.org/1.0/docs/devguide/local-dom.html#node-finding
* Polymer automatic node finding/a
*/
T T getCustomStampedElement(String id, ClassT type);
It appears that the PolymerDialog JsType is being left out of the
list of class literals available in superdevmode. Is this a bug? Any
ideas
for workarounds?
Chris DiGiano
--
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/9826758e-1b0f-4797-8902-738a1fade037%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/9826758e-1b0f-4797-8902-738a1fade037%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
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
Re: [gwt-contrib] Class literals for JsTypes in superdevmode
@Ray, rolling back your change indeed fixed the problem (
https://gwt-review.googlesource.com/#/c/12311/). How do you recommend we
proceed? Anything I can do to help?
@Roberto, thanks for your suggestion, but I had already tried restarting
the code server and clearing the cache. This did not fix things.
Chris
On Mon, Jun 8, 2015 at 6:55 PM 'Roberto Lublinerman' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
This might be due to the way we handle class literals. Class literals for
interfaces if not referenced during the initial compile might cause that
error. The error should go aways if you restart SDM.
The offending sequence is
0) Suppose initially you have (interface A, class B and class C) and start
SDM.
1) Now edit class B to add a reference to A.class and recompile with SDM
(do not touch A at this time nor anything that makes it recompile) . This
should work fine because the literals that are referenced but whose classes
where not part of this compile will be generated in the epilogue.
2) Now edit class C in any way that does not make B or A recompile. Here
you will have an error like the one you described.
If you restart SDM at this point it should work.
I'll get a fix for this tomorrow.
On Mon, Jun 8, 2015 at 3:23 PM, 'Ray Cromwell' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
Ooops, wrong pointer (for external users) This one
https://gwt-review.googlesource.com/#/c/12311/
On Mon, Jun 8, 2015 at 3:14 PM, Ray Cromwell cromwell...@google.com
wrote:
Try rolling back this CL and see if it fixes it (
https://critique.corp.google.com/#review/92873682/depot/google3/third_party/java_src/gwt/svn/trunk/dev/core/src/com/google/gwt/dev/jjs/impl/GenerateJavaScriptAST.java
)
On Mon, Jun 8, 2015 at 3:04 PM, Chris DiGiano d...@google.com wrote:
I'm having trouble referencing a JsType interface when running under
superdevmode. I'm trying to pass the JsType as a class reference to a
method that uses the class to coerce the results into the expected type:
myelement.getCustomStampedElement(dialog,
PolymerDialog.class).open();
Unfortunately, in superdevmode (and only in SDM) I get this error:
Uncaught ReferenceError:
Lcom_google_ccc_groups_rosters_frontend_polymer_jstype_PolymerDialog_2_classLit_0_g$
is not defined
PolymerDialog is declared like this:
@JsType
public interface PolymerDialog {
void open();
}
and getCustomStampedElement is defined like this:
/**
* Returns the element specified in this custom element's template
that matches the given id
* with the result coerced to a non-vanilla element type.
Equivalent to Polymer's $ function.
*
* @see
* a href=
https://www.polymer-project.org/1.0/docs/devguide/local-dom.html#node-finding
* Polymer automatic node finding/a
*/
T T getCustomStampedElement(String id, ClassT type);
It appears that the PolymerDialog JsType is being left out of the list
of class literals available in superdevmode. Is this a bug? Any ideas for
workarounds?
Chris DiGiano
--
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/9826758e-1b0f-4797-8902-738a1fade037%40googlegroups.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/9826758e-1b0f-4797-8902-738a1fade037%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
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/CAPVRV7fZhv0AkiPYqfM2WWaW8zFvdgk-BYEucwRP8k4ewXEp6w%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7fZhv0AkiPYqfM2WWaW8zFvdgk-BYEucwRP8k4ewXEp6w%40mail.gmail.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
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/CAC7T7gk_U85%2B6z1QK9XpAKEXbBJgviBfZ1j0kgE8_pYZsV6Y3g%40mail.gmail.com
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gk_U85
[gwt-contrib] Class literals for JsTypes in superdevmode
I'm having trouble referencing a JsType interface when running under
superdevmode. I'm trying to pass the JsType as a class reference to a
method that uses the class to coerce the results into the expected type:
myelement.getCustomStampedElement(dialog, PolymerDialog.class).open();
Unfortunately, in superdevmode (and only in SDM) I get this error:
Uncaught ReferenceError:
Lcom_google_ccc_groups_rosters_frontend_polymer_jstype_PolymerDialog_2_classLit_0_g$
is not defined
PolymerDialog is declared like this:
@JsType
public interface PolymerDialog {
void open();
}
and getCustomStampedElement is defined like this:
/**
* Returns the element specified in this custom element's template that
matches the given id
* with the result coerced to a non-vanilla element type. Equivalent to
Polymer's $ function.
*
* @see
* a
href=https://www.polymer-project.org/1.0/docs/devguide/local-dom.html#node-finding;
* Polymer automatic node finding/a
*/
T T getCustomStampedElement(String id, ClassT type);
It appears that the PolymerDialog JsType is being left out of the list of
class literals available in superdevmode. Is this a bug? Any ideas for
workarounds?
Chris DiGiano
--
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/9826758e-1b0f-4797-8902-738a1fade037%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: JsInterop
Have you enabled jsInterop mode via the compiler flag? It looks like this on the command line: -XjsInteropMode JS Chris On Tue Sep 30 2014 at 7:05:23 AM Michael Vogt mich...@michaelvogt.eu wrote: Btw, when calling parse() out of jsni or in the browser console, it works fine. So the Javascript side is ok. -- 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/443bbcf0-bc50-4c3e-aacb-bc38c6c1c85d%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/443bbcf0-bc50-4c3e-aacb-bc38c6c1c85d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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/CAHbZCdNdV4jAcSmssxiJQL%2BxgH1oenQqUbgbzL4d0Ba%2BJm7mzg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
I had this problem also. There is no need to mess around with the registry though. The fix is to run Eclipse as Administrator and compile your project. It will create the registry key for you, then you can restart Eclipse as a normal user and you won't have the warning anymore. -- 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+unsubscr...@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.
Can I use replace-with / to replace a Google class?
Hi, I am having problems running in hosted mode (GWT 2.6.1) as a result of a possible bug in com.google.gwt.dom.client.StyleInjector.java (see Issue 8863 https://code.google.com/p/google-web-toolkit/issues/detail?id=8863). The fix is simple, so I have created my own version of the problem class in my Eclipse project, and specified a replace-with / in the module file: replace-with class=com.db.patch.StyleInjectorImplIE when-type-is class=com.google.gwt.dom.client.StyleInjector.StyleInjectorImplIE/ /replace-with It doesn't seem to work. Using the debugger, I still see the code in the original class being executed, and the resulting ArrayIndexOutOfBoundsException is thrown. Is there a reason why I can't replace this class? If so, can anyone suggest a way to get my patch into the project, preferably without replacing or modifying gwt-user-2.6.1.jar? It looks like the original StyleInjector.StyleInjectorImplIE may be replacing StyleInjector.StyleInjectorImplIE. Does replace-with / recurse through multiple levels of replacement? Is there a way to see what browser-specific replacements happen by default? Thanks, Chris -- 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+unsubscr...@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: Can I use replace-with / to replace a Google class?
As usual, I found the solution within 15 minutes of posting the question. The default replacement that GWT does is com.google.gwt.dom.client.StyleInjector.StyleInjectorImplIE for com.google.gwt.dom.client.StyleInjector.StyleInjectorImpl, so I need to replace my patched version of the IE injector for the class that GWT replaces, and I need to limit it to IE, because that's what the default does. Also, the replacement class need to be in a client package. replace-with class=com.db.dbpalace.client.patch.StyleInjectorImplIE when-type-is class=com.google.gwt.dom.client.StyleInjector.StyleInjectorImpl / any when-property-is name=user.agent value=ie8 / when-property-is name=user.agent value=ie10 / /any /replace-with Chris On Friday, 15 August 2014 15:15:58 UTC+1, chris-x...@db.com wrote: Hi, I am having problems running in hosted mode (GWT 2.6.1) as a result of a possible bug in com.google.gwt.dom.client.StyleInjector.java (see Issue 8863 https://code.google.com/p/google-web-toolkit/issues/detail?id=8863 ). The fix is simple, so I have created my own version of the problem class in my Eclipse project, and specified a replace-with / in the module file: replace-with class=com.db.patch.StyleInjectorImplIE when-type-is class=com.google.gwt.dom.client.StyleInjector.StyleInjectorImplIE/ /replace-with It doesn't seem to work. Using the debugger, I still see the code in the original class being executed, and the resulting ArrayIndexOutOfBoundsException is thrown. Is there a reason why I can't replace this class? If so, can anyone suggest a way to get my patch into the project, preferably without replacing or modifying gwt-user-2.6.1.jar? It looks like the original StyleInjector.StyleInjectorImplIE may be replacing StyleInjector.StyleInjectorImplIE. Does replace-with / recurse through multiple levels of replacement? Is there a way to see what browser-specific replacements happen by default? Thanks, Chris -- 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+unsubscr...@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.
How to make SuggestBox display scroll properly?
I'm working with a SuggestBox that produces a very large number of suggestions on the first one or two chanracters. I don't want an ugly list that disappears off the bottom of the screen, so I've made the selection display scroll by adding height and overflow to the CSS for .gwt-SuggestBoxPopup .suggestPopupContent. It all works fine until I try to move through the selection list using the keyboard. The selected element does not scroll into view. This is obviously not going to pass any UX tests. I've subclassed SuggestBox.DefaultSuggestionDisplay in the hope of being able to scroll the selected element into view as part of the moveSelectionDown() and moveSelectionUp() methods. But it seems that to get to the Element selected I need access to the suggestionMenu field, and that, for some reason, is private, so the subclass can't see it. Oh well, I guess I can copy the code from SuggestBox.DefaultSuggestionDisplay and implement my own version. This sort of cut-n-paste inheritance goes against decent Java principles, but it's only 280 lines or so. No luck - SuggestBox.DefaultSuggestionDisplay has a dependence on the private class SuggestBox.SuggestionMenu. At this point the only solution I can think of is to search the DOM for an element with with a CSS class of item-selected. Does anyone know of a better solution? I would be delighted to hear it. Chris -- 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+unsubscr...@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: parsing library for the client side
lpetit laurent.petit@... writes: Thanks guys for the encouragements ! Anybody could give feedback ? Anybody already tried to do this already ? Hi, I recently wrote a blog on the subject of how to write a client-side parser using GWT JavaCC. The new version of JavaCC 6.1 means that there are no modifications required to your Java code, as long as your client side parsing library stays within the emulated classes of GWT. http://consoliii.blogspot.co.uk/2014/04/creating-gwt-compatible-parser- using.html Regards, Chris -- 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+unsubscr...@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.
GWT XML File Validation Errors in Eclipse
Working GWT 2.5.1 today, I was unable to clear errors on the validation of any of my project's modules (gwt.xml) and uibinder (ui.xml) files. These file were not changed from my last close of the Eclipse IDE (Kepler) and I don't recall making any changes to the environment. To be more clear, any existing or newly created gwt.xml appears as: https://lh5.googleusercontent.com/-O34886gfdRY/Uu-7y7rmzWI/BEo/nWzrtP36GcM/s1600/one.png The error detail is: https://lh5.googleusercontent.com/-cd2vCJKms1k/Uu-76-vG-1I/BEw/xK6n-voioI0/s1600/two.png This error is similar for uibinder files. I have tried: - Re-imported project - Updated the Google Plug-in and GWT sdk - Turned off Validator builders (faceted project validation builder, validation) - Created new Google Web Application project - This is interesting because there is no error here Any other ideas? -- 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+unsubscr...@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/groups/opt_out.
Re: GWT XML File Validation Errors in Eclipse
Looks like I fixed it. After analysis, it seems that this problem occurred after connecting to Amtrak's Wifi which has a weird accept-terms requirement. My best guess is that corrupted files were downloaded and cached. The errors went away after clearing the cache in Eclipse (*Window Preferences Network Connections Cache Remove All*). Probably should disable the caching here to prevent that in the future. On Monday, February 3, 2014 11:08:04 AM UTC-5, Chris wrote: Working GWT 2.5.1 today, I was unable to clear errors on the validation of any of my project's modules (gwt.xml) and uibinder (ui.xml) files. These file were not changed from my last close of the Eclipse IDE (Kepler) and I don't recall making any changes to the environment. To be more clear, any existing or newly created gwt.xml appears as: https://lh5.googleusercontent.com/-O34886gfdRY/Uu-7y7rmzWI/BEo/nWzrtP36GcM/s1600/one.png The error detail is: https://lh5.googleusercontent.com/-cd2vCJKms1k/Uu-76-vG-1I/BEw/xK6n-voioI0/s1600/two.png This error is similar for uibinder files. I have tried: - Re-imported project - Updated the Google Plug-in and GWT sdk - Turned off Validator builders (faceted project validation builder, validation) - Created new Google Web Application project - This is interesting because there is no error here Any other ideas? -- 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+unsubscr...@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/groups/opt_out.
Re: GWT XML File Validation Errors in Eclipse
Looks like I fixed it. After analysis, it seems that this problem occurred after connecting to Amtrak's Wifi which has a weird accept-terms requirement. My best guess is that corrupted files were downloaded and cached. The errors went away after clearing the cache in Eclipse (*Window Preferences Network Connections Cache Remove All*). Probably should disable the caching here to prevent that in the future. -- 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+unsubscr...@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/groups/opt_out.
GWT.create Session videos
I was unable to attend the gwt.create event but am wondering if I will be able to view the sessions somewhere? Thanks, Chris -- 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+unsubscr...@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/groups/opt_out.
Re: gwt-2.6.0-rc1 can't compile guava-gwt
Sorry, I'm doing a poor job of following the threading. The fix that Thomas identified is in Guava 15: http://code.google.com/p/guava-libraries/source/detail?r=1908e9db5c671f0ef95202b8b0aab1ade954bd0fname=release15 I wouldn't expect there to be problems with that version. Iker, can you double-check that all copies of Guava 14 were removed from your dependencies when you tested with Guava 15? -- 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+unsubscr...@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/groups/opt_out.
Re: gwt-2.6.0-rc1 can't compile guava-gwt
[re-sending now that I think I have group posting permissions] I see the problem with GWT 2.6 + Guava 15 but not with GWT 2.5 + Guava 15 or GWT 2.6 + Guava 14. I suspect that Michael is right that Java 7's changes to generics enforcement are responsible. I assume that we fixed the problem for Guava 15 when switching to Java 7 for our non-GWT compiles. Are you able to update to Guava 15 (or at least to easily verify that that Guava 15 solves the problem, in case I got my tests mixed up)? -- 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+unsubscr...@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/groups/opt_out.
Dynamic Output?
Hello, I'm just learning GWT and I've noticed that there's no documentation about producing dynamic output. By which I mean the ability to, for example, make a call to a database and build that information into the HTML which is sent to the client. All of the information that I see requires the developer to make RPC calls for every bit of dynamic information, after the HTML has been downloaded. I suspect that the RPC method is the only way, but I just wanted to verify that I wasn't missing something. Thank you. -- 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+unsubscr...@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/groups/opt_out.
Re: RequestFactory - BaseRequest, Locator, ServiceLocator, service inheritance on the client
Try adding @SkipInterfaceValidation to the EntityBaseRequest or make sure
that all the interfaces that extends EntityBaseRequest have the getDataPage
implemented in their implementing class. I noticed a problem that the
implementing class must contain the methods that are provided. I believe
this is a problem with the request factory validation tools. To reiterate
the requestfactory validation tools do not check the parent class for the
method so I either had to add ListEntityBase getDataPage(int offset, int
limit, String orderString){} to the implementing class. I chose to add the
@SkipInterfaceValidation so that I could allow the requestfactory to skip
validating my parent service and would get the error at runtime if it could
not find the method. RequestFactory can find the parent method when it
instantiates the service.
The problem described in the section was a problem with generics. You can
add generics to your EntityBaseRequestT extends EntityBaseProxy if you
wish to make the service more generic. The problem there was that the
client side code was not able to use the base service because it could not
find the client side method. Your issue is similar but different.
Hope this helps,
Chirs
On Sunday, October 6, 2013 11:30:51 AM UTC-5, Manuel wrote:
Hi everyone,
I actually try to do a Celltable-Component, that can work with any
Proxy-class. So the component should work with a template class T.
(Actually it just works with a certain type of Proxy)
Inside the component, i actually got some Requests for the certain Proxy,
like delete(), persist(), findall(). These requests I want to make work
with all kinds of proxies.
Now, instead of writing:
CertainEntityRequest request = Factory.certainEntityRequest ();
RequestListCertainEntityProxy findAll= request.findall(
offset, size, orderByString);
I want to have a BaseRequest, that has these services for all my proxies.
I tried to put all service-methods that I use in my component into one
base-Service, similar to this post
http://stackoverflow.com/questions/7625692/gwt-2-4-0-requestfactory-polymorphism.
persist() and remove() works well. But I dont know how to implement the
findall() / getDataPage() service.
@Entity class EntityBase {
//some methods, persist(), remove() etc
...
public ListEntityBase getDataPage(int offset, int limit,
String orderString) {...}
}@Entity class SomeEntity extends EntityBase {...}
@Entity class SomeOtherEntity extends EntityBase
{...}...@ProxyFor(EntityBase.class) class EntityBaseProxy extends EntityProxy
{...}@ProxyFor(SomeEntity.class) class SomeEntity extends EntityBaseProxy
{...}
@ProxyFor(SomeOtherEntity.class) class SomeEntity extends EntityBaseProxy
{...}
...
@Service(value = EntityBase.class, locator = MyServiceLocator.class)
@ExtraTypes({ SomeEntity.class, SomeOtherEntity.class })
public interface EntityBaseRequest extends RequestContext {
InstanceRequestEntityBaseProxy, Void remove();
InstanceRequestEntityBaseProxy, Long persist();
//This doesnt work. And even if this would work, how to build the query ?
I wouldnt know the specific class, it could be SomeEntity or
SomeOtherEntity
//Thats the error: *Could not find domain method similar to
java.util.List...EntityBaseProxy getDataPage(intintjava.lang.String)*
*RequestListEntityBaseProxy getDataPage(int offset, int limit, String
orderString)*
}
I also found this issue, I guess thats what I try to do:
http://code.google.com/p/google-web-toolkit/issues/detail?id=6234
Anyways, Im not sure if I even chose the right approach. Maybe there is
already an working example for this ? Or a simpler approch?
Regards,
Manuel
--
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+unsubscr...@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/groups/opt_out.
Re: push data from server to clients
I've had most success with http://www.jboss.org/errai On Sunday, 14 July 2013 04:36:14 UTC+10, Gal Lavie wrote: hello I want when first client do action on data base (update ,delete or add) the server updating client b I want that my server can push data to clients how I can do this? I hope you understand me thank you -- 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+unsubscr...@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/groups/opt_out.
Re: No source code is available for type com.google.gwt.autobean.shared.AutoBean
thanks. -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Firing a click event on a CellTable
Hello, I am interested in using GWTTestCase to test some features of a view that extends CellTable. In my implementation, I have added a CellPreviewHandler that I would like to check by firing a click event on a cell of the CellTable. I have tried several methods to no avail. My most recent attempt follows: CellTableArtist cellTable = (CellTableArtist) view.getDataView(); NativeEvent event = Document.get().createClickEvent(0, 0, 0, 20, 30, false, false, false, false); DomEvent.fireNativeEvent(event, cellTable); This does not work. The CellPreviewHandler doesn't get called. This has also been tried: CellTableArtist cellTable = (CellTableArtist) view.getDataView(); NativeEvent event = Document.get().createClickEvent(0, 0, 0, 0, 0, false, false, false, false); TableCellElement element = cellTable.getRowElement(2).getCells().getItem(1); element.dispatchEvent(event); Same problem as the former. *TL;DR* Does anyone have insight as to how I can simulate a click event that will fire a CellPreviewEvent on a CellTable for a desired Cell? -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
New To GWT: Objects in composite object not aligned correctly
I created a composite object for a date range that is supposed to be all
bottom aligned. My text boxes are not aligned with my listbox and it's
driving me crazy. Thanks for the help.
import com.google.gwt.user.client.ui.Composite;
import com.google.gwt.user.client.ui.HasVerticalAlignment;
import com.google.gwt.user.client.ui.HorizontalPanel;
import com.google.gwt.user.client.ui.Label;
import com.google.gwt.user.client.ui.ListBox;
import com.google.gwt.user.client.ui.Panel;
import com.google.gwt.user.client.ui.TextBox;
import com.google.gwt.user.client.ui.VerticalPanel;
public class YearWeekInput extends Composite{
ListBox listBox;
YearWeekPanel fromPanel;
YearWeekPanel toPanel;
public YearWeekInput() {
HorizontalPanel mainPanel = new HorizontalPanel();
mainPanel.setVerticalAlignment(HasVerticalAlignment.ALIGN_BOTTOM);
mainPanel.setSpacing(5);
mainPanel.add(getListBox());
mainPanel.add(getFromPanel());
mainPanel.add(getToPanel());
initWidget(mainPanel);
setStyleName(year-week-input);
}
private ListBox getListBox(){
if(listBox == null){
listBox = new ListBox(false);
listBox.setVisibleItemCount(1);
listBox.addItem( Year/Week Single);
listBox.addItem(Year/Week Range);
}
return listBox;
}
private YearWeekPanel getFromPanel(){
if(fromPanel == null){
fromPanel = new YearWeekPanel(From);
}
return fromPanel;
}
private YearWeekPanel getToPanel(){
if(toPanel == null){
toPanel = new YearWeekPanel(To);
}
return toPanel;
}
private class YearWeekPanel extends Composite {
private TextBox year;
private TextBox week;
public YearWeekPanel(String title) {
VerticalPanel mainPanel = new VerticalPanel();
mainPanel.setVerticalAlignment(HasVerticalAlignment.ALIGN_BOTTOM);
mainPanel.setBorderWidth(0);
mainPanel.add(new Label(title));
mainPanel.add(getTextFields());
initWidget(mainPanel);
setStyleName(title + -year-week-panel);
}
private Panel getTextFields(){
HorizontalPanel hPanel = new HorizontalPanel();
hPanel.setVerticalAlignment(HasVerticalAlignment.ALIGN_BOTTOM);
hPanel.setSpacing(2);
hPanel.add(getYearTextBox());
hPanel.add(getWeekTextBox());
return hPanel;
}
private TextBox getYearTextBox(){
if(year == null){
year = new TextBox();
year.setWidth(4em);
}
return year;
}
private TextBox getWeekTextBox(){
if(week == null){
week = new TextBox();
week.setWidth(2.5em);
}
return week;
}
}
}
--
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+unsubscr...@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: How does GWT work with App Engine backends?
It seems you cannot call a backend directly from GWT because of the same origin policy. My workaround was to call a servlet and have the servlet call the backend. http://googcloudlabs.appspot.com/ has a lot of great examples that helped me figure this out. On Wednesday, 10 April 2013 17:50:56 UTC-3, Chris Malloy wrote: Hi All, I'm trying to find some documentation on how to get GWT working with an App Engine backend. The sample code GWT generates is enough to get servlets up and running, but not much else. The available documentation from Google has helped me to properly configure backends.xml, and I can see the backend instance on my App Engine dashboard. From here on I'm stuck. thanks, Chris -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
How does GWT work with App Engine backends?
Hi All, I'm trying to find some documentation on how to get GWT working with an App Engine backend. The sample code GWT generates is enough to get servlets up and running, but not much else. The available documentation from Google has helped me to properly configure backends.xml, and I can see the backend instance on my App Engine dashboard. From here on I'm stuck. thanks, Chris -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: gwtsizzle - CSS selectors for GWT dom
Not sure which browsers you are targeting or the selectors you require, but querySelector might be an alternative without requiring the extra library. http://caniuse.com/#feat=queryselector On 1 Jan 2013 05:14, Sebastián Gurin sebastigu...@gmail.com wrote: Thank you Thomas for the clarification and for taking a look to the project. Didn't know about the new xsiframe. I'm reading some documentation and fixing my projects. about wrapper/port thing, I thought a wrapper was when you put the JSO as a pure java class attribute. Then you delegate all methods to the JSO. You have a little (x2) overhead because of the second call but you gain in language because you work with pure java so you can do new MyClass() and inheritance. In my case I use JSOs for talking directly to JS objects from java, so I didn't called wrapper but perhaps you are right, i don't know... iIm pretty confused about terminology here you are right it is not a port... I would call it (direct) Java API for sizzlejs . Happy new year and thanks again! On Monday, December 31, 2012 9:58:44 PM UTC-2, Thomas Broyer wrote: On Monday, December 31, 2012 10:55:50 PM UTC+1, Sebastián Gurin wrote: I needed a lightweight solution for CSS selectors in com.google.gwt.dom.client.**Element so I made a GWT port of the JavaScript library *sizzle*js.com/ http://sizzlejs.com/ Ah, this is not a port, it's a wrapper. Also note that the script src= in the gwt.xml won't work with the xsiframe linker (and the xsiframe linker is the future) -- 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/-/RjoowyRiuDEJ. 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. -- 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: DataGrid vs CellTable
The 100% won't help you, because the FlowPanel (which contains your DataGrid as I understand it) has a height of 0 unless you fill it with widgets that mount their own height. In other words, you are creating a cycle: The FlowPanel asks its children for the height they need, and the child (DataGrid) conversely asks the parent FlowPanel for its height. Obviously, this doesn't work, and in CSS, it always ends up with a height of 0 (not a special GWT thing). It's not, that DataGrid and CellTable aren't interchangeable. To the contrary: They are highly interchangeable, but they differ basically in exactly this point: CellTables span up their own height from inside out, whereas DataGrids require the size from outside in. (Note: Almost the only real reason for the requiresResize() is, that DataGrid uses a HeaderPanel, which performs one of the few JavaScript tricks still needed today, because CSS still can't do HeaderPanel-like layouts by itself.) On Monday, December 3, 2012 5:39:55 PM UTC+1, Tony B wrote: Well, that makes sense, I guess. Granted, I don't know what size to expect, thus the percentage :-). I cannot just assume a PC browser, but also need to plan for mobile devices. There is a really good example out there ( herehttp://rvsoni.wordpress.com/2011/10/25/gwt-datagrid-with-pagination-using-simple-pager/). Maybe I should just rework my code to mimic this example more closely. Maybe that will help me wrap my head around things. It looks like my assumption was right: CellTable and DataGrid are not, strictly speaking, interchangeable ( not without extra work ). To bad. Thanks. Tony On Monday, December 3, 2012 2:59:49 AM UTC-5, Thomas Broyer wrote: On Monday, December 3, 2012 12:05:49 AM UTC+1, Tony B wrote: Ooops, missed your second question, about the parent widget. Here is the path: FlowPanel - WidgetList - DataGrid Your comments above about the contraints are what made me ask my question in the first place. I even set the size of the DataGrid to 100% on the hunch that that would meet your rule that it must be explicitly sized. 100% isn't reliable. RequiresRzsize widgets have to be informed when their size change, so you have to give them a size that won't change on your behalf (I think EMs and EXs will be detected –i.e. when the user changes his browser font settings–, though probably not by each and every RequiresResize widget; better stick with pixels). -- 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/-/expzpkx8S0oJ. 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 Maps V3 Api, clearing directions
did you get the issue with $wnd.google is undefined resolved?
On Thursday, September 20, 2012 9:56:28 AM UTC-7, Deepak Singh wrote:
Any guidance pls..
On Thu, Sep 20, 2012 at 1:39 AM, Deepak Singh
deepaks...@gmail.comjavascript:
wrote:
Could not resolve the exception mentioned.
Then i copied PlaceSearchMapWidget.java and tried to use.
But could not create the widget as
PlacesService placeService = PlacesService.newInstance(attrContainer,
mapWidget);
And i could not understand 'attrContainer' parameter.
My requirement is simple,
I have latitude and longitude. I need to search places within 2 kms area
of this latlong.
Pls let me know which kind of class will be useful for me ?
Regards
Deepak
On Thu, Sep 20, 2012 at 1:36 AM, Deepak Singh
deepaks...@gmail.comjavascript:
wrote:
Now, I added gwt-ajaxloader.jar
It was able to run in dev mode.
Now i run the following code
MapOptions mo = MapOptions.newInstance();
LatLng ll = LatLng.newInstance(Double.parseDouble(latitude),
Double.parseDouble(longitude));
mo.setCenter(ll);
mo.setZoom(4);
mo.setMapTypeId(MapTypeId.HYBRID);
MapWidget mw = new MapWidget(mo);
// enquiryDiv.appendChild(mw.getElement());
com.google.gwt.core.client.JavaScriptException: (TypeError)
@com.google.gwt.core.client.impl.Impl::apply(Ljava/lang/Object;Ljava/lang/Object;Ljava/lang/Object;)([JavaScript
object(6222), JavaScript object(6221), JavaScript object(6296)]):
$wnd.google is undefined
On Thu, Sep 20, 2012 at 1:02 AM, Deepak Singh
deepaks...@gmail.comjavascript:
wrote:
I added jar file APIs_Google_map3.8.0beta.jar to my classpath.
Added this to lib also.
Included
inherits name='com.google.gwt.maps.Apis_Google_Maps' / to my *.gwt.xml
When i run the app in local, i get the following exception
Unable to find 'com/google/gwt/ajaxloader/AjaxLoader.gwt.xml' on your
classpath;
Thanks
Deepak
On Wed, Sep 19, 2012 at 11:00 AM, Brandon Donnelson
branfl...@gmail.com javascript: wrote:
Are you looking for the PlaceServiceSearchRequest? If so, I added and
example map in the live demo maps.
https://github.com/branflake2267/GWT-Maps-V3-Api/blob/master/Apis_Maps_Test/src/com/google/gwt/maps/testing/client/maps/PlaceSearchMapWidget.java#L40
Brandon
On Tuesday, September 4, 2012 7:16:38 AM UTC-7, Deepak Singh wrote:
I want to use this library.
I have lattitude and longitude with me and i need to show the
location on the map.
Also, need to find the nearest locations based on lattitue/longitude.
I went through the docs but could not understand the right class to
be used.
Can you give me some sample code ?
Thanks
Deepak
On Fri, Aug 31, 2012 at 6:52 PM, Thai Ha Duong
duong...@gmail.comwrote:
I have the same question please any one can help?
On Friday, 31 August 2012 12:47:02 UTC+1, Jonas wrote:
I'm using the GWT Maps V3 Api from https://github.com/**branflake22
**67/GWT-Maps-V3-Apihttps://github.com/branflake2267/GWT-Maps-V3-Api
After finding directions on the map, I'm trying to clear the
previous ones before finding new.
In DirectionsRenderer:
/**
* This method specifies the map on which directions will be
rendered. Pass null to remove the directions from the map.
* @param mapWidget
*/
public final void setMap(MapWidget mapWidget) {
setMapImpl(mapWidget.getJso());
}
private final native void setMapImpl(MapImpl map) /*-{
this.setMap(map);
}-*/;
I'm trying to pass:
directionsDisplay.setMap(null);
which results in NPE:
Caused by: java.lang.**NullPointerException**: null
at com.google.gwt.maps.client.**ser**vices.DirectionsRenderer$.
**setM**ap$(DirectionsRenderer.**java:**50)
Anyone used this API and knows how to clear directions from the map
widget?
--
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/-/**
emLbrk1GnloJhttps://groups.google.com/d/msg/google-web-toolkit/-/emLbrk1GnloJ
.
To post to this group, send email to google-we...@**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=enhttp://groups.google.com/group/google-web-toolkit?hl=en
**.
--
Deepak Singh
--
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/-/r8sXg55osSoJ.
To post to this group, send email to
google-we...@googlegroups.comjavascript:
.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com javascript:.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: SuperDevMode not so super
In my opinion, Super Dev Mode is an awesome addition to Dev Mode. It fits in my workflow: - For super-fast changes in client-side code (to fine-tune styling etc.), I use Dev Mode, with a Debugger attached, and a simple button on the page that rebuilds just the widget I am tuning. Nothing beats that in speed (1 sec reload). - When trying the real app without the intention to make client-side changes, I use Production Mode. - When I plan to make some bigger code changes e.g. to a Dialog (structural changes which a Java Debugger couldn't handle anyway), I use SuperDevMode, displaying only the Dialog. This gives me a quick UI and very high realism. The only problem I see is, that Super Dev Mode has been officially described as a replacement for Dev Mode. I don't know, if that's such a good idea. I agree with Andrew Mackenzie, that it would be basically good enough to have one browser (per OS) available for DevMode (reminds me of the old Hosted Mode). Hosted Mode for one browser + Super Dev Mode for all browsers would give me most of what I need. I imagine, that it would also allow Hosted Mode to be more optimized than the current Dev Mode (somehow I always had the feeling, that the old Hosted Mode reacted quicker than Dev Mode, but I could be wrong). I understand, that keeping the browser plugins up to date is not an easy task. And the current Dev Mode plugin situation is not good: - The Firefox Plugin *seriously* leaks memory (http://code.google.com/p/google-web-toolkit/issues/detail?id=7648), - Chrome plugin doesn't always work with latest Chrome (which is ok on Mac thanks to Chromatic, but it's hard to get old versions of Chromium on Linux) So currently, it's impossible to recommend *any* browser to use with DevMode on Linux (and also somewhat difficult for Windows). Which is a situation that should be resolved soon (maybe by fixing the Firefox plugin leak). I think, it should take priority over Super Dev Mode - because even if it maybe actually replaces Dev Mode someday, there's still a long way until it's fully there. -- 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/-/FJBhWhbDgUYJ. 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: SuperDevMode not so super
On Thursday, November 15, 2012 2:53:37 AM UTC+1, Thomas Broyer wrote: SourceMaps could then be used by your IDE so you could put breakpoints in your editor window. I can see the potential - it could be big. I do have a few doubts though: 1. Would this also allow me to inspect the internal state of objects from within my IDE? (Is this even possible?) 2. What about super-sourced classes, which are - at least in Eclipse - usually excluded from the build path to avoid error messages (that's probably the smaller problem, as I imagine, that this could be taken care of by the IDE plugins) Embedded browsers, even if using the exact same engine, don't behave like their full blown counterparts (IE, when embedded, has different rules for switching between IE5.5Quirks/IE7/IE8/etc. modes for instance) I think, living with these differences in Dev Mode would be ok. The situation was different back in Hosted Mode's time, because Super Dev Mode was missing. I believe, that Dev Mode currently has some important use cases, which Super Dev Mode can't cover (yet?) For these use cases, the browser differences are often not that important. -- 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/-/65KGTSLnUJ0J. 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 2.5 RC2 EntityProxy Validation
On Tuesday, November 6, 2012 10:13:59 AM UTC+1, Thomas Broyer wrote:
Couldn't you simply override the methods and refine the return type? (Java
has covariant return types)
interface Employee {
Employee getBoss();
}
interface EmployeeProxy extends Employee, EntityProxy {
EmployeeProxy getBoss();
}
class EmployeeEntity implements Employee {
@Override
public EmployeeEntity getBoss() { … }
}
It gets more difficult for setters though:
interface Employee {
...
void setBoss(Boss boss);
}
can't be implemented in Java by
class EmployeeEntity implements Employee {
@Override
public void setBoss(BossEntity boss) { … }
}
So you could use generics
interface EmployeeB extends Boss {
...
void setBoss(B boss);
}
class EmployeeEntity implements EmployeeBossEntity {
@Override
public void setBoss(BossEntity boss) { … }
}
However, once I tried this (with GWT 2.5.0), it led to an Exception (only
when I define setters) - sorry, I don't exactly remember which Exception it
was, and I'm a little bit short of time at the moment to pursue it further.
(Maybe related to
http://code.google.com/p/google-web-toolkit/issues/detail?id=5762 ?)
--
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/-/RbSPxfagQzUJ.
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.
RequestFactory and (JPA) transaction concepts
I'd like to discuss how to best use (JPA) transactions with RequestFactory.
As a basis, I'm assuming the approach where one user interaction should
normally result in one DB transaction, so that the whole interaction can
either fail or succeed, atomically.
The first thing to consider with RequestFactory is, that each method call
in a RequestContext can succeed or fail individually. Also note, that the
fire() call will (usually) succeed as a whole, even if one of the
RequestContext method calls fails.
So for example, if you have
ctx.opA().to(receiverA);
ctx.opB().to(receiverB);
ctx.fire(receiverX);
Then this may result in the sequence
receiverA.onSuccess(),
receiverB.onFailure(),
receiverX.onSuccess().
What this means is, that you get atomicity only for the individual
RequestContext methods. Therefore you definitely shouldn't wrap the entire
RequestFactoryServlet's onPost() method in one transaction, but rather only
the individual service method implementations individually. (Otherwise, the
client may believe, that opA has succeeded, while in reality the entire
transaction was rolled back.)
And if you need a transaction with multiple objects involved, you will have
to wrap the entire interaction in one service method call.
*Side note: Convenience solution*
*
*
If you grow tired of wrapping each service method implementation in a
transaction individually, you may want to use your own
ServiceLayerDecorator in the RequestFactoryServlet constructor, and
override invoke() like this:
@Override
public Object invoke(final Method domainMethod, final Object... args) {
// Note: Ideally use dependency injecton for this:
final EntityManager em = getRequestScopedEntityManager();
try {
em.getTransaction().begin();
final Object result = super.invoke(domainMethod, args);
em.getTransaction().commit();
return result;
} catch (final Error e) {
em.getTransaction().rollback();
throw e;
} catch (final RuntimeException e) {
em.getTransaction().rollback();
throw e;
}
}
(Better solutions are welcome!)
*Question/Discussion:*
There is however a little issue that remains: RequestFactory calls
Locator.find() outside of such a transaction:
1. In RequestState.getBeansForPayload(), which calls
ServiceLayerDecorator.loadDomainObjects()
2. In SimpleRequestProcessor.createReturnOperations, which calls
ServiceLayerDecorator.isLive()
I think, it's possible to pretty much ignore this (at least if you don't
use isolation levels higher than READ_COMMITTED, and if your DB is ok with
autocommit style queries), or is it? Note: My Locator's find method re-uses
the same RequestScoped EntityManager instance - so I get the same
underlying Hibernate session with the same first-level cache - it's just
not in the same transaction, that's all.
How do you deal with this? What is the intended transaction concept by the
RequestFactory designers?
--
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/-/ASBa77ljy3cJ.
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: RequestFactory and (JPA) transaction concepts
On Thursday, November 1, 2012 6:36:54 PM UTC+1, Thomas Broyer wrote:
Guice Persist's @Transactional works great (of course with a
ServiceLayerDecorator to instantiate your services through Guice):
http://code.google.com/p/google-guice/wiki/Transactions
That's the missing guice-extension what I was looking for, thanks! (I'm
already using Guice to inject a RequestScoped ProviderEntityManager into
ServiceLayerDecorator, Locator and ServiceLocator, and Guice Persist could
help me to cut down some more boilerplate.)
I believe you MUST use a @RequestScoped EntityManager (again, Guice
Persist FTW), to make sure you always have a single instance of a given
(logical) entity. See
http://code.google.com/p/google-web-toolkit/issues/detail?id=7341
Absolutely. (It's what I would expect anyway.)
And there are a few consequences that need consideration:
1.)
Since it's one and the same EntityManager, a call to persist() is actually
only required for new entities. For existing entities, it can be enough to
call
CatProxy editableProxy = ctx.edit(cat);
editableCat.setName(newName);
ctx.somethingThatSucceeds();
ctx.fire();
Where the implementation of somethingThatSucceeds() can be empty! It's
strange, that this call is necessary at all, but without it,
SimpleRequestProcessor.processOperationMessages() determines, that operations
== null, and returns immediately.
2.)
But there's also a danger involved in not calling persist(): With the
following sequence of calls:
CatProxy editableProxy = ctx.edit(cat);
editableCat.setName(newName);
ctx.somethingThatFails();
ctx.somethingThatSucceeds();
ctx.fire();
the entity will not be updated. This happens, because a rollback occurs in
the first transaction, which detaches the object from the EntityManager. If
we want it to be re-attached after that, we need to call merge().
So what I currently do, is to always call persist(), and to implement
persist() like
public void persist(final Cat cat) {
if (cat.getId() == null)
em.persist(cat);
else {
if (!em.contains(cat))
em.merge(cat);
}
}
But this doesn't look perfectly good to me yet. How do you use and
implement persist()?
--
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/-/hev_LM2qtO8J.
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 2.5 Java 5 runtime(!) compatibility
On Tuesday, October 30, 2012 5:42:11 PM UTC+1, Lars Ködderitzsch wrote: Bummer, at least this finally confirms that anyone doomed to still use Java 5 based servers will be unable to user anything newer than GWT 2.4 from this point on. What I find interesting is, that companies who are afraid to update an extremely old closed source server, would be willing to update to the cutting edge version of an open source web framework, which has been released just a few days ago? -- 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/-/H8Gheg_vC3wJ. 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.
[gwt-contrib] Re: Thanks minichate! (issue1863803)
Note that more advanced media queries are still borked:
@media all and (max-width: 699px) and (min-width: 520px), (min-width:
1151px) {
// ...
}
The above gets truncated to:
@media all {
}
I haven't tracked down where the truncation is occurring -- a project
for tonight, most likely!
http://gwt-code-reviews.appspot.com/1863803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: Could not load GWT DMP Plugin
After updating the GWT Dev Plugin to version 1.0.11349 it seems to work again on my system (Win 7/64, Chrome 22, GWT Dev Plugin 1.0.11349, Juno, m2e ) Thanks for fixing it On Wednesday, October 24, 2012 8:46:22 AM UTC+2, Juanra Collado wrote: It's working for me the new version in: Chrome - Versión 22.0.1229.94 m Windows XP SP3 Thanks for your work. El miércoles, 24 de octubre de 2012 02:52:41 UTC+2, Markus Grill escribió: the new version works... Thank you Markus Am Mittwoch, 24. Oktober 2012 01:53:48 UTC+2 schrieb Brian Slesinsky: A new version is now live in the Chrome store. The only difference is that the Windows version is statically linked. I don't have a sufficient number of Windows machines available for testing, so I don't know how much this will help. However, it shouldn't make things worse. https://chrome.google.com/webstore/detail/gwt-developer-plugin/jpjpnpmbddbjkfaccnmhnkdgjideieim - Brian On Tuesday, October 23, 2012 10:35:33 AM UTC-7, Brian Slesinsky wrote: It looks like I linked the DLL wrong on Windows, so it requires some additional DLL's that not everyone has. We'll have a new release later today. -- 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/-/efXKgsbLv4EJ. 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: Could not load GWT DMP Plugin
This workaround is also not working for me. I don't even see the toolkit icon in the statusbar. I'm using m2eclipse and everything worked fine out of the box until last week. Setup: Juno, m2eclipse, Chrome 24 dev (but also tried 22), Windows 7 On Tuesday, October 23, 2012 1:57:23 AM UTC+2, Markus Grill wrote: Hello Brian, I've also the problem that the GWT DMP Plugin could not be loaded anymore until now I've never had an entry in my preferences for the hostnames because I always used localhost as code- and webserver. (by the way... adding localhost to the list does not work either...) Setup: Windows7; Chrome 22.0.1229.94 m; GWT-Plugin 1.0.11338 Markus Am Montag, 22. Oktober 2012 20:09:54 UTC+2 schrieb Brian Slesinsky: Yes, we released a new version of the plugin on Friday. For some reason, upgrading to the new plugin loses your preferences for the hostnames that Dev Mode is allowed to connect to. So you'll have to add them again. Sorry about that! If it's not connecting and the toolkit icon on the right side of URL bar is gray instead of red, click on the gray icon to pop up the dialog to add the hostname. An alternate way to get to the same options page: 1. visit chrome://chrome/extensions/ 2. Find the entry for GWT Developer Plugin 3. Click on Options. - Brian On Monday, October 22, 2012 5:49:24 AM UTC-7, Drew Spencer wrote: Same here. Glad I'm not the only one. I'm on Windows as well, using v22 of Chrome. Bah! On Saturday, 20 October 2012 21:08:44 UTC+1, seas wrote: Started getting 'Could not load GWT DMP Plugin' yesterday when I start my app from Eclipse using Chrome. Happening on both work and home computers. From web searches, it looks like this has happened in the past, which seemed to indicate that in those cases a new plugin was deployed that had issues. In those cases there was no clear fix except some people has success rolling back to an earlier version of the plugin. I've tried reinstalling the latest plugin. Didn't see any option for downloading previous versions from the app store. Tried restarting Chrome, Eclipse, and rebooting the machine. Has there been a recent update to the plugin? Where can I get the previous one to roll back to? Is there another update coming soon that will fix this? My home set up is: Windows XP SP 3 Eclipse Helios Service Release 2 build ID 20110218-0911 Chrome 22.0.1229.94 m GWT Developer Plugin 1.0.11338 My work set up is similar but with Window 7 -- 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/-/EbPpNSZJUs0J. 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: Could not load GWT DMP Plugin
Same here. Really annoying.. On Monday, October 22, 2012 2:00:15 AM UTC+2, seas wrote: Tony, thanks for the reply. I didn't have much luck using different ip addresses though. Initially, the url generated for launching in dev mode was 127.0.0.1. I tried changing it in the Chrome address bar to local host and the machine's URL. I also added the -bindAddress 0.0.0.0 to the eclipse configuration. That changed the url generated for launching dev mode to my machine's url, but still no luck. I'll keep playing with it. On Sunday, October 21, 2012 7:38:09 AM UTC-7, Tony Rah wrote: There seems to be yet another problem with the latest Chrome plugin where it won't load in dev mode when the codesvr argument is pointing to your local ip address. Try switching the ip adress portion of the argument to either 127.0.0.1 or localhost in your browser. You might also have to add -bindAddress 0.0.0.0 to you eclipse launch config. This worked for me but I didn't dig any deeper to understand the problem more thoroughly. I also don't know how this will effect remote debugging. Perhaps someone else has better info. On a side note, this latest plugin fixes the Chrome22/OSX issue that was plaguing everyone for the last several weeks. Unfortunately, it now introduces this new issue. x On Saturday, October 20, 2012 2:08:44 PM UTC-6, seas wrote: Started getting 'Could not load GWT DMP Plugin' yesterday when I start my app from Eclipse using Chrome. Happening on both work and home computers. From web searches, it looks like this has happened in the past, which seemed to indicate that in those cases a new plugin was deployed that had issues. In those cases there was no clear fix except some people has success rolling back to an earlier version of the plugin. I've tried reinstalling the latest plugin. Didn't see any option for downloading previous versions from the app store. Tried restarting Chrome, Eclipse, and rebooting the machine. Has there been a recent update to the plugin? Where can I get the previous one to roll back to? Is there another update coming soon that will fix this? My home set up is: Windows XP SP 3 Eclipse Helios Service Release 2 build ID 20110218-0911 Chrome 22.0.1229.94 m GWT Developer Plugin 1.0.11338 My work set up is similar but with Window 7 -- 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/-/azLFhPxf3D0J. 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.
[gwt-contrib] Subversion tag for 2.5.0-rc2?
I'd like to check out the code for 2.5.0-rc2. For previous versions I can find a tag, e.g. http://google-web-toolkit.googlecode.com/svn/tags/2.5.0-rc1;, with the svn log entry r11147 | rda...@google.com | 2012-06-27 06:55:21 +0200 (Wed, 27 Jun 2012) | 5 lines Changed paths: A /tags/2.5.0-rc1 (from /releases/2.5:11145) Tagging the 2.5.0.rc1 release. Was built at r11145. svn copy https://google-web-toolkit.googlecode.com/svn/releases/2.5@11145 https://google-web-toolkit.googlecode.com/svn/tags/2.5.0-rc1 Is this tag intenionally missing for rc2, or will this be created later (because the contents of an svn tag directory should never change)? -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: Googlebot dissing my GWT app
A Google search for site:www.spot...com [replace the ellipsis] just returns www.spot...com. But you don't have that page in your sitemap, and you're not using step 3 Handle pages without hash fragments of the Step-by-step guide: In order to make pages without hash fragments crawlable, you include a special meta tag in the head of the HTML of your page. The meta tag takes the following form: meta name=fragment content=! Your main page is a dynamic JS-page. Googlebot can't see your links (like #driver_reports), as they don't appear in the static content of your main page (it doesn't know about www.spot...com/#!home yet, only about www.spot...com. Sitemaps just complement a discovery crawl (so that's probably not enough). Only with the meta tag, googlebot will go to www.spot...com?_escaped_fragment_= On Wednesday, October 10, 2012 8:02:05 PM UTC+2, rhodebump wrote: Hi, I have been trying for weeks, but can't get google to update it's index for my GWT application. -- 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/-/eTKfNxLrbtQJ. 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: Saving results from GWT-RPC call on client
One alternative for serialization would be to work with AutoBeans. - Advantage: They can be decoded from/encoded to Strings via AutoBeanCodexhttp://code.google.com/p/google-web-toolkit/wiki/AutoBean#AutoBeanCodex . - Disadvantage: AutoBeans (or the interfaces they represent) can't be used as parameter types for GWT-RPC, so you'd have to convert them to Strings here, too. So effectively you lose type safety. On the upside, AutoBeanCodex can also be used on the server side, so it's easy to en-/decode between AutoBeans and Strings on both sides, and using the same methods for your cache. On Wednesday, October 10, 2012 7:13:20 AM UTC+2, JeanV wrote: I was wondering if there's anyway to save the returned results from an RPC call to an HTML5 enabled browser. Basically the only way I have found would be to convert the results into strings and use LocalStorage to save them to the browser. I guess my question then would be how can IsSerializable java objects be converted to a string and back. Any help would be appreciated. Jean -- 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/-/AE2R-ThQtsQJ. 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: Are you happy with GWT?
That's a very interesting situation. Actually, this is a decision between full-ajax site and js-enhanced site, and for that question it doesn't even really matter which JS framework is used. Server-side templating has always been a somewhat crazy idea (a hack, if you want - but then again, AJAX is a hack, too). It's surprising, that GWT can handle even this scenario well, and although it can't show its full set of advantages then, it's still a great choice. It's possible with GWT to eliminate server-side templating, if you want, because GWT makes it so easy to move the UI logic to the client. There are simply things that should live on the server side and things that should live on the client side. With traditional web development techniques, this decision was biased - now you can make a balanced decision. On Tuesday, October 9, 2012 2:10:16 PM UTC+2, David wrote: Some examples of pushback when trying to introduce GWT into a legacy j2ee application -- 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/-/Jz9n8x8JjQwJ. 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: Are you happy with GWT?
On Tuesday, October 9, 2012 4:38:47 PM UTC+2, David wrote: When servlet engines first came on the scene , developers were writing stringified content directly to the HttpResponse. Absolutely, from that point of view (and I remember cgi scripts), template engines are a big enhancement to what existed before! But imagine telling developers from a different field, who have never looked into web development before, that there's - one approach that is based on sending the complete same htmlhead.../headbodydiv.../div/body over and over again, after using a template to replace just a small part of it. - and there's a second approach that just gets the necessary data from the server, and then updates the view (making use of the specific client's features) Which one would they choose? I believe it might be a hard time arguing in favor of the first approach. Eliminating them completely has always been a tough sell. The only significant technical argument against full-ajax is probably the SEO argument. Then again, it's not hard to make it work with Google Searchhttps://developers.google.com/webmasters/ajax-crawling/docs/getting-started. And other search engines, while maybe not treating it perfectly yet, will eventually have to improve their strategy, too. (Note: In Germany, this is not much of an issue, as Google Search has a market share of 95%http://www.chip.de/news/Suchmaschinen-Statistik-Google-als-Alleinherrscher_54987735.html here) Eliminating them completely has always been a tough sell. Luckily GWT does not require this . I agree. The decision is separate from GWT/other JS framework. And GWT doesn't restrict what you can do in web development. -- 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/-/MAdGydemJkcJ. 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: Possible RFE: Make UiBinder aware of IsWidget interfaces
On Friday, July 20, 2012 6:42:02 PM UTC+2, Jens wrote: Actually UiBinder special treats addStyleNames for normal widgets (it works with my:MyViewImpl addStyleNames=...) but it stops doing so when it sees something that does not extend Widget I guess. FYI, this is true, the special code is in com.google.gwt.uibinder.elementparsers.UIObjectParser which is registered in com.google.gwt.uibinder.rebind.UiBinderWriter.registerParsers() That method already contains a code comment: // TODO(rjrjr): Allow third-party parsers to register themselves // automagically Then again, if such a parser were registered, it probably shouldn't be registered for IsWidget, but instead for a new Interface that contains the addStyleName method. -- 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/-/KD9538Bd7TwJ. 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: Is GWT market is down?
what state/city are you looking for work in? Texas? New South Wales? Rajasthan? On Monday, 8 October 2012 22:49:14 UTC+11, Mayank pandya wrote: Hi, I am a GWT freelance developer form last 2 years but now a days I has no job form last 2 months in GWT? I am so depressed that there is no any new bid for GWT developer in freelance market. and planned to change my field. So what would you suggest me to either wait for new jobs or jump to another new technologies? Also looking for any job If anyone suggest. -- 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/-/44y7lFYm2pcJ. 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: mp3 resources - can they be played from within GWT?
Yes, GWT includes an Audio class: http://google-web-toolkit.googlecode.com/svn/javadoc/2.5/com/google/gwt/media/client/Audio.html However, not all browsers support all formats, e.g. Firefox doesn't support mp3: http://en.wikipedia.org/wiki/HTML5_Audio So you may have to serve the file in multiple formats. More background on HTML5 audio: http://html5doctor.com/html5-audio-the-state-of-play/ On Sunday, October 7, 2012 2:59:00 AM UTC+2, jones34 wrote: Is there any way (a widget, maybe) I can play an MP3 that I have as gwt resource, without leaving gwt or sending the user to a new browser tab? An MP3 player widget, maybe? thanks -- 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/-/qwIUytVQR6QJ. 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: compiled file ending with *.htm instead of *.html
On Thursday, October 4, 2012 8:32:13 PM UTC+2, James wrote: I extended IFrameLinker to return .cache.htm in getCompilationExtension. GWT compiler generates all js files ending with cache.htm as expected. But nocache.js still has cache.html in one place such as $intern_62 = '.cache.html'. It work fine after I change cache.html to cache.htm in nocache.js file. I can not find any files containing cache.html in gwt-user.jar and gwt-dev.jar. Any help will be appreciated. It's probably in /com/google/gwt/core/linker/IFrameTemplate.js This file is used as a template to create the nocache.js. You can specify a different template by overriding getSelectionScriptTemplate(TreeLogger logger, LinkerContext context) That would however require you to copy and paste that template file (each time you upgrade to a new version of GWT). So maybe it's a better idea to override SelectionScriptLinker.generateSelectionScript(TreeLogger logger, LinkerContext context, ArtifactSet artifacts, CompilationResult result) instead, and replace .cache.html with .cache.htm in the resulting string - a little bit hacky, but the chances that it will break are small. -- 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/-/A94eB-4TFcsJ. 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 dev plugin for Chrome 21.0.1180.60 m not installing
what exactly does drag the file onto the extensions page mean? i'm using gPrecise. if i click on the home folder and position its window next to the chrome window and attempt to drag the .crx icon from the home folder to the chrome/extensions page, it just slips off and acts like it has no idea what operation i'm trying to communicate. is there maybe some way of typing a filename instead of fancy drag and drop? - chris -- 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/-/-ySa-tUqxicJ. 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 dev plugin for Chrome 21.0.1180.60 m not installing
that is bizarre. it did not work last night even with many attempts, but the exact same operation this morning worked! i didn't even restart chrome or anything. btw i'm using chrome Version 22.0.1229.64 beta. - chris -- 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/-/6tMsXBplx9YJ. 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: Scary: GWT Team does not fix serious GWT Compiler Bugs
Sorry, but definitely no. Admittedly, I've never actually encountered such a GWT bug in my own code. But that's irrelevant. Imagine you're changing a method temporarily to debug some code (in a way, that it always returns true), and in compiled mode it will simply not do what you expect - you'll search thousands of places before thinking that it could be a compiler bug. 1. Such bugs are avoidable. 2. It's a compiler's job to make sure you can rely on the basics - everything builds upon that, and errors at that level may amplify, leading to completely unpredictable results. This has nothing to do with good coding on the GWT developer's side (BTW, unit tests are often examples of intentional bad coding. What if they fail - or worse: pass - unpredictably?) On Tuesday, October 2, 2012 7:21:47 PM UTC+2, jchimene wrote: +1 on Manolo's point. -- 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/-/GkEDfwGo3PcJ. 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.
[gwt-contrib] RemoteServiceServlet + Transactions
In my opinion, it's currently unnecessarily difficult to integrate basic
transaction management with GWT-RPC.
Usually, in a web application it's best to start a transaction, when a call
arrives at the server, and to commit it, when the server has finished
processing and created the response. For GWT-RPC, this would mean to wrap
all service methods with transaction handling code.
Of course, it's possible to write each method like
public String greetServer(final String input) throws
IllegalArgumentException
{
beginTx();
try {
String result = doGreetServer(input);
commit();
} catch (Throwable t) {
rollback();
throw t;
}
}
But you definitely want to eliminate that boilerplate. So you can override
RemoteServiceServlet's processCall() method. But look at the code:
public String processCall(String payload) throws SerializationException {
// First, check for possible XSRF situation
checkPermutationStrongName();
try {
RPCRequest rpcRequest = RPC.decodeRequest(payload,
delegate.getClass(), this);
onAfterRequestDeserialized(rpcRequest);
return RPC.invokeAndEncodeResponse(delegate, rpcRequest.getMethod(),
rpcRequest.getParameters(), rpcRequest.getSerializationPolicy(),
rpcRequest.getFlags());
} catch (IncompatibleRemoteServiceException ex) {
log(
An IncompatibleRemoteServiceException was thrown while
processing this call.,
ex);
return RPC.encodeResponseForFailure(null, ex);
} catch (RpcTokenException tokenException) {
log(An RpcTokenException was thrown while processing this call.,
tokenException);
return RPC.encodeResponseForFailure(null, tokenException);
}
}
The straightforward way would be to override it like
public String processCall(String payload) throws SerializationException {
beginTx();
try {
super.processCall(payload);
commit();
} catch (Throwable t) {
rollback();
/* Optionally perform additional logging etc. here */
throw t;
}
}
But that doesn't work reliably, because IncompatibleRemoteServiceException
and RpcTokenException will escape, i.e. they won't reach the rollback().
From the Javadoc of java.sql.Connection.close():
It is bstrongly recommended/b that an application explicitly commits or
rolls back an active transaction prior to calling the codeclose/code
method. If the codeclose/code method is called and there is an active
transaction, the results are implementation-defined.
So all that can be currently done is copying and pasting the entire
processCall() method to a subclass, replacing delegate (unfortunately
private) with this (a hack!), and adding the transaction handling code
there. Other options are of course using a dispatch approach like
gwt-dispatch http://code.google.com/p/gwt-dispatch/, or maybe AOP - but
this is not always desirable.
What I would recommend is simply changing processCall() to:
public String processCall(final String payload) throws
SerializationException {
// First, check for possible XSRF situation
checkPermutationStrongName();
try {
final RPCRequest rpcRequest = RPC.decodeRequest(payload,
delegate.getClass(), this);
return doProcessCall(rpcRequest);
} catch (final IncompatibleRemoteServiceException ex) {
log(
An IncompatibleRemoteServiceException was thrown while
processing this call.,
ex);
onAfterRequestDeserialized(rpcRequest);
return RPC.encodeResponseForFailure(null, ex);
} catch (final RpcTokenException tokenException) {
log(An RpcTokenException was thrown while processing this call.,
tokenException);
return RPC.encodeResponseForFailure(null, tokenException);
}
}
protected String doProcessCall(final RPCRequest rpcRequest) throws
SerializationException {
return RPC.invokeAndEncodeResponse(delegate, rpcRequest.getMethod(),
rpcRequest.getParameters(), rpcRequest.getSerializationPolicy(),
rpcRequest.getFlags());
}
Then, it's easy for everyone to override doProcessCall like:
public String doProcessCall(RPCRequest rpcRequest) throws
SerializationException {
beginTx();
try {
super.doProcessCall(rpcRequest);
commit();
} catch (Throwable t) {
rollback();
/* Optionally perform additional logging etc. here */
throw t;
}
}
This would be a very simple change, and it would allow to do all kinds of
things at the beginning and end of each service method, as well as
handling/logging top level Exceptions in a central place.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Documentation of GWT logging (compile out of log levels)
The documentation mentions, that it's possible to make all logging code compile outhttps://developers.google.com/web-toolkit/doc/latest/DevGuideLogging#Making_All_Logging_Code_Compile_Out, but it doesn't mention how to compile out only certain levels. This is however possible: The property gwt.logging.enabled can take the values FALSE, TRUE, SEVERE and WARNING (note: this is separate from the property gwt.logging.logLevel, which can take ALL, FINEST, FINER, FINE, CONFIG, INFO, WARNING and SEVERE) When gwt.logging.enabled is set to SEVERE or WARNING, then the finer levels will not be compiled into the permutation. It would be nice if this information were integrated into the documentation. Also, I think it would be a good idea to add at least INFO to the allowed values of gwt.logging.enabled. -- 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/-/joE7tiqkreIJ. 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: Need a tool to find out client side coverage .
Thanks for the link, Joseph - it's an old version of eclemma, but it works: It shows client side coverage when running in dev mode (not in production mode). Then again, I'm not sure what the patch does exactly. I installed the unpatched v1.3.2 and v1.5.3 from http://sourceforge.net/projects/eclemma/files/01_EclEmma_Releases/, and they both seem to work without patching: At least they show client side coverage (but I only tested it with a small example, so maybe I'm missing something?) v2.1 doesn't show client side coverage, even if patched. On Tuesday, September 25, 2012 8:03:40 PM UTC+2, Joseph Lust wrote: There is now a newer patched version for download. http://code.google.com/p/santa-exchange/downloads/detail?name=eclemma-1.3.2-gwt.zipcan=2q= Followed the instructions and it worked well for me. Would still be nice to have it work out of the box, but I don't expect the Emma team to drop everything for GWT. Ideally someone would submit the patch on the Emma and get it in the trunk. Sincerely, Joseph -- 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/-/Y7wmN2h99KkJ. 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: [Activities Places] How to save and display the criterias again when hitting the back button ?
On Tuesday, September 25, 2012 5:00:28 PM UTC+2, Celinio Fernandes wrote: How can i save them ? If you always only need the previously selected criteria, you don't have to store them in the token: - Either save the values somewhere in your Java objects (wherever you want). When re-creating the search view, initialize it with the saved values. - Or re-use the same view. - Depending on your application, maybe also re-use the same presenter, but it's debatable if this is a good idea or not. If you don't re-use it, you might also have to initialize the presenter's state. All of this however forgets the criteria, if the user leaves the GWT application, and returns to it via the back button. If you want to keep them across application restarts, you can use HTML5 Storagehttps://developers.google.com/web-toolkit/doc/latest/DevGuideHtml5Storage (consider browser support). I know it has something to do with places and tokens and the history class but i have not found a clear example yet. This is only really necessary, if you want to allow users to go back through multiple sets of criteria in the history. But consider this: The search view is presented before the user enters the criteria - therefore the current token can't contain the criteria. If you really want to have the criteria in the token, you would have to go to the search place again when hitting the submit button, adding the criteria to the search token, and then automatically go to the results place. (But this would happen only once after the submit button is pressed, not when returning via the back button.) The easiest solution would be to combine the search criteria view and the results view into one (like Google search does). -- 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/-/tf7I8zx3T8sJ. 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: [Activities Places] How to save and display the criterias again when hitting the back button ?
On Wednesday, September 26, 2012 1:55:53 PM UTC+2, Chris Lercher wrote: you can use HTML5 Storagehttps://developers.google.com/web-toolkit/doc/latest/DevGuideHtml5Storage (consider browser support). Forgot to mention: You could also save them in a cookie. -- 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/-/-guCfovkDPgJ. 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: Super Dev mode : speed, find source in Chrome, stacktrace of exception
On Tuesday, September 25, 2012 7:59:16 AM UTC+2, maticpetek wrote: 2) When we get exception in client code, Dev mode will print out full stacktrace. Is something like this available in SuperDev mode? For example, the following code : String bla = null; bla.length(); // Exception will print Uncaught TypeError: Cannot read property 'length' of null in Chrome Console windows, you can get source of compile JS code, but matching this with Java code is practical imposible. I'm using remote logging and emulated stack traces (which can print beautiful emulated Java stack traces, containing Java method names and line numbers, even for compiled and obfuscated JavaScript) as explained in http://code.google.com/p/google-web-toolkit/wiki/WebModeExceptions But what's missing for super dev mode is the possibility to specify the -extra argument, which can be specified for the GWT compiler (which is needed to update the symbol maps). Super dev mode's CodeServer currently just says Unknown argument: -extra. So in super dev mode, this currently leads to output like: java.lang.Throwable: Some at Unknown.$collect(Unknown Source) at Unknown.fillInStackTrace_1(Unknown Source) at Unknown.fillInStackTrace(Unknown Source) at Unknown.$fillInStackTrace(Unknown Source) -- 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/-/XGKE1rhZ8M4J. 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: Super Dev Mode general question
I want to add to that list, that running Dev Mode with a debugger can be used to fine-tune user interfaces extremely quickly: What I usually do is to put the unit which I need to optimize in a panel, and add a button that refreshes the panel with a new instance of the unit. This doesn't even take a tenth of a second, and it's possible to optimize and fine-tune in quick repetition. Plain JavaScript developer often insist on the importance of seeing the effect of changes absolutely immediately. And I agree with that: If you want to make a UI perfect to the detail, you often end up doing hundreds of iterations. The quicker the iterations, the more willing you are to improve even the last tiny detail. In addition to that, I agree with Alex, that having the debugger features of your IDE (the same IDE you use for developing the application) is indispensable. - For me, it's absolutely ok if Dev Mode doesn't always support the latest version of each browser (as long as the browser allows to have multiple versions installed at the same time). Even dropping support for most browsers would be acceptable. - It's awesome to have Super Dev Mode in addition to standard Dev Mode - I already love it although I haven't used it very much yet. But it should not replace standard dev mode. -- 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/-/irwmlBwB_bgJ. 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: What happened to composite images for ClientBundles?
On Thursday, September 20, 2012 3:54:41 AM UTC+2, Tim wrote:
Perhaps you want set some ImageOptions on the resource. Check
preventInlining and RepeatStyle
Thanks, according to the javadoc, ImageOptions.preventInlining actually
seems to disable all kinds of optimizations:
Set to {@code true} to require the ImageResource to be downloaded as a
separate resource at runtime. Specifically, this will disable the use of
{@code data:} URLs *or other bundling optimizations* for the image.
I assume, this also includes spriting (?). A quick look at
com.google.gwt.resources.rg.ImageResourceGenerator seems to confirm this
for the current implementation.
It's a bit counter-intuitive, because the option is just called
preventInlining, so to be on the safe side, I'll probably use a
DataResource instead (I might miss ImageResource's getWidth()/getHeight()
methods though).
And about RepeatStyle.Both: Here, the javadoc says:
The image is intended to be tiled both horizontally and vertically. Note
that this will prevent compositing of the particular image *in most cases*
.
--
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/-/lCqKpfXTALYJ.
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.
What happened to composite images for ClientBundles?
According to https://developers.google.com/web-toolkit/doc/latest/DevGuideUiImageBundles, multiple images in the same ClientBundle should usually be merged to a composite image, quote: Multiple ImageResources are declared in a single ClientBundle, which is a composition of many images into a single image And I remember, that I tried and confirmed this, when I first used it a few years ago. But I don't see this happening anymore: - Either we get data URIs (for small images), - or we get separate *.cache.jpg images for each ImageResource in the ClientBundle (for large images, or if setting set-property name=ClientBundle.enableInlining value=false/) Is this correct, or is it a bug? Can I maybe even rely on GWT not producing composite images anymore [*]? [*] This would allow me to use new Image(imageResource.getSafeUri()), which would be useful in certain circumstances (e.g. when printing the page), as it uses a foreground image instead of a background image. -- 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/-/SZ7ken7Ajn8J. 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: Future of GWT survey
Please excuse me for this negative feedback, but in my opinion, the survey is rather suggestive in that it presupposes that GWT should develop into something that better supports other technologies. It asks a series of questions that point in this direction (and it offers some free text questions about new features/extensions etc.), but it forgets to ask, which things should NOT change. I would have liked to answer, that it should not lose its core library character. It doesn't come with bells and whistles, but its enormous flexibility - imposing zero restrictions on what you can do in web development - is essential (like with any successful language). Focus on reducing compile times even more, fixing all bugs, making it more extendable (e.g. by removing some unnecessary private modifiers, removing static state, ...), improving support of Java core libraries (and things that are close, like Guava, Joda, ...), improving some basic widgets - but don't impose the specialized concepts of Vaadin, GXT, ... (which absolutely do have their place, in their own frameworks!) on GWT itself. That's actually the only worry I currently have about GWT's future (Note: I believe it will turn out well). On Wednesday, September 19, 2012 3:23:24 PM UTC+2, Joonas Lehtinen wrote: What is your opinion on the future of GWT? How should GWT develop? What technologies should it better support? ... We all would like to get answers to these questions, right? To do so, we created survey with help of Ray Cromwell, Artur Signell, Mike Brock, David Chandler, Daniel Kurka and Bhaskar Janakiraman. If you want to help finding the best direction for GWT, please fill the survey at: http://bit.ly/GWT2012 (it will take just 10 minutes) When the results are collected, the will share the information with you. - Joonas @ Vaadin -- 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/-/5J6JhqkVerEJ. 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.
GWT Bean Validation + Hibernate Validator version?
What is the officially supported Hibernate Validator versionhttp://repository.jboss.org/nexus/content/groups/public-jboss/org/hibernate/hibernate-validator/that should be used in conjunction with GWT JSR 303 Bean Validationhttp://code.google.com/p/google-web-toolkit/wiki/BeanValidation? (Note: I'm using the word official, because the EXPERIMENTAL flag has now been removedhttps://groups.google.com/d/topic/google-web-toolkit-contributors/jyaODjNwVj0/discussion in trunk.) *4.0.2 GA* 4.0.2 GA is the version the validation sample uses in its pom.xmlhttp://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/validation/pom.xml. But this doesn't really work: Compiling with -strict fails with Errors in 'jar:file:/path/to/gwt-2.5.0.rc1/gwt-user.jar!/org/hibernate/validator/super/org/hibernate/validator/constraints/impl/URLValidator.java' Line 20: The import org.hibernate.validator.constraints.URL cannot be resolved Line 26: URL cannot be resolved to a type *4.2.0 Final* I also tried 4.2.0 Final, but this fails twofold: First problem: [ERROR] Errors in 'jar:file:/path/to/gwt-user.jar!/org/hibernate/validator/super/org/hibernate/validator/engine/PathImpl.java' [ERROR] Line 72: The constructor NodeImpl(String) is undefined Second problem: Version 4.2.0 requires Joda time, which cannot be used on the client side * * *4.1.0 Final* * * After some experimenting, I found that this is the only version that really works. So I'd like to know, if this is the best version to use for now, and where we can find out when to upgrade to which newer version. -- 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/-/1KT13z1edJ0J. 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 Bean Validation + Hibernate Validator version?
Ok, thanks. On Monday, September 17, 2012 3:34:48 PM UTC+2, Thomas Broyer wrote: This has actually been reported a few days ago: http://code.google.com/p/google-web-toolkit/issues/detail?id=7661, and in the comments on the wiki page. GWT is built against 4.1.0 Final and depends on Hibernate Validator internals (NodeImpl, PathImpl implementations, etc.), so I'd suggest you stick to that version, at least for compiling your client code (you could use 4.2.0 GA on the server-side for instance). -- 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/-/5eA3hmlrQSUJ. 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: Properties file with GWT
1. The java.util.Properties class isn't available on the client side. It's possible to get a properties file to the client side (e.g. using com.google.gwt.http.client.RequestBuilder), but you'd have to find a way to parse it. So why not use JSON format instead? Or GWT-RPC (which can contain the ids as a Collection or Map, or whatever you need)? 2. It sounds as if you don't have any control over your host page, but if you do, it would be more efficient to put the data directly there, similar to the example in http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/i18n/client/Dictionary.html. This way you wouldn't need to make the extra server request. 3. Another possibility would be to have the values directly in your GWT client side source code. This would however require a re-compile of your client code, and a reload by the user. If you choose this option, and you still want a Properties file or something, you can use a TextResource to directly include it with the GWT JavaScript file (see https://developers.google.com/web-toolkit/doc/latest/DevGuideClientBundle#TextResource) On Friday, September 14, 2012 9:37:18 PM UTC+2, Deepak Singh wrote: Hi, I have some div id's in my host html page. Which might change regularly, based on that we will show / hide some content. I need to manage this requirement. I thought to update the id's in a properties file on client side and the file will be read on client side and shows / hides the content based on id's found in properties file. Is it a good approach ? If yes, how to use properties file ? Regards Deepak Singh -- 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/-/tdzrZsZ6hacJ. 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.
Debugging Fails with IBM JDK
I installed the GWT today and ran through the getting started document. When I tried, Debug As Web Application, I got the following: Unable to start embedded HTTP server java.lang.RuntimeException: Unable to create a DevAppServer at com.google.appengine.tools.development.DevAppServerFactory.createDevAppServer(DevAppServerFactory.java:173) at com.google.appengine.tools.development.DevAppServerFactory.createDevAppServer(DevAppServerFactory.java:69) at com.google.appengine.tools.development.DevAppServerFactory.createDevAppServer(DevAppServerFactory.java:52) at com.google.appengine.tools.development.gwt.AppEngineLauncher.start(AppEngineLauncher.java:84) at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509) at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068) at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811) at com.google.gwt.dev.DevMode.main(DevMode.java:311) Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodException: sun.net.www.protocol.https.Handler.openConnection(java.net.URL) at com.google.appengine.tools.development.StreamHandlerFactory.getDeclaredMethod(StreamHandlerFactory.java:161) at com.google.appengine.tools.development.LocalURLFetchServiceStreamHandler.init(LocalURLFetchServiceStreamHandler.java:52) at com.google.appengine.tools.development.StreamHandlerFactory.init(StreamHandlerFactory.java:106) at com.google.appengine.tools.development.StreamHandlerFactory.install(StreamHandlerFactory.java:65) at com.google.appengine.tools.development.DevAppServerImpl.init(DevAppServerImpl.java:89) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57) at java.lang.reflect.Constructor.newInstance(Constructor.java:539) at com.google.appengine.tools.development.DevAppServerFactory.createDevAppServer(DevAppServerFactory.java:165) ... 7 more Caused by: java.lang.NoSuchMethodException: sun.net.www.protocol.https.Handler.openConnection(java.net.URL) at java.lang.Class.throwNoSuchMethodException(Class.java:304) at java.lang.Class.getDeclaredMethod(Class.java:621) at com.google.appengine.tools.development.StreamHandlerFactory.getDeclaredMethod(StreamHandlerFactory.java:157) ... 16 more I'm using the IBM Java 7 SDK, which clearly does not have the same set of sun packages as the Oracle SDK. Why is GWT making calls into the sun classes instead of, in this case, java.net? The sun classes are not intended for application use. Chris -- 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/-/KcAtbPrZo8QJ. 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.
DevAppServer Creation Fails With IBM JDK
Installed GWT today and ran through the steps in the Getting Started guide. When I tried to debug the sample I created as a web application, GWT was unable to create the DevAppServer: Initializing App Engine server Unable to start embedded HTTP server java.lang.RuntimeException: Unable to create a DevAppServer at com.google.appengine.tools.development.DevAppServerFactory.createDevAppServer(DevAppServerFactory.java:173) at com.google.appengine.tools.development.DevAppServerFactory.createDevAppServer(DevAppServerFactory.java:69) at com.google.appengine.tools.development.DevAppServerFactory.createDevAppServer(DevAppServerFactory.java:52) at com.google.appengine.tools.development.gwt.AppEngineLauncher.start(AppEngineLauncher.java:84) at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509) at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068) at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811) at com.google.gwt.dev.DevMode.main(DevMode.java:311) Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodException: sun.net.www.protocol.https.Handler.openConnection(java.net.URL) at com.google.appengine.tools.development.StreamHandlerFactory.getDeclaredMethod(StreamHandlerFactory.java:161) at com.google.appengine.tools.development.LocalURLFetchServiceStreamHandler.init(LocalURLFetchServiceStreamHandler.java:52) at com.google.appengine.tools.development.StreamHandlerFactory.init(StreamHandlerFactory.java:106) at com.google.appengine.tools.development.StreamHandlerFactory.install(StreamHandlerFactory.java:65) at com.google.appengine.tools.development.DevAppServerImpl.init(DevAppServerImpl.java:89) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57) at java.lang.reflect.Constructor.newInstance(Constructor.java:539) at com.google.appengine.tools.development.DevAppServerFactory.createDevAppServer(DevAppServerFactory.java:165) ... 7 more Caused by: java.lang.NoSuchMethodException: sun.net.www.protocol.https.Handler.openConnection(java.net.URL) I'm using the IBM Java 7 SDK. Why is GWT making calls directly to classes in the sun packages and not, in this case, java.net? Chris -- 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/-/oB9s0LU3Rz8J. 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.
[gwt-contrib] Deprecating DeRPC classes
https://developers.google.com/web-toolkit/doc/latest/DevGuideServerCommunication#DevGuideDeRPC says about Direct-Eval RPC: This feature did not work out as planned, and the GWT team strongly discourages its use. However, the classes RpcServlet, RpcService etc. are not marked as deprecated. It's easy to mistype RemoteService as RpcService, which doesn't cause any warning. If this happens, it can be very difficult to spot the problem, and it's not trivial to revert to RemoteService, see for example: http://code.google.com/p/google-web-toolkit/source/diff?spec=svn11258r=11229format=sidepath=/trunk/samples/validation/src/main/java/com/google/gwt/sample/validation/client/GreetingService.javaold_path=/trunk/samples/validation/src/main/java/com/google/gwt/sample/validation/client/GreetingService.javaold=10642 -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: Nasty overlay types restrinction : Only one JavaScriptObject type may implement the methods of an interface
Sebastián: You may already be aware of this, but when I first looked
into this problem it was a subtlety I had overlooked.
If you have -
interface A { void a();}
interface B extends A { void b(); }
interface C extends A { void c(); }
You can't have -
final class BImpl implements B {
void a() { ... }
void b() { ... }
}
final class CImpl implements C {
void a() { ... }
void c() { ... }
}
Because as has been pointed out a would be implemented twice.
However, you can have -
final abstract class AImpl implements A {
void a() { ... }
}
final abstract class BImpl extends A implements B {
void b() { ... }
}
final abstract class CImpl extends A implements C {
void c() { ... }
}
Because in this case a is only implemented once.
It may not help but when I was wrapping a third-party lib, I found the
above pattern worked almost everywhere.
Chris
On Fri, Sep 7, 2012 at 4:53 PM, Alain Ekambi jazzmatad...@gmail.com wrote:
Your approach however would make this kind of Java API much more
confortable to Java users
Is nt it why you are wrapping YUI in the first place ? To make it
confortable for Java users ?
2012/9/7 Sebastián Gurin sebastigu...@gmail.com
Thanks Paul, Nino and Thomas
Paul: yes I suppose that too, but interfaces do not implement methods, so
I thought it is strange.
Nino: I do not want to make object wrapping as you suggested because I
want my library user's to use the overlay types directly for a zero-overhead
API. Your approach however would make this kind of Java API much more
confortable to Java users.
Thomas, thanks. Yes I'm using .cast() a lot, it is much more confortable
than java casting. Also I have designed this YUI java API to be the most
similar to the native javascript API. So code using mine YUIGWT will look
strange to java programmers, for example, a js literal object definition :
in javascrpt:
var p = {name: seba, age: 28}
in java:
Person p = Person.create().name(seba).age(28);
On Thursday, September 6, 2012 3:22:16 PM UTC-3, Sebastián Gurin wrote:
Hi all. I'm writing a lot of GWT overlay types for my new project YUIGWT
- http://code.google.com/p/yuigwt/. I'm creating a nice and rich java
hierarchy of overlay types there.
Today I discovered that it is not good to let overlay types (extends
JavaScriptObject implement interfaces because it seems that for a certain
interface, no more than one overlay type can implement its methods. The
error in question is pasted below, but this arrises a big question for me:
While I understand perfectly what the error means, I would really
appreciate if somebody can explain me the reasons behind this nasty
restriction ? ??
[ERROR] [org.sgx.yuigwt.YuiGwtTestOnline] - Line 9: Only one
JavaScriptObject type may implement the methods of an interface that
declared methods. The interface (org.sgx.yuigwt.yui.yql.api.YQLQueryResult)
is implemented by both (org.sgx.yuigwt.yui.yql.api.desc.DescResult) and
(org.sgx.yuigwt.yui.yql.api.wheather.forecast.WheatherForecastResult)
Thanks in advance.
--
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/-/GAl_l1hUSQkJ.
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.
--
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.
--
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: How to obfuscate RequestFactory type name, not only the operations ( GWT 2.4 )
On Thursday, September 6, 2012 3:58:34 PM UTC+2, Thomas Broyer wrote: Would you mind filing an issue in the tracker (if no one already did it) ? I did a few years ago: http://code.google.com/p/google-web-toolkit/issues/detail?id=5729 It was closed as a duplicate of http://code.google.com/p/google-web-toolkit/issues/detail?id=5394, which is fixed and released in 2.4... but it doesn't really fix 5729. -- 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/-/K7InVqQH19cJ. 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: compiled file ending with *.htm instead of *.html
I assume it should be possible by extending IFrameLinker, and overriding getCompilationExtension(...) to return .cache.htm. Then define and add your linker as in /com/google/gwt/core/Core.gwt.xml I haven't tried it though, so you may encounter some difficulties (?) On Wednesday, September 5, 2012 4:59:05 PM UTC+2, James wrote: Is there a possible way to pass some parameter to compiler so the compiler can generate javascript file ending with *.htm instead of *.html? So far I just manually edit the generated javascript files and change the file extension. Thanks, James -- 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/-/TYqKXJwWTHoJ. 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 Compilation Time Performance Improvement
Another possibility would be to replace some classes with stubs (- dependency injection) - only activating the functionality that is currently interesting. The rest doesn't need to be compiled. Of course it depends on the application's architecture, if this can be done easily or not. On Tuesday, September 4, 2012 10:31:46 AM UTC+2, Thomas Broyer wrote: On Tuesday, September 4, 2012 9:04:05 AM UTC+2, Hilco Wijbenga wrote: On 3 September 2012 23:10, Niraj Salot salot...@gmail.com wrote: 1) Will this help us in Improving the compilation time? No. 2) IF we change only Module 2 and then compile Module Main, will GWT still compile Module 1 as it is inherited by Module Main? Yes. Please share your views on above scenario. We have even tried out GWT 2.5 option but no help in performance improvements. You might want to check out code splitting (see [1]). I haven't tried it but it *might* be possible to break up your app into separately compiled modules. What we really need is a linker that takes precompiled modules (each stored in, say, a JAR) and combines them into an application. I know this has been discussed but I am not aware of anyone actually working on it. Unless code splitting already allows for all this... [1] https://developers.google.com/web-toolkit/doc/latest/DevGuideCodeSplitting No. Code Splitting is about generating a bunch of JS scripts instead of a single one. The compilation process is still monolithic. What could possibly help is to precompile the modules into *.gwtar files, but it's something that's supposed to only be used by GWT itself (you'll find such gwtar files in the gwt-user.jar) AFAIK. At least it's not designed to build libraries, as the gwtar files depend on the version of GWT that produced them (IIUC). No, really, 4-6 minutes is not that long given the size of the project, depending on the machine (number of cores/processors, memory, disks, etc.) and JVM tweaks (-Xmx, -Xms, etc.) -- 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/-/zXDkjxU8aGUJ. 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: Migrating CSS to GWT 2.4
They're in gwt-user.jar, in subdirectories of package com.google.gwt.user.theme. You can also view them in the subversion browser, e.g. http://code.google.com/p/google-web-toolkit/source/browse/tags/2.4.0/user/src/com/google/gwt/user/theme/standard/public/gwt/standard/standard.css The css files will be copied automatically to a subdirectory of your war folder (mymodulename/gwt/...), if your module inherits e.g. inherits name='com.google.gwt.user.theme.standard.StandardResources'/ If you also want to automatically inject the standard.css into your host HTML page, then you would use inherits name='com.google.gwt.user.theme.standard.Standard'/ instead. On Thursday, August 30, 2012 3:23:17 AM UTC+2, GWTFan wrote: We are in the process of migrating from GWT 1.5.3 to 2.4. I have moved the gwt folder containing css files from public to war folder. But as they were from 1.5.3 apparently some new definitions are missing. Where do I find the standard.css and other css files for GWT 2.4? Thanks and appreciate any pointers. -- 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/-/TvwvsllyIAsJ. 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: How to set stroke width for Canvas Context2d?
To set the width of the stroke, use ctx.setLineWidth(double) In general, FillStrokeStyle currently has three subclasses: - CanvasGradient - CanvasPattern - CssColor They don't have public constructors. CanvasGradient can be created by using ctx.createLinearGradient() or ctx.createRadialGradient(). CanvasPatterns can be created with ctx.createPattern(). CssColors can be created with CssColor.make(). There's also a shortcut: A CssColor object is created in the background, when you use some of the overloaded methods of Context2d like ctx.setStrokeStyle(String color) or ctx.setFillStyle(String color). On Thursday, August 30, 2012 12:44:22 AM UTC+2, mark wrote: Hi, I'd like to change the stroke width but am not clear how to do this: Context2d context = ...; context.setStrokeStyle(FillStrokeStyle ?); context.strokeRect(…); I'm not sure how to create a FillStrokeStyle object (or specifically how to create one where I can control its width). Anyone know? Thanks http://google-web-toolkit.googlecode.com/svn/javadoc/2.2/com/google/gwt/canvas/dom/client/FillStrokeStyle.html -- 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/-/e5_3EDLYqxoJ. 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: FF DevMode plugin + Memory leaks (+ Address already in use)
I analyzed this a bit more (this time on Linux), and I noticed, that the number of Thread also grows: 1 thread per reload. Again, this happens only with Firefox, not with Chrome. So probably the ClassLoader references will be discarded only when the Thread terminates... One more thing that might be interesting: When closing the entire FF instance (just closing the tab is not enough), then the threads are discarded, and Heap/PermGen space can be garbage collected. By the way, closing the FF instance leads to the following Exception printed by the DevMode server: 10:53:21.549 [ERROR] [mymodule] Remote connection lost com.google.gwt.dev.shell.BrowserChannel$RemoteDeathError: Remote connection lost at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:308) at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:547) at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.EOFException: null at java.io.DataInputStream.readByte(DataInputStream.java:250) at com.google.gwt.dev.shell.BrowserChannel$Message.readMessageType(BrowserChannel.java:1100) at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:284) at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:547) at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364) at java.lang.Thread.run(Thread.java:662) On Tuesday, August 28, 2012 2:07:02 AM UTC+2, Brian Slesinsky wrote: That's an interesting report. We always want to garbage collect the ClassLoader when the session is over and if that doesn't happen, it's a bug. I don't know why Firefox would behave differently; the JVM side should work the same way for Firefox versus Chrome. The only thing I can think of is some difference in distributed garbage collection, but that shouldn't matter once the session ends. Alan's not on the team anymore. I'd like to fix this, but I'm busy with other things and I don't have a good idea where to begin. If someone's handy with a memory profiler, figuring out what's preventing the classloader from being gc-ed in this case would be very useful. - Brian -- 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/-/0tBYLSRxh1AJ. 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: Best practices waiting for DOM parsing
I was under the impression that all DOM manipulation calls are synchronous, are you sure it's not GWT using the Scheduler under the hood to run some of your code asynchronously? Can you give some example code? On Tue, Aug 28, 2012 at 2:33 PM, Joseph Lust lifeofl...@gmail.com wrote: I wanted to ask the community's opinion on the best practice for waiting for a DOM resource to become available. Use Case: You make an elaborate component via UiBinder or injecting some HTML/SVG into the DOM and upon executing the following statement trying to access an element that was injected, the DOM does not see it (i.e. inject 2MB of SVG) due to DOM parsing lag. Work Arounds: Schedule recurring timer to check if the element is available and then continue the program flow (now that the element's accessible in the DOM). OR Schedule a deferred timer and then continue (less robust, does not always work). So, curious what other folks have been using in this case where the GWT code must wait to wait for DOM parsing lag time. It seems to me like this is something there should be an official GWT function for doing as other frameworks do have functions to wait until an object becomes available in the DOM. Sincerely, Joseph -- 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/-/JpBdhNvNWbIJ. 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. -- 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: DART vs. GWT
About Dart: - I really (!) hope that Dart will succeed. - Ideally, Dart would even become the new JavaScript alternative in all browsers (however, AFAIK a few browser vendors have signaled, that this ain't gonna happen). If not, then it could maybe still be successful with dart2js. About GWT: - GWT allows to code in *Java* for the client side, which is perfect, if you already use *Java* on the server side. - There is no significant amount of existing Dart code for the server side, so Dart does not have that advantage. Conclusion: GWT + Dart would be such an awesome combination: GWT compiling Java to Dart. And then Dart to JS only if necessary. - This would require changing GWT internals, - but it wouldn't require changing the GWT API and programming techniques much (except for low level JSNI and JSO) - remember, that a lot of the GWT API is about manipulating the DOM (which stays the same no matter if the underlying language is JS or Dart), handling browser events, ... - As long as you want to work with Java on the server side, it's a good idea to use GWT - otherwise you'd have to duplicate common parts of your code for the server (Java) and client side (Dart) - like in the medieval days before GWT. (I hope we'll never have to fall back to that situation.) Alternative: The alternative would be that Dart also succeeds on the server side, completely replacing Java. This is rather unlikely, but if things like O/R mapping, fully-fledged IDEs, and anything of value that Java provides is available in Dart someday, plus if it provides any real advantage over Java, then I'm the first one to switch completely to Dart. Then we wouldn't need GWT anymore, and Dart would probably adopt all useful GWT features. (And it should be straightforward to port existing GWT code to Dart.) On Wednesday, August 22, 2012 5:57:42 PM UTC+2, deepak chauhan wrote: One question is disturbing me from a long time. Why Google invented DART, when GWT is already there? -- 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/-/G02R2U9lzkcJ. 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: how to write a 2D game by using GWT and html5.
Have you looked at PlayN? http://code.google.com/p/playn/ On Tue, Aug 28, 2012 at 8:51 PM, Joey lihaizhou...@hotmail.com wrote: I want to write a simple animated 2D game by using GWT and HTML5. The game basically needs to keep running several animations all the time, but I do not know what libraries or techniques I should use to achieve this. Based on my experience in GWT so far, I know I can just use plain GWT and GWT-animation to achieve what I want. This is the easiest way for me to achieve. However, I hope I can make the game look and feel a bit more professional and attractive. So GWT-Canvas may be the good option for me to write the animation. Physical reactions and Audio are also the important concern. Please give me some advices about the following questions. 1. To write the animations, which technique should I use, plain GWT-animation or GWT-Canvas+HTML5. Which one has better performance? (the game will be running on the webpage, so the level of performance is the most important for me) 2. Is there any good libs I should definitely use for writing 2d games? I do not prefer the complicated lib because my game is pretty simple. 3. I am considering using some game engine. My game is easy and simple, I could make a fake physical reactions by just using some math functions to run the animations. but if the game engine is easy and handy to use, then I would prefer using game engine. So is there any good one out there for beginners? 4. Please give me some advices about making the game audio. are there any good audio libraries for GWT projects? Thanks. -- 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/-/ppy_atK6jRkJ. 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. -- 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: FF DevMode plugin + Memory leaks (+ Address already in use)
Yes. I disabled all Add-Ons: All Extensions (except for the GWT Extension) and all Plugins, and restarted Firefox. On Wednesday, August 29, 2012 12:12:03 AM UTC+2, Brian Slesinsky wrote: Does the connection leak happen with all plugins (other than GWT) disabled? -- 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/-/Y47n4p71LKAJ. 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: GwtChosen: make your select boxes much more user-friendly
Very useful. Great widget. On Tuesday, August 28, 2012 10:34:09 PM UTC+2, Julien Dramaix wrote: Dear community, I just released the first version of GwtChosen. GwtChosen is the entire rewritte in Google Web Toolkit of the Chosen component (http://harvesthq.github.com/chosen/) making this nice component available for all GWT developers. It is available as a +GwtQuery plugin or as a widget. Check the example and doc : http://jdramaix.github.com/gwtchosen/ Julien -- 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/-/Z8P3L76eDXEJ. 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.
FF DevMode plugin + Memory leaks (+ Address already in use)
When I analyze a DevMode process's memory usage (e.g. using jconsole), it shows that Heap and Non-Heap (PermGen) Memory usage increases, whenever the page is reloaded. This happens both when I run DevMode with Firefox 14, as well as Chrome 21. The difference is however, that - with Chrome, Heap and PermGen usage restores to a very low value after calling Perform GC - whereas in Firefox the PermGen stays at the high value, and the Heap just decreases slightly. After a number of reloads, this leads to an out of memory (Heap or PermGen, depending on which reaches the limit first). More often than not, the out of memory is not printed (which is usual for out of memory errors). *How to reproduce the error?* Create a simple GWT project (e.g. the one that's auto-generated by Eclipse), use Firefox, press the reload-button repeatedly (tested on OS X 10.6, but I've encountered similar memory problems on Linux amd64, too) *Solution?* Without knowing anything about the details of the FF plugin, it looks as if the Chrome plugin discards the ClassLoader entirely (so the PermGen space can be freed up http://stackoverflow.com/a/148707/291741), whereas FF probably keeps a reference to the ClassLoader somewhere (?) *Problems when restarting DevMode* The problem may also explain, why many people are seeing an [ERROR] Unable to bind socket on port 9997 -- is another session active? java.net.BindException: Address already in use after restarting DevMode (see e.g. https://groups.google.com/d/topic/google-web-toolkit/btPIOoriq_o/discussion , http://code.google.com/p/google-web-toolkit/issues/detail?id=4312 , http://code.google.com/p/google-web-toolkit/issues/detail?id=4514 , ...). It would also explain, why it's often dismissed as cannot reproduce (because it cannot be reproduced with Chrome). But when stopping a DevMode server that is (nearly) out of memory, it may hang. And you usually won't see an error message (the reason why I finally found this issue, is that I did get it a few times now). Plus, in Eclipse it looks as if DevMode had already terminated (the red stop button turns gray). *Question:* Is it a good idea to create another new issue for this? I'd like to ask here first, if anybody knows what the Status is? @AlanLeung? -- 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/-/aDdcADCmUbIJ. 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: Errai Experience?
Used in a number of real projects. API is very good and straight forward, dev team support also great. I was able to employ web sockets on one project which really made it fly. Real-time financial price distribution. The server side is wired up using Guice, which we struggled to sensibly(ended up statically accessing stuff) make work with Spring, so could do with a bridge there. I wouldn't necessarily recommend the GWT RPC substitute. While it works, it synthesis's subscription requests under the hood, so one simple call results in a number of http requests. (subscribing and unsubscribing) to a GWT RPC single call. Played havoc with ntlm and IE, re-authenticating every post requests. Firebug/Chrome dev tools very handy to see what's going on. On Tuesday, 14 August 2012 16:50:47 UTC+10, Ed wrote: What is your experience with RedHat Errai ( http://www.jboss.org/errai/) It uses GWT to build rich web app's. Is it mature?..., too early to jump in, ... ? anybody used it in real projects?... JS output overhead ?... - Ed -- 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/-/Ea-fhyCMlDwJ. 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.
Eclipse Update has broken all GWT Projects?
I just updated eclipse and now all GWT projects are broken. I inspect the installation and I see everything is installed, the problem is that: *All my run configurations are gone *There is no option to run anything as Web Application. *Error log includes: -Unable to restore perspective: Workspace - Java. -Problems occurred when invoking code from plug-in: org.eclipse.ui.workbench. *Errors in build path: [Persisted Container] com.google.gwt.eclipse.core.GWT_CONTAINER gwt-user.jar (missing) gwt-dev.jar (missing) Can anyone offer a suggestion what I might do to fix this? What is a persisted container? Is there a roll-back mechanism in Eclipse? -- 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/-/DNNGpIO9l20J. 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: How can we save state of a GWT page?
I'd advise against storing anything other than a session authentication token in the cookie, it is sent with every request, including static resources etc., so can significantly increase the traffic of your app. Storing it in the URL as Dennis suggested is a better idea, I'd suggest you check out the activities and places tutorial - https://developers.google.com/web-toolkit/doc/latest/DevGuideMvpActivitiesAndPlaces On 26 Jul 2012 08:00, Dennis Haupt d.haup...@googlemail.com wrote: if its not too much data, you can use autobeans to serialize your data class and store the stuff in a cookie or the url itself. i've been doing something similar, just with a selfmade serialization mechanism instead of the autoproxy one. Am 26.07.2012 08:14, schrieb Rubina: Hi All, We have one requirement to implement in GWT application. Below example will clear the requirement – There are 3 screensin application. Suppose, useris on 2ndscreen after moving from 1^st screen to 2ndscreen. When user clicks on Next button on first screen, then some RPC call is executed and fetch data from some external database. This data is used to display on 2^nd screen. Now user bookmarks the browser URL (2^nd screen) and closes the browser window. Next time, now user directly wants to navigate to the 2^nd screen without repeating the work done on 1^st screen. We want to store the state of 2^nd screen somehow on browser. If this screen launches, all Next and Previous button should also work properly. Is this requirement achievable, if yes then which GWT APIs provides this feature? Please advice. -- 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/-/VH8-qdGcKvMJ. 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. -- -- 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. -- 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: SuperDevMode stuck on compiling
Posted... http://code.google.com/p/google-web-toolkit/issues/detail?id=7513 Thank you for all your help! On Wednesday, July 11, 2012 12:16:31 PM UTC-4, Thomas Broyer wrote: On Wednesday, July 11, 2012 5:46:16 PM UTC+2, Chris Gamache wrote: I am using Ext-Js LGPL via GWT-Ext, and they have indeed modified the Array prototype. Not much I can do about that. I'm stuck there. I hacked in the modification, and it will get through to compile now. Is there already an issue in the tracker for the xsiframe generator bug/bad practice? I don't know of any, and this __getPropMap seems to only be used for SuperDevMode so it's not surprising that this bug hadn't been discovered yet. -- 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/-/mQuuOWKgH0wJ. 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: SuperDevMode stuck on compiling
Stopped on that line above when propName == 'remove' here's the call stack:
console.trace()
(anonymous function)
(anonymous function)
evaluate
InjectedScript._evaluateOn
InjectedScript._evaluateAndWrap
InjectedScript.evaluateOnCallFrame
computePropValue mymodule.nocache.js:326
mymodule.__getPropMap mymodule.nocache.js:389
getBindingParameters dev_mode_on.js:324
compile dev_mode_on.js:388
runBookmarklet dev_mode_on.js:414
(anonymous function) dev_mode_on.js:427
(anonymous function)
On Wednesday, July 11, 2012 5:38:54 AM UTC-4, Thomas Broyer wrote:
On Tuesday, July 10, 2012 11:40:22 PM UTC+2, Chris Gamache wrote:
I know it's poor form to bump one's own thread, but I'm down to the end
of my rope:
I'm not sure if this has anything to do with anything, but this is from
my nocache.js file, where the error had occurred:
function computePropValue(propName){
var value = providers[propName](), allowedValuesMap = values[propName];
if (value in allowedValuesMap) {
return value;
}
var allowedValuesList = [];
for (var k in allowedValuesMap) {
allowedValuesList[allowedValuesMap[k]] = k;
}
if (__propertyErrorFunc) {
__propertyErrorFunc(propName, allowedValuesList, value);
}
throw null;
}
propName is set to 'remove' and I can't for the life of me figure out
where GWT is getting that. It is certainly not in the values array. The
script execution fails when it tries to find 'remove' and it is not in
allowedValuesMap. Adding to that problem, __propertyErrorFunc is undefined.
That sure is strange. What does the callstack look like at that point?
--
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/-/Mqmg7TIol0wJ.
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: SuperDevMode stuck on compiling
I am using Ext-Js LGPL via GWT-Ext, and they have indeed modified the Array
prototype. Not much I can do about that. I'm stuck there.
I hacked in the modification, and it will get through to compile now. Is
there already an issue in the tracker for the xsiframe generator bug/bad
practice?
On Wednesday, July 11, 2012 10:02:57 AM UTC-4, Thomas Broyer wrote:
On Wednesday, July 11, 2012 3:27:13 PM UTC+2, Chris Gamache wrote:
Stopped on that line above when propName == 'remove' here's the call
stack:
console.trace()
(anonymous function)
(anonymous function)
evaluate
InjectedScript._evaluateOn
InjectedScript._evaluateAndWrap
InjectedScript.evaluateOnCallFrame
computePropValue mymodule.nocache.js:326
mymodule.__getPropMap mymodule.nocache.js:389
getBindingParameters dev_mode_on.js:324
compile dev_mode_on.js:388
runBookmarklet dev_mode_on.js:414
(anonymous function) dev_mode_on.js:427
(anonymous function)
Are you using any third-party lib? One that would manipulate the
Array.prototype?
There's a small bug in the xsiframe linker generated script, rather a bad
practice than a bug actually: using an Array as if it were an Object
first, and using a for…in on it without checking hasOwnProperty; and when
combined with the other bad practice of augmenting prototypes, it breaks!
Not really a bug in the generated script, just that it can break
relatively easily if there are bugs/bad practices elsewhere.
I just tried it in Chrome dev tools' console:
var values = [];
values['foo'] = 'foo';
values['bar'] = 'bar';
for (var key in values) { console.log(key); }
The above should print foo and bar.
Now, add the following and then start the for loop again:
Array.prototype.remove = function() { console.log(remove); }
(using Array.prototype here, because 'values' is an array; would be true
with Obejct.prototype if 'values' had been initialized with {})
It'll now print foo, bar, remove.
Should be relatively easy to hack around it: locate __getPropMap in your
nocache.js and change the for-loop to add the following if:
for (key in values) {
if (values.hasOwnProperty(key)) {
...
}
}
--
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/-/dO3YxsIfnhMJ.
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.
SuperDevMode stuck on compiling
So I start CodeServer-- that works. Then I fire up a server instance of the GWT app and navigate to the landing page for the module. I hit my bookmarklet and it brings up the module - compile box. I hit compile. It just stays there. There's no logging output in the CodeServer. Stuck. I can see from the scripts panel in the debug tools that it has loaded dev_mode_on.js ... I also get an error after I hit the compile button : Uncaught ReferenceError: __propertyErrorFunc is not defined ... Hopefully that looks familiar to someone. CG -- 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/-/5TdOgCVWIzAJ. 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: How do I assign a JSONObject or JavaScriptObject to $wnd[x] in GWT?
Is this what you're after?
public native void set(JavaScriptObject value) /*-{
$wnd[test] = value;
}-*/;
public void onResponseReceived(Request request, Response response) {
JSONObject obj = (JSONObject) JSONParser.parseLenient(response.getText());
set(obj.getJavaScriptObject());
}
On Mon, Jul 9, 2012 at 8:24 AM, Boris Der Tester
borisdertes...@gmail.com wrote:
I read some var from my HTML-Page using GWT Dictionary. The var looks like
this:
var test = {
a : 123,
b : jg34l,
...
}
Now I get via AJAX-Call new content for my JS var. At the moment I overwrite
it like this:
public native void set(String key, String value) /*-{
$wnd[test][key] = value;
}-*/;
public void onResponseReceived(Request request, Response response) {
JSONObject obj = (JSONObject)
JSONParser.parseLenient(response.getText());
for (String key : obj.keySet()) {
JSONString val = (JSONString) obj.get(key);
set(key, val.stringValue());
}
}
As you can see I get a JSON-String. Parse it. Cast it to JSONObject. Take
every key-value-pair and use the JSNI-method to set the pairs.
There must be an easier way to do this?! I want simply to say: $wnd[test]
= myJsonObject
Thank you!
--
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/-/0xxTrLI-df4J.
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.
--
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: SuperDevMode stuck on compiling
I know it's poor form to bump one's own thread, but I'm down to the end of
my rope:
I'm not sure if this has anything to do with anything, but this is from my
nocache.js file, where the error had occurred:
function computePropValue(propName){
var value = providers[propName](), allowedValuesMap = values[propName];
if (value in allowedValuesMap) {
return value;
}
var allowedValuesList = [];
for (var k in allowedValuesMap) {
allowedValuesList[allowedValuesMap[k]] = k;
}
if (__propertyErrorFunc) {
__propertyErrorFunc(propName, allowedValuesList, value);
}
throw null;
}
propName is set to 'remove' and I can't for the life of me figure out where
GWT is getting that. It is certainly not in the values array. The script
execution fails when it tries to find 'remove' and it is not in
allowedValuesMap. Adding to that problem, __propertyErrorFunc is undefined.
If I remove
if (__propertyErrorFunc) {
__propertyErrorFunc(propName, allowedValuesList, value);
}
throw null;
it will get to compile. There are other issues beyond that, but at least it
will compile. The other problems are for a different thread.
Help!
On Monday, July 9, 2012 3:37:18 PM UTC-4, Chris Gamache wrote:
So I start CodeServer-- that works. Then I fire up a server instance of
the GWT app and navigate to the landing page for the module. I hit my
bookmarklet and it brings up the module - compile box. I hit compile. It
just stays there. There's no logging output in the CodeServer. Stuck.
I can see from the scripts panel in the debug tools that it has loaded
dev_mode_on.js ... I also get an error after I hit the compile button :
Uncaught
ReferenceError: __propertyErrorFunc is not defined ... Hopefully that
looks familiar to someone.
CG
--
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/-/g0bFcT5J2JMJ.
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: RF and REST
RestyGWT is worth considering - http://restygwt.fusesource.org/ On Tue, Jul 3, 2012 at 10:24 AM, chal...@gmail.com wrote: Please have anyone of you been successful with REST on a GWT project? What api's did you use. We are in the design stage of an app, we love GWT but want to liberate the architecture such that we can use the same server code for the clients (GWT and JQuery mobile). I don't know if RequestFactory (for the GWT client) can play nicely with a REST back end and we are not even sure how to go about it. Some googling revealed Restlet (which I think couples our server code to GWT) and Apache CXF. Any hint on which to use, and how to go about it? Big thanks. Sent from my BlackBerry® wireless handheld from Glo Mobile. -- 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. -- 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: ..Something other than an int was returned.. warnings in DevMode
Sorry not at a PC to lookup link for you but check the issue tracker it is a known bug with Chrome. On Jun 29, 2012 10:47 AM, Flori floon...@gmail.com wrote: Hey all, I have absolutley no idea why this warning appears.. maybe someone of u can give me an answer or a hint in the correct direction: [WARN] [pacadm] - Something other than an int was returned from JSNI method '@com.google.gwt.dom.client.DOMImplStandardBase$ClientRect::getLeft()': Rounding double (5.454545021057129) to int for int DevMode is still working.. but these warnings are endless (they don't appear in the javascript console)! I'm using gxt 2.2.5 along with gwt 2.4 (same with gwt 2.5 RC1). https://lh3.googleusercontent.com/-fhsOtpq1_Kg/T-14KRCADjI/APY/N95gZlEpF2s/s1600/warnings.png Thanks in advance! cheers Flori -- 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/-/vnJiefc3x5kJ. 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. -- 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: Communicating with the server
You could try Errai - http://www.jboss.org/errai Talking to the server is much easier, too! Leveraging ErraiBus, you can transparently and easily mix event-based and RPC-based functionality in your app as neccessary. When leveraging the bus, everything in your app is push, everything is asynchronous! On Tue, Jun 26, 2012 at 11:30 AM, Emil Daoura e.dao...@gmail.com wrote: Hi, I am new in GWT. I have a question about the Communication between a client and a server. I would like to create a GWT application that can do the following: The client A fires an event to the server and the server in his turn fire an event to the client B. Here the client B has to be able to listen to the event all the time. I wanted to send some event with few data in real time to a connected client B. is that possible? and if yes how can I do that? Thanks -- 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/-/ePbehCWHbGsJ. 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. -- 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.
