Comment by bobbysoares:
I see use for public constructors in Overlay-Types when wrapping around JS
libraries. I say this because when it's necessary to enable the overlayed
types to be constructed from Java, where the choice is between the use of a
plain Java wrapper class or an Overlay-Typ
Comment by rj...@google.com:
JSOs can now implement interfaces. Rather than wishing for a constructor on
your JSO, you can implement to an interface and have your JRE code provide
an alternative, non-JSO implementation.
For more information:
http://code.google.com/p/google-web-toolkit/wiki/
Comment by sco...@google.com:
@bobbysoares: It's not clear to me, if you provided a public constructor,
what that constructor would actually return?
For more information:
http://code.google.com/p/google-web-toolkit/wiki/OverlayTypes
--~--~-~--~~~---~--~~
http
Comment by bobbysoares:
Scottb, I was suggesting for example having "new MyObject(...)" be replaced
with "MyObject.newInstance(...)" automatically (where newInstance would be
a method supplied by the developer which returns an instance of the class,
possibly natively, after calling the JS c
Comment by cromwellian:
It would be interesting to consider Constructor() as being rewritten to a
static method with an implicit call to createObject() and all references to
this rewritten to this$static. e.g.
public Foo(int x, String y) {
this.x = x;
this.y = y;
}
rewritten to
publi
Comment by sco...@google.com:
Regarding the hosted mode implementation: we should actually mangle the
method name into com_google_Person$someMethod. Adding the dollar-sign is
the convention for synthetics.
For more information:
http://code.google.com/p/google-web-toolkit/wiki/OverlayTypes
