Our plan is to make Super Dev Mode compile faster. Plan B is to use an extended release of Firefox for a while. (I believe Firefox 24 is the next one.)
Despite appearances, I'm not actually a C++ programmer and I'm not plugged into the Firefox community enough to know how realistic it is that it would break or what it would take to get working again. Unfortunately few people in the GWT community are interested in this level of advanced browser hackery, or the thread leak would be fixed by now. It's one of the reasons I wanted to avoid anything other than standard browser API's when writing Super Dev Mode. (The debugger API isn't really suitable because if we take it over for Dev Mode, there will be no way to attach a debugger to debug JavaScript.) - Brian On Thursday, August 8, 2013 3:55:26 PM UTC-7, Jens wrote: > > >> - Brian: Firefox architecture changes may break the Development Mode >> plugin by the end of the year. (The ContextStack service went away [1] and >> word is that they will be making more architectural changes [2]. This isn't >> the end of Development Mode because we still have Chrome, but we should get >> moving on Super Dev Mode. >> > > Would be good to know what "may break" means. How realistic is it? IMHO > its one of the most important things to figure out asap. > > As an example: I am developing on Mac OS. Safari plugin is gone, as you > stated Firefox is maybe gone by the end of year, Chrome is painfully slow > compared to Firefox, SuperDevMode is not an option either for most apps out > there (SDM takes ~40 seconds to recompile our app last time i tried it, and > its not a really large app). So what should I use then? > > Thats not a nice situation to be in if Firefox will really break DevMode > in the near future. Even today with Firefox the situation isn't great > because this known memory leak when using FireFox + DevMode regularly > drives me crazy. > > This all could easily become a real major issue among developers and their > every days work. > > Maybe there are also other things to explore beside SDM. Random thoughts: > Maybe its possible to provide a special Google Chrome build that is maybe > not that secure but can execute DevMode freaking fast. What about remote > connecting to Firefox/Chrome from the IDE? IntelliJ can do this already, > maybe it can be used with GWT? Something like IntelliJ's LiveEdit but with > GWT support would be so awesome. Maybe thats possible in combination with > incremental compilation you mentioned above? > > > -- J. > > > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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]. For more options, visit https://groups.google.com/groups/opt_out.
