We need to call out some use cases that show how these settings would be used in practice, for posterity if nothing else.
Could you describe how we would handle each of these high-level intents that a developer might have? A) I want stack traces everywhere that it isn't costly. B) I want stack traces on every browser possible, and for browsers in which it is costly, I want to only burden a random 2% of those users. C) I want maximum fidelity stack traces everywhere, even paying for emulation on browsers that have native stack traces, if that's better. D) I want the smallest possible script size by default, but I'm willing to burdon a random 2% of users to capture stack traces. If we could write clear rules for each of these scenarios, then it's probably sound and easy enough to understand. On Wed, Nov 25, 2009 at 9:33 AM, BobV <[email protected]> wrote: > Since emulatedStack and stripStack are mutually-exclusive, I'd say to > switch to option number three and use the conditional property setters > to support the old value. Something like: > > <define-property name="compiler.stackMode" values="strip, native, emulated" > /> > <set-property name="compiler.stackMode" value="native" /> > <set-property name="compiler.stackMode" value="emulated" > > <when-property-is name="compiler.emulatedStack" value="true" /> > </set-property> > > Also, we should probably get around to adding a way to deprecate old > deferred-binding properties. > > -- > Bob Vawter > Google Web Toolkit Team > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
