I'll also take this oppurtinity to explain why I created Mvp4g, hopefully this can help.
Mvp4g, compared to gwt-presenter, has another approach concerning the event bus. Instead of using GWT HandlerManager and having to create a lot of classes for events, you have only one Java interface. Each method inside this interface will allow you to define an event and you will be able to configure handlers thanks to annotations. It's really easy to use and it also allows you to have a strongly-typed event bus. Another reason why you may want to consider Mvp4g for a big project is that it lets you control your event flow easily. The problem for a big project with GWT HandlerManager is that it can become hard to know who handles what because each presenter is responsible for registering to events (so if you want to find which presenters handle a particular event, you need to look at all the classes that call addHandler(MyEvent.Type, ...)). Mvp4g provides a centralized way to manages handlers and you can just look at one annotation to know which presenters handle the event. Mvp4g also comes with features like LazyLoading & CodeSplitting (& a debug mode to trace your event flow). Mvp4g defines only the MVP + eventbus architecture and lets you choose how you want to communicate with the server (Mvp4g can be used with gwt-dispatch). For those who are interested, a new snapshot of Mvp4g (1.2.0) that integrates GIN is now available. Mvp4g is an open-source project (licence Apache 2.0) so if you have ideas to improve it, let me know. Thanks, Pierre On Apr 7, 3:17 am, Lars Erik Karlsen <larse...@gmail.com> wrote: > Nice! > Will check it out. > > - lars > > > > PhilBeaudoin wrote: > > I'll take this opportunity to shamelessly plug my own take on the MVP > > architecture: > >http://code.google.com/p/gwt-platform/ > > > I started using gwt-presenter, but I ran into a number of problems > > with code-splitting, lazy-loading and weakly-coupled nested > > presenters. So I created GWTP, a fork of gwt-presenter with a slightly > > different architecture. It still results in simple Presenter-View > > classes, but introduces a nice annotation-based mechanism to build > > proxy classes -- the key behind lazy-loading and code-splitting. > > > I'd love to get feedback on this, if you ever have some time to look > > at the project. > > > On Mar 22, 9:50 am, Nathan Wells <nwwe...@gmail.com> wrote: > > >> Here's a copy of the current version on my blog: > > >>http://nathanwells.net/blog/?p=235 > > >> On Mar 22, 9:17 am, Simon <simon.bar...@gmail.com> wrote: > > >>> I'd love to read what you have done. Unfortunately, I do not have > >>> Google Wave yet as it is not released and I cannot follow your link... > > >>> I guess I'm not the only person in this case ! :) > > >>> Do you have a link publicly available ? > > >>> On 22 mar, 16:10, Nathan Wells <nwwe...@gmail.com> wrote: > > >>>> I've just started designing something new for client-server > >>>> communications: > > >>>>https://wave.google.com/wave/#restored:search:group%253Agoogle-web-to... > > >>>> I'd love to get feedback on the ideas I put down there. > > >>>> On Mar 21, 11:24 am, Jamie Gennis <jgen...@gmail.com> wrote: > > >>>>> I'll take this opportunity to insert a shameless plug for > >>>>> gwt-remote-action<http://code.google.com/p/gwt-remote-action/> as an > >>>>> alternative to gwt-dispatch. The idea behind gwt-remote-action is that > >>>>> it > >>>>> enables use of the command pattern using the same RPC interface as > >>>>> traditional GWT RPC. This means you don't have to build your app from > >>>>> the > >>>>> ground up with the command pattern in mind, but rather you can just use > >>>>> normal GWT RPC and then augment it later when you need caching, > >>>>> transactions, undo, or any other command pattern goodness. > > >>>>> You can also check out > >>>>> gwt-remote-action-extension<http://code.google.com/p/gwt-remote-action-extension/> > >>>>> for > >>>>> a library than enables the use of Gilead with gwt-remote-action as well > >>>>> as a > >>>>> demo app. > > >>>>> Best, > >>>>> Jamie > > >>>>> On Sun, Mar 21, 2010 at 8:35 AM, zggame <zgg...@gmail.com> wrote: > > >>>>>> I second that idea. I start to really understand thegwt-presenterby > >>>>>> reading its code. It is actually not that complicated and teach me > >>>>>> some really nice lessons. And you also see a few short-coming of it. > >>>>>> It is open-source under BSD. So you can do whatever to fit it for > >>>>>> your purpose. > > >>>>>> On Feb 28, 5:58 pm, Geraldo Lopes <geraldo...@gmail.com> wrote: > > >>>>>>> Initiatives like gwt-dispatch andgwt-presenterare welcome. > >>>>>>> Reading others code is a very good way to improve our skills. > >>>>>>> Even if one don't adopt the library it can be very helpful. > > >>>>>>> Keep small (but useful) libraries river flow :) > > >>>>>>> Regards, > > >>>>>>> Geraldo > > >>>>>>> On 28 fev, 15:40, Ed <post2edb...@hotmail.com> wrote: > > >>>>>>>> Be careful using many third party lib's which are more like hobby- > >>>>>>>> projects and will not be updated when gwt will come out with a new > >>>>>>>> version such that you can't make the switch to the new gwt > >>>>>>>> version.... > >>>>>>>> I try to do everything myself and learn from others... I already had > >>>>>>>> a > >>>>>>>> few times that I was using other frameworks and couldn't make the gwt > >>>>>>>> update when I wanted, but had to wait till all frameworks made the > >>>>>>>> switch... or didn't made the switch at all. :( > > >>>>>>>> GWT is awesome, short learning curve for simple things, and makes it > >>>>>>>> very easy to create nice things which people then want to share with > >>>>>>>> others... So they drop it in a google code project and never look > >>>>>>>> back > >>>>>>>> to it anymore.... > > >>>>>>>> Of course there are also very good lib's like smartgwt and gxt > >>>>>>>> (before: mygwt)... The latter one cost a bit, but there for future > >>>>>>>> proof and has a very nice MVC implementation with dispatcher > >>>>>>>> integration that is well suited for more complex app's and is very > >>>>>>>> lean and mean... > > >>>>>>>> Goodluck, > >>>>>>>> Ed > > >>>>>> -- > >>>>>> You received this message because you are subscribed to the Google > >>>>>> Groups > >>>>>> "Google Web Toolkit" group. > >>>>>> To post to this group, send email to > >>>>>> google-web-tool...@googlegroups.com. > >>>>>> To unsubscribe from this group, send email to > >>>>>> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2Bunsubs > >>>>>> cr...@googlegroups.com> > >>>>>> . > >>>>>> For more options, visit this group at > >>>>>>http://groups.google.com/group/google-web-toolkit?hl=en.- Hide quoted > >>>>>>text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
