I've been mockng the views for testing and injecting for integrating.
Easymock and mockito do most of what I need. I've also been creating
concrete Has... Mock classes as needed.
I'm also still feelling things out.
On Oct 4, 5:49 pm, Chris wrote:
> Don't you just inject a Mock Panel in that
Don't you just inject a Mock Panel in that case? (Sorry rather new)
On Oct 4, 11:08 pm, Dave Pinn wrote:
> What is your alternative, Miroslav?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" gro
What is your alternative, Miroslav?
--~--~-~--~~~---~--~~
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-toolkit@googlegroups.com
To unsubscribe from this group,
Hello,
How you test the following snippet ?
The following snippet is not following the Law of Demeter and I'm not
sure that such usage is correct, because in your test if have to mock
the display, the MyReusablePanel and the Display of MyReusablePanel.
Regards,
Miroslav
Dave Pinn wrote
You would typically have one presenter and one view for each discrete
part of the page. The idea is to componentise the parts of the page so
that they can be re-used in a variety of contexts; for example: you
might have a page navigation sub-panel that gets used on several
pages.
To re-use your p
Hi
I'm new to whole lot (GWT, MVP, Dependency Injection, etc.) but my mind is
coming round to the idea.
At the risk of sounding like a total ignorant, do View incorporate other
Views?
Or would you for example build your custom panels to ensure that you only
have one view with lots of bits on it?
