On Friday, August 26, 2016 at 4:30:48 PM UTC+2, JonL wrote: > > I have always considered the deprecation of "DevMode" to mean the > deprecation of the "HostedMode"/GWT Dev Mode plugin combo and that SDM was > the non-deprecated version. It sounds like some are considering losing SDM > as the default run mode. I think that would be a mistake and would make it > appear that GWT is more cumbersome to use than it is. Hosted Mode w./ Dev > Mode Plugin was broken due to the deprecation of the NPAPI plugin, other > than possibly refactoring out SDM from the DevMode class, I would > personally consider removing SDM as breaking something that isn't broken > for no particular reason. >
I don't understand what you mean. DevMode can mean either "dev mode using the browser plugin", or "the c.g.g.dev.DevMode entrypoint class". SDM, to me, can only mean "dev mode using compiled-on-the-fly JS", so it'd be the opposite of "dev mode using the browser plugin", without saying "how" you run it. The opposite of "the c.g.g.dev.DevMode class" is CodeServer (i.e. "the c.g.g.dev.codeserver.CodeServer class"). And SDM could be used either through c.g.g.dev.DevMode or CodeServer. So for SDM, there's no terminology problem, and yet I don't understand what you mean by "removing SDM". CodeServer will stay, that's a given. The question (to the Steering Committee) is whether c.g.g.dev.DevMode will stay with only its SDM mode, or whether it'll be removed (and SDM can only run through CodeServer, which would remain the only "development mode" of GWT). -- 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/f247962e-bca9-4366-bb99-86485c4a2c7b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
