Mark,
The SerializedObject contains a circular reference because each child
has a back reference to the parent. So, parent-childrenList-item0-
parent. The code for the new RPC classes appears to serialize
recursively without accounting for circular references (the existing
RemoteService RPC
As Thomas Boyer said, there is no way to answer the question of which
is better performance wise. Assuming serialization technologies are
equivalent for both performance and message size, all other
performance costs (e.g., latency, throughput) depend on the server
environment, including the
);
}
);
}
public class MyPresenter implement MyView.Listener {
public interface View {
}
public void onEdit(String id){
// Do something here.
};
}
Please correct me if i am following the wrong way.
Thanks.
On Sep 7, 8:32 am, Jason A. Beranek
One approach I've used is to put some logic in the View to forward a
different event than the purely GUI events to the Presenter. For
example, if you have a table or list of items which can be clicked,
and a click signifies selection of an item, use HasSelectionHandlers()
in the View, and
to, But I
do get the feeling I'm stretching the MVP pattern well out of shape in order
to get it all to work.
Ian
http://examples.roughian.com
2009/9/3 Jason A. Beranek jason.bera...@gmail.com
Ian,
When you mention your current solution fetches the MenuItem view from
the MenuPanel view
Ian,
When you mention your current solution fetches the MenuItem view from
the MenuPanel view, do you mean the MenuItem view(s) are already in
the MenuPanel view or do you mean the MenuPanel view acts as a factory
for MenuItem views? I have been experimenting a bit with the former,
though I
I've run some quick tests on one approach to incorporating UiBinder,
the MVP design pattern, and child view's. Most of the approaches I've
seen in the group have focused on how to add the child View to the
parent View after construction. But, another approach is to return the
child View from the
On Jul 22, 3:51 am, Thomas Broyer t.bro...@gmail.com wrote:
They're IMO as easy to parse
as path-like tokens like Gmail uses; it's just a matter of taste
(and how you'd like to model your internal API)
Agree that the implementation depends on the model for an applications
internal API. Part
On Jul 22, 6:59 am, Daniel Wellman etl...@gmail.com wrote:
So it seems it's a tradeoff in how much test coverage you need --
expose the low-level HasXyz interfaces in your view if you need more
automated test code coverage, or use a gateway interface to the view
which exposes higher-level
I've been looking at the place service as well, but while I don't
agree with exactly the structure in David Peterson's example, I'm not
sure if the place service should fire an IssueEditEvent that drives
some UI change. From the Ray Ryan presentation, my impression is the
Place Service functions
David,
The Apache Shindig project (reference implementation of OpenSocial)
provides another approach for registering ActionHandlers. The Shindig
OpenSocial API code uses a HandlerDispatcher to dispatch Action
handling (as opposed to using the Servlet to do this directly). For
application
source locations, the approach for the most part still
stands (the code is just built with more complex dependency
injection).
Respectfully,
Jason
On Jul 4, 7:42 am, Jason A. Beranek jason.bera...@gmail.com wrote:
David,
The Apache Shindig project (reference implementation of OpenSocial
I've struggled with the go(RootPanel.get()) function as well, but
discounted the idea of casting my Presenter.Display interface to a
Widget as it removes an amount of type safety from the presenter and
somewhat defeats the purpose of having a nice generic Display
interface for the Presenter to
Ed,
I may be missing something from the original presentation, but your
description of a limited number of Controllers interacting with your
event bus seems identical in principle to a limited number of
presenters interacting with the event bus (as in Ray Ryan's talk).
Your limit on the number
14 matches
Mail list logo
