On Tue, Sep 30, 2014 at 12:06 PM, Brandon Donnelson <[email protected] > wrote:
> I was looking at this when updating the feature for GPE and thought this > might change in 3.0, but would be easy to adjust in GPE, I'm testing the > preview build now and things are working good. > > The only thing I care here is trying to avoid telling thousands of developer to pass a flag to get what we consider the recommended way. If we change the default then they will basically upgrade the SDK and reuse their existing configurations. So that depends on how soon people get the GPE updates (I thought lots of people might just only upgrade the SDK?) and if there is going to be need for additional instructions (e.g. need to recreate run/debug configuration). > But on the other hand if this changes, what do you think would happen, b/c > I would need to deal with the change right away so I can change it in GPE > and get IDEA to change the program arg. > > How do you see the flag getting changed? > > We would keep the flag the same but change the default. So passing -superDevMode or nothing enables superdev mode and passing -nosuperDevMode disables the superdev mode. > On Tuesday, September 30, 2014 11:57:56 AM UTC-7, John Stalcup wrote: >> >> Yeah I kind of agree. >> >> If DevMode support is removed in Chrome soon after the 2.7 release, we'll >> be wishing we'd made DevMode launches default to turning superDevMode on. >> >> On Tue, Sep 30, 2014 at 11:54 AM, 'Goktug Gokdogan' via GWT Contributors >> <[email protected]> wrote: >> >>> Thinking about it, we should probably make superDevMode opt-out instead >>> of opt-in and make it work out of the box for existing users instead of >>> asking them to add the -superDevMode. >>> >>> So what do you think about making superDevMode the default for dev-mode >>> in 2.7 release? >>> >>> PS: BTW, if you haven't already, take a look at the Daniel's video here: >>> https://plus.sandbox.google.com/+DanielKurka/posts/JsVKoQ9nvn5 >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "GWT Contributors" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] >>> . >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/google-web-toolkit-contributors/CAN%3DyUA2K2J_ >>> MBVVcwyFiBT54riyH_Wh_QL1ES0uXHP_YAn7yRg%40mail.gmail.com >>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA2K2J_MBVVcwyFiBT54riyH_Wh_QL1ES0uXHP_YAn7yRg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/b034b9b9-b349-463a-9186-e15d675235ed%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/b034b9b9-b349-463a-9186-e15d675235ed%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0N5nFvrBVi9RTLznFOOJCO8tTSWN%3DP5dvPD9pALkjdgA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
