[gwt-contrib] Re: Patch to add getElementsByClassName support

2009-04-18 Thread Vitali Lovich
Do you have any suggestions regarding how to do the proper deferred binding for the various versions? Should I just put the typical JS check that regular libraries use? (i.e. if (!document.getElementsByClassName) { // provide fallback }. I thought the whole point of deferred binding was to get

[gwt-contrib] Re: Patch to add getElementsByClassName support

2009-04-18 Thread Vitali Lovich
If I put the check in a static block, then the check is only done once on startup, right? Is this acceptable, or is it frowned upon because it adds a slight penalty to the startup even if the developer never uses the function. Something like, static {

[gwt-contrib] Re: Patch to add getElementsByClassName support

2009-04-18 Thread Vitali Lovich
Also, what's the difference between DOMImplMozilla DOMImplMozillaOld in terms of Firefox versions? And what versions of each browser are supported? Are all versions of Safari, FF, Opera supported as much as possible? Is there a minimum version for any of them? On Sat, Apr 18, 2009 at 4:05

[gwt-contrib] Comment on OverlayTypes in google-web-toolkit

2009-04-18 Thread codesite-noreply
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