if i may add my 2 cents, i think that Places-Activities-Framework(PAF? anyone? , each time somebody adds another component, and it's beginning to be absurd, so why not go for PAF :) ). should NOT be considred as an MVP framework, nor should be considered as history handling one. for example our CTO declared there where will NO back button functionality thus no history to be managed (advocating that "regular" I.T apps do not have back button as well), however i'm still promoting it's use not as MVP or history but as a FLOW framework, allowing me to clearly define points of interests in regards to WHERE should a user go and WHAT a user can do when he gets there, something similar to webflow i would think. is see nothing in GWT that currently supports that. where as the presenter is concerned i found it cumbersome, why would i restrict to redefine an inner class with rigid interfaces only to separate myself from other parts, all i REALLY wanna do is to send messages from the view to what ever is using it. using Custom events (but with an abstract Event pattern i wrote here earlier) i avoid the boiler plate coding that comes with and earn a much more flexible interface between layers.
On Sun, Jul 3, 2011 at 6:56 PM, ungarida <[email protected]> wrote: > I open the project > http://code.google.com/p/gwt-meeting-room/ > > -- > 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. > > -- 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.
