Revision: 6572
Author: rj...@google.com
Date: Fri Oct 30 15:47:46 2009
Log: Fixing the UiBinderTestApp. The tests don't use the app itself,
just its constituent modules, so I didn't notice that you could
no longer actually run the thing.
Desk review by amitmanjhi
Revision: 6573
Author: rj...@google.com
Date: Fri Oct 30 16:12:45 2009
Log: tr...@6570 was merged into this branch
Fixing the UiBinderTestApp
svn merge --ignore-ancestry -c 6572
https://google-web-toolkit.googlecode.com/svn/trunk .
Reviewers: hermes_google.com, rdamazio_google.com,
Message:
Review requested. Hermes, if you won't actually be able to get to this
please let me know as quickly as you can. Our deadline is very near.
Description:
Moving AttributeParsers to XMLElement, where they belong.
This is a pretty major
Reviewers: scottb, Lex, bobv,
Description:
Changes normal GWT vtable setup from
function foo() { ... }
_.foo = foo;
to
_.foo = function foo() { ... }
This reduces gzip'ed size on Showcase by 2%. Independent testing of
programs with 100% polymorphism shows that this can improve module
Very cool find.
On Fri, Oct 30, 2009 at 8:00 PM, cromwell...@gmail.com wrote:
Note, that if you don't desire correct stack traces, you can use the
following construct:
_.foo = function() { ... }
This results in a 6% post-gzip size reduction on Showcase. It might be
useful to introduce a
On Fri, Oct 30, 2009 at 8:24 PM, Bruce Johnson br...@google.com wrote:
In terms of design, I think this would actually be best as a
permutation-specific conditional deferred binding property that the compiler
is sensitive to (that was a mouthful), so that it would be possible to let
app
I wish we could wrap that all up in a simpler-to-understand package.
But a good article would make it at least bearable.
On Saturday, October 31, 2009, Ray Cromwell cromwell...@gmail.com wrote:
On Fri, Oct 30, 2009 at 8:24 PM, Bruce Johnson br...@google.com wrote:
In terms of design, I
Maybe it would make sense to move properties which the compiler relies on
into a special CompilerFlags.gwt.xml module, then if you want to change
class meta data, class cast checking, aggressive optimization, or stack
info, there'd be one centralized place to look at and document all the
flags.?
yep, and all of them should be per-perm
On Saturday, October 31, 2009, Ray Cromwell cromwell...@gmail.com wrote:
Maybe it would make sense to move properties which the compiler relies on
into a special CompilerFlags.gwt.xml module, then if you want to change class
meta data, class cast
I ran tests on iPhone and Android 2.0 SDK with Showcase and I didn't see any
significant different in startup times over wifi (3g/3dge may be a different
story), so the latency improvement really only shows up in degenerate test
cases where all functions are polymorphic, small and/or empty, so
101 - 110 of 110 matches
Mail list logo
