Best I could come up with is to use a modified version of EditTextCell
instead, which at least highlights the text in the box on click. This
still seems like a bug or at least an area that needs improvement.
-TJ
On May 25, 10:23 am, tjmcc18 tjmc...@gmail.com wrote:
I have a CellTable which
If you are using an application server to run your services, making
use if connection pools and datasources at that level is usually an
easy way to share a pool of database connections.
-TJ
On May 26, 4:06 am, Myth17 nitishupr...@gmail.com wrote:
Do I need something like Struts? I dont want
I have a CellTable which makes use of TextInputCells to allow the user
to edit data. I would like this to behave in a spreadsheet like
manner such that the user can select the various textboxes and make
changes as they see fit. However, the default behavior for selecting
the textboxes is not
Try clicking though and editing the TextInputCells in the showcase.
It takes multiple clicks... how can I get around that?
http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellSampler
-TJ
On May 25, 10:23 am, tjmcc18 tjmc...@gmail.com wrote:
I have a CellTable which makes use
Anyone???
On Mar 2, 3:58 pm, tjmcc18 tjmc...@gmail.com wrote:
I just updated my app from 2.0.4 to 2.1.1. Now I am intermittently
seeing the following error:
Exception while dispatching incoming RPC call
java.lang.IllegalArgumentException: encodedRequest cannot be empty
When an unexpected error occurs on the client side, such as a
NullPointerException, the result is that an UmbrellaException is
thrown and that generally ends up being interpreted as a javascript
error by the browser. Those javascript errors are usually less than
helpful in determining what the
I just updated my app from 2.0.4 to 2.1.1. Now I am intermittently
seeing the following error:
Exception while dispatching incoming RPC call
java.lang.IllegalArgumentException: encodedRequest cannot be empty
at com.google.gwt.user.server.rpc.RPC.decodedRequest(RPC.java:228)
at
So to sum it up, for better performance in IE:
- Use uibinder when possible instead of constructing the layout manually
- Use div based widgets instead of VerticalPanel and HorizontalPanel
Does that sound about right? I'll give those a try and see if it speeds
things up. We use a lot of
Thanks everyone for the tips. I have found the source of some of my
current problems. One issue is that we were passing around a very
large and complex object in some of our RPC calls. I have heard that
serialization can be slow in IE, and I believe that is the case for
me. I redesigned the
I am working on a GWT application and over time it has become
extremely slow while running in IE7. It still runs very fast in
Firefox3 however. This leads me to believe there must be some GWT
specific programming techniques that while acceptable when running in
Firefox, cause IE to run very
The problem is in production mode when running the compiled
javascript.
On Feb 10, 12:35 pm, Jeff Schwartz jefftschwa...@gmail.com wrote:
Is the problem in dev or production?
On Feb 10, 2011 12:33 PM, tjmcc18 tjmc...@gmail.com wrote:
I am working on a GWT application and over time
of the speed of
that browser's JavaScript engine. In my most recent testing on
Windows XP, that boils down to:
Assign a relative speed of 1X to Chrome and Opera; they are
comparable.
Firefox 3.6.13 is about 3X.
IE8 is about 21X.
On Feb 10, 9:38 am, tjmcc18 tjmc...@gmail.com wrote
, there
are bottlenecks in any application. If you find and optimize those
bottlenecks in Speed Tracer, there's a good chance that you will be
able to improve performane in all browsers.
On Feb 10, 9:59 am, tjmcc18 tjmc...@gmail.com wrote:
Thank you very much for the information. I have no doubt
I've seen several posts regarding using JAAS with GWT, but not a lot
of answers. I'm trying to wrap my brain around how to use these two
technologies together to perform user authentication and
authorization.
The concept of using JAAS authentication with GWT seems straight
forward enough. I
14 matches
Mail list logo
