I definitely use a MVP/C model but not Places. I don't think I should be tided to one and only one MVP approach. However even if I did it's not clear how that would help the fact that the browser has a 'copy' or 'image' of the real thing...at the end of the day I need my IDE to make changes.
-Dave On Mon, Nov 3, 2014 at 7:51 AM, Timothy Michael Spear <n61...@gmail.com> wrote: > David, > > The problem is a fundamental disconnect in approach. In using Places, and > the MVP model, your application is supposed to be a series of much smaller > applications with minimal navigation required to re-enter a specific point. > I have very mixed perceptions on this multi-entry point development. > > Tim > > > From: David Hoffer <dhoff...@gmail.com> > Reply-To: <google-web-toolkit@googlegroups.com> > Date: Monday, November 3, 2014 at 9:45 AM > To: Google Web Toolkit <google-web-toolkit@googlegroups.com> > Subject: Re: Development Mode will not be supported in Firefox 27+ > > IMO, the loss of DevMode is a huge problem for GWT, I understand > SuperDevMode is its replacement but unfortunately that is no where near a > true replacement at least not yet. > > It's a bit hard to explain unless you have used both approaches on a large > project but the best way I can think of to explain it is that in > SuperDevMode you see an 'opaque' version of your source in the browser. So > yes you can 'see' your Java source in the browser and you can debug > it...but that's about it. E.g. you get to have an image or a copy of your > source in the browser. However that's all you get in SuperDevMode what you > don't get is the ability to find and edit your source code. I have an app > with hundreds of classes in the client side, there are no tools like my IDE > has for finding the code i want to jump to so I can inspect, set break > points, edit code, etc. > > So with SuperDevMode everything has to be done twice, you can debug in the > browser (but navigating the code is very painful) but then when you need to > make changes you need to re-navigate the code over in the IDE, edit the > code, and re-deploy. So in effect the code in the browser is an image of > the real code...you can't do anything with it really. > > I find SuperDevMode to be incredibly inefficient in developing GWT > applications, especially large ones where the strength of GWT is evident. > SuperDevMode might be fine for later stages of development, e.g. testing > stages where you don't need to make large code changes but rather just need > to fine tune what GWT generated but it's inadequate for development stages. > Personally I'm keeping an an old version of Firefox so that I can continue > to use DevMode. > > Please let me know if I'm missing something here or are other approaches. > > -Dave > > > On Mon, Nov 3, 2014 at 6:21 AM, Leejjon <leej...@gmail.com> wrote: > >> There's a developer version of Firefox coming out: >> >> https://blog.mozilla.org/blog/2014/11/03/the-first-browser-dedicated-to-developers-is-coming/ >> >> Maybe we can ask Mozilla to export the C++ symbols in this developer >> version, so the GWT dev plugin can work on this developer version of >> Firefox. >> >> Op dinsdag 4 februari 2014 01:01:41 UTC+1 schreef Brian Slesinsky: >>> >>> Mozilla has stopped exporting some C++ symbols that the Firefox plugin >>> relies on [1]. Therefore it's not possible to support Development Mode in >>> any new versions of Firefox starting with 27. >>> >>> As a workaround, I am doing one last release to get the plugin working >>> again with Firefox 24.2 (and hopefully newer point releases on the ESR >>> track). If you wish to continue to use Development Mode on Firefox, you >>> will need to download this version from Mozilla [2]. For more details see >>> the issue tracker [3]. >>> >>> Long-term, the plan is to improve Super Dev Mode. >>> >>> I apologize for the late notice; when I said at GWT.create that Firefox >>> could stop working with any release, I didn't expect it to be the next one. >>> >>> - Brian >>> >>> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=920731 >>> [2] http://download.cdn.mozilla.net/pub/mozilla.org/firefox/ >>> releases/24.2.0esr/ >>> [3] https://code.google.com/p/google-web-toolkit/issues/detail?id=8553 >>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Google Web Toolkit" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/google-web-toolkit/QSEjbhhHB4g/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> google-web-toolkit+unsubscr...@googlegroups.com. >> To post to this group, send email to google-web-toolkit@googlegroups.com. >> Visit this group at http://groups.google.com/group/google-web-toolkit. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-web-toolkit+unsubscr...@googlegroups.com. > To post to this group, send email to google-web-toolkit@googlegroups.com. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google Web Toolkit" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-web-toolkit/QSEjbhhHB4g/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > google-web-toolkit+unsubscr...@googlegroups.com. > To post to this group, send email to google-web-toolkit@googlegroups.com. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
