What is the best way to implement that ?
1) only one couple of presenter/view for object1 and this couple
manages the display of object2 in each tab
2) one presenter/view object for object1 and one presenter/view for
each instance of object2 ?
in other words, do I have one couple of presenter/view by object
model ?
Group items tagged
Client session - Google Web Toolkit | Google Groups - 0 views
-
The way I would do is to define a application event (eg. LocationEvent<LocationHandler>) & handler encapsulating whatever data (ex. co ordinates) that you need to send and fire the event. First presenter fires the event when the mouse is clicked. Second Presenter handles the event and takes appropriate action.
One v.s N EventBus - Google Web Toolkit | Google Groups - 2 views
-
My application has several modules, and in each module, it may have different layout. Hence I have multiple level of Activity and in each module, I have an ActivityManager and ActivityMapper to create an appropriate Activity according to the Place or return null if not interested. All the ActivityManagers are attached to a global Event bus.
Menu Item and MVP (2) - Google Web Toolkit | Google Groups - 0 views
-
>> Would the MenuItem class need to implement HasClickHandler so that >> when a MenuItem is clicked, the action can be handled in the >> presenter. At this time, the MenuItem needs an object that implements >> the Command interface, so the view seems to know about the presenter. >> I would like to know what others think about this.
Share user input data within MVP + Lady_Gaga - Google Web Toolkit | Google Groups - 0 views
-
use the history and pass the information as parameters in the history token.
-
has a number of advantages provided the parameter is serializable (and small enough). For example, it could let the user bookmark the detail page of "Lady_Gaga". A bit trickier when the presenter is a dialog box, but totally doable.
Sanjiv Jivan's Blog - 0 views
-
Once a DataSource has been defined to describe your entity / domain class, data can be read into a DataSource from a wide variety of sources. For example local array data, XML or JSON, data from the server, or you can even point to sample test data. The DataSource has a build-in mechanism to communicate with the source of the data, whether local or the backend server, for the four key operations : FETCH, ADD, UPDATE and REMOVE.
« First
‹ Previous
121 - 140 of 191
Next ›
Last »
Showing 20▼ items per page