The increased complexity is definitely an issue. I don't like the idea of yet more interfaces to have to worry about. It's a shame that part 2 of the MVP article doesn't address testing beyond simply mentioning that these practices improve testability. It would be much clearer to see before-and-after code highlighting the code that we want to be testable in both cases. Without that, it's hard to convince someone that the extra complexity is worthwhile.
I'm currently working on a small application using UiBinder (and hopefully GIN) without MVP. It's giving me a refreshing perspective on how fluent GWT can be, and I think the people I work with will appreciate that. However, it's not going to be any more testable than any other web technology we've used. >From there, I'm going to go about refactoring the code to make it more testable. This will probably involve applying MVP-like patterns, but I'm going to try to apply patterns that make sense and not be too biased by existing examples. I may end up with something much like what the GWT team is suggesting, or I may find some middle ground, but I should at least have a good feel for what I'm getting in return for the increased complexity. -Brian On May 11, 1:24 am, dayre <[email protected]> wrote: > I could comprehend part I after watching Ray's presentation and > reading it a few times... it gave me a much better idea on how to > structure my application, but part II things started to fall apart for > me. It was very difficult to keep track of the additional layers of > abstraction introduced and the reasons for them + introducing UIBinder > and it's details, and shifting interfaces around from where they were > in part 1 made me dizzy. The author says it was a lot to cover at > one point and it was definitely "lost in translation" for me. > > On Apr 25, 6:25 am, dmen <[email protected]> wrote: > > > I've read it and IMHO it suffers from extreme over-compexity. Problem > > is people will take this article as a reference for their designs. > > > -- > > 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 > > athttp://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 > athttp://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.
