About the gwt-presenter library, I found some points that I would like talk to you: - When I extend WidgetPresenter/BasicPresenter I have to implement many abstract methods, is it really necessary to set those methods as abstract? Isn't it better to provide an empty default implementation? I know that I can do it by myself but it's just a suggestion. - Isn't it better to define the Place mechanism in the BasicPresenter checking if the current object is a instanceof SomePlaceInterface instead of calling directly getPlace? - I didn't realize the meaning of the startProcessing and stopProcessing methods in Display interface. Can you gimme some usage example?
That's my 5cents, I think I will change my project to use your library and keep it online just as an usage example. If you want to take a look on it: http://code.google.com/p/gwt-mvp-sample/source/browse/#svn/branches/gwt-presenter Best regards, On Sat, Jul 18, 2009 at 11:32 PM, David Peterson<[email protected]> wrote: > > I really think it's a purely philosophical decision - I can see how it > would work fine with EventBus, I'm just choosing not to, basically. > For me the line in the sand is that events are about information, > commands are about action. Your mileage may vary :) > > David > > On Jul 18, 7:22 am, Kwhit <[email protected]> wrote: >> On Jul 15, 9:36 pm, David Peterson <[email protected]> wrote: >> - Thinking further, I think it's better to separate the EventBus from >> - the Command system somewhat. The reason being that generally, events >> - are used to update on changes that have already happened, or are >> about >> - to happen. They don't trigger the actual event itself. >> >> Yes I've been thinking about that. >> >> Any user action that interacts with the server: sign in, create >> account, update address, etc., has an asynchronous response. I find >> myself tempted to wrap the service request in and make it synchronous >> but that would be morally wrong and lead into all kinds of >> difficulties in the details. So I've gone the other route... >> >> My proof of concept implementation treats a click on the 'sign in' >> button as an event which it fires and forgets to the event bug. Maybe >> this goes too far in the other direction - time will tell. I'll post >> my results as soon as I've got some real experience with it. > > > -- Eduardo S. Nunes http://e-nunes.com.br --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
