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.
Regards
Prashant
On 16-07-2010 03:41, munna kaka wrote:
You wrote that
On Thu, Jul 15, 2010 at 11:36 AM, Feldman, Nir (48Upper)
<[email protected] <mailto:[email protected]>> wrote:
Sharing of data is threw the bus. You should have your display
expose mouseClickedEvent. The presenter should capture it and fire
it to the bus.
The secondPresenter should get the event and notify the second
display on whatever required.
Plz let me know that how first presenter can send data (say user
clicked item id in first display or any data) to second presenter?
Above is the question, I really need answer..thanks in advance...
-----Original Message-----
From: [email protected]
<mailto:[email protected]>
[mailto:[email protected]
<mailto:[email protected]>] On Behalf Of Stefan
Bachert
Sent: Thursday, July 15, 2010 6:02 PM
To: Google Web Toolkit
Subject: Re: Client session
Hi,
I am not sure what you mean with client side sessions?
Do you mean to pass the HttpSession (maybe just the id) to the client
side?
But for what reason? It is already there. Either due to url-rewriting
or by cookie.
Stefan Bachert
http://gwtworld.de <http://gwtworld.de/>
On 9 Jul., 19:48, mk <[email protected]
<mailto:[email protected]>> wrote:
> How to implement a client side session ( and any best practices to
> implement them).
> Is it to just create a static variable ?
>
> How do two different MVP widgets share MODEL data (i.e. user input
> data).
>
> How do two different MVP widgets share VIEW data ( for example if
> display of one widget is dependent on mouse click location of second
> widget, than how do two widgets share view information i.e. mouse
> click location).
>
> Again, all widgets are designed using MVP and send events using
> EventBus.
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:google-web-toolkit%[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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:google-web-toolkit%[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.
--
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.
