I've applied the same technique to makePayloadOperations to slightly
reduce the request payload size (by removing false-positives in property
changes), as it's causing issues in our app.
It still, IMO, sends too many things in a request (every proxy
referenced by another proxy, even if not
Brian, can you review this CL?
http://gwt-code-reviews.appspot.com/1601805/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Reviewers: cromwellian,
Description:
Adding jscomp to the classpath for gwt user and dev projects.
Review by: cromwell...@google.com
Please review this at http://gwt-code-reviews.appspot.com/1606803/
Affected files:
M eclipse/dev/.classpath
M eclipse/user/.classpath
Index:
LGTM
In my working copy I also have a .factory and an entry in .classpath for
.apt_generated. See
http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation#Eclipse
http://gwt-code-reviews.appspot.com/1606803/
--
LGTM. Sorry, as an IntelliJ user, Eclipse often escapes my mind. :)
http://gwt-code-reviews.appspot.com/1606803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
http://gwt-code-reviews.appspot.com/1601805/diff/1/user/src/com/google/web/bindery/autobean/shared/ValueCodex.java
File user/src/com/google/web/bindery/autobean/shared/ValueCodex.java
(right):
http://gwt-code-reviews.appspot.com/1601803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
On 2011/12/06 06:11:56, stephenh wrote:
This patch uses Thomas's suggestion of static methods with srcElement to
avoid holding on to a scrollableElem that comes from outside the event
handler's closure.
http://gwt-code-reviews.appspot.com/1601803/
--
