Hi, Everyone
I start to work on my app which has requirement to have some kind of
action buffer in the client side. All the actions will push to this
buffer and make request to server every 2 or 3 seconds. Basically it
is doing batching. So it should be a good use case to use command
pattern to a
> One question though:
>
> "The first line creates a Java class thanks to the configuration file
> and a Generator."
> "For example, with the following configuration file:"
>
> How is that class generated from the configuration file? (Sorry to ask
> if it's obvious.)
> Will the argument of the gen
I'm really much interested into that project. I've been studying MVP
since I saw the famous Google IO video on the subject. I read talks
about it in many places, but nothing solid still, nor any good
tutorial explaining the topic in a clear way (all abstract and good-
practice theories). Since I h
Hi,
I created a framework, Mvp4g, to easily build gwt application using
Mvp + event bus + DI thanks to an xml file.
A new version is now available (mvp4g-0.13-beta). You can:
-Set an event bus without creating extra classes.
-Configure which presenter handles an event.
-Inject a view and one to
I already ported my app to use gwt-presenter. So far it really work out :)
Bye,
Norman
2009/7/20 Eduardo Nunes :
>
> For everyone following this thread, I would recommend to take a look
> in the presenter's implementation created by David
> http://gwt-presenter.googlecode.com
>
> I'm taking a lo
For everyone following this thread, I would recommend to take a look
in the presenter's implementation created by David
http://gwt-presenter.googlecode.com
I'm taking a look on it too, and it seems to be very interesting. I
will port my little application as a proof concept. As soon as
possible I
On 13 juil, 11:18, Kwhit wrote:
> I'm following your work with interest Eduardo, I'm in the process of
> building a 'dream-team reference application' myself including RPC,
> EasyMock, GIN, Guice, ... so I can unit test and hack end-to-end
> without deploying on a server.
>
> Here's question / c
On Mon, Jul 13, 2009 at 6:18 AM, Kwhit wrote:
>
> I'm following your work with interest Eduardo, I'm in the process of
> building a 'dream-team reference application' myself including RPC,
> EasyMock, GIN, Guice, ... so I can unit test and hack end-to-end
> without deploying on a server.
>
Good, m
Hi:
Talking about a dream-team, has any one start to work on JSONP request
and REST response to completely separate client and server services with
Command pattern at client side and workflow at server side?
BaTien
DBGROUPS and BudhNet
On Mon, 2009-07-13 at 02:18 -0700, Kwhit wrote:
> I'm follo
I'm following your work with interest Eduardo, I'm in the process of
building a 'dream-team reference application' myself including RPC,
EasyMock, GIN, Guice, ... so I can unit test and hack end-to-end
without deploying on a server.
Here's question / comment...
I don't understand the go() method
Hi Mr. Broyer,
I've updated gwt-mvp-sample following your tips. Do you have any other tip?
Thanks at all and I hope it could help someone. If someone else have
any other tip or want to discuss about it, please just reply this
e-mail.
Best Regards
On Fri, Jul 10, 2009 at 12:11 PM, Thomas Br
Exactly the same, only your implement your service yourself, instead
of relying on the GWTrpc.
You should end up with something similar to (assuming "traditional"
RPC, not the command patten displayed in the Google-IO video):
interface MyService {
void myMethod(..., AsyncCallback);
}
class MySe
How does this architecture work if I do not have RPC calls? Instead,
mostly I use RequestBuilder to make REST service calls and update/
change View depends on onError or onRespondeReceived callback.
Thanks,
On Jul 10, 11:11 am, Thomas Broyer wrote:
> On 10 juil, 15:15, Eduardo Nunes wrote:
>
>
On 10 juil, 15:15, Eduardo Nunes wrote:
> On Fri, Jul 10, 2009 at 7:10 AM, Thomas Broyer wrote:
>
>
> > I wouldn't have used an addClickHandler on the View, but rather a
> > "HasClickHandlers getAddIssueButton()". Also, I would have named the
> > EditIssuePresenter method showIssue(Issue issue)
On Fri, Jul 10, 2009 at 7:10 AM, Thomas Broyer wrote:
>
>
>
> On 10 juil, 08:40, Gert wrote:
>> On Jul 10, 12:47 am, Eduardo Nunes wrote:
>>
>> > Hello guys,
>>
>> > I had a little difficulty to define how establish a communication
>> > between the Presenters. When you deal with just one Present
On 10 juil, 08:40, Gert wrote:
> On Jul 10, 12:47 am, Eduardo Nunes wrote:
>
> > Hello guys,
>
> > I had a little difficulty to define how establish a communication
> > between the Presenters. When you deal with just one Presenter, the MVP
> > pattern is very simple to understand. After a whil
On Jul 10, 12:47 am, Eduardo Nunes wrote:
> Hello guys,
>
> I had a little difficulty to define how establish a communication
> between the Presenters. When you deal with just one Presenter, the MVP
> pattern is very simple to understand. After a while I found my
> solution and I decided to share
Hello guys,
I had a little difficulty to define how establish a communication
between the Presenters. When you deal with just one Presenter, the MVP
pattern is very simple to understand. After a while I found my
solution and I decided to share it with you all. I created a simple
application that
The HandlerManager is indeed new in GWT 1.6, that might be why. If you
wrap your own you can always add new functionality, that might also be
why. Thanks for the link to the MVZ project, it'll be good to see some
example implementations of the concepts.
--
Arthur Kalmenson
On Thu, Jul 2, 2009
Thanks Thomas!
I feel like my spaghetti-in-a-bowl code is slowly becoming
spaghetti-in-a-box. ;-)
I found what appears to be a nice sized app that uses
MVP+Eventbus+IOC+Command Patterned RPC+Place all in one spot. It looks to
be property of berkeley.edu. It also uses AppEngine if that floats yo
On 2 juil, 02:56, Daniel Jue wrote:
> (BTW- Thanks for the corrections on my previous email.)
>
> I'm looking on slide 47, with this code:
>
> public void execute(final UpdateContact update,
> final AsyncCallback cb) {
> realService.execute(update, new
> AsyncCallback()
(BTW- Thanks for the corrections on my previous email.)
I'm looking on slide 47, with this code:
public void execute(final UpdateContact update,
final AsyncCallback cb) {
realService.execute(update, new
AsyncCallback() {
public void onFailure(Throwable caught)
I'm only making guesses here as well... but perhaps either:
interface Display {
HasFocusHandlers getEntryFocus();
HasBlurHandlers getEntryBlur();
}
or something like:
interface FocusableTextEntry extends HasValue,
HasFocusHandlers, HasBlurHandlers {}
interface Display {
FocusableTe
Using of
http://google-web-toolkit.googlecode.com/svn/javadoc/1.6/com/google/gwt/user/client/ui/HasWidgets.htmlis
a better idea. If HasWidgets interface is used then you can use the
presenter in a simple unit test without the extension of GWTTestCase cause
the Widget is provided to the HasWidgets's
So if for a TextBox I need to bind both FocusHandler and BlurHandler,
I need to have two interfaces and combine them?
How does that work?
On Jun 30, 6:54 am, gscholt wrote:
> On Jun 29, 11:13 pm, Daniel Jue wrote:
>
>
>
>
>
> > Does anyone have a working MVP/Eventbus sample of something simple
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 int
On Jun 29, 11:13 pm, Daniel Jue wrote:
> Does anyone have a working MVP/Eventbus sample of something simple
> like the PhoneEditor?
> I don't think I'm doing it right. The code from the IO presentation
> leaves out enough details so that I'm not sure what to do.
> For instance, in my Presenter.c
In my Display interface, I included a method like
Widget getWidgetView();
which (interestingly enough) returns a widget view of the display
object. this eliminates your casting problem, while still maintaining
a degree of anonymity for the Display interface.
On the command pattern thing, I crea
On 29 juin, 23:13, Daniel Jue wrote:
> Does anyone have a working MVP/Eventbus sample of something simple
> like the PhoneEditor?
> I don't think I'm doing it right. The code from the IO presentation
> leaves out enough details so that I'm not sure what to do.
> For instance, in my Presenter.c
check this out:
http://www.webspin.be/
I left out the model (Phone class here) and the command pattern, since
I'm not using it yet.
For your comment on the casting: I'm having trouble with that too.
When I want to attach the widgets to the root panel or whatever other
panel, I can't do anything
Does anyone have a working MVP/Eventbus sample of something simple
like the PhoneEditor?
I don't think I'm doing it right. The code from the IO presentation
leaves out enough details so that I'm not sure what to do.
For instance, in my Presenter.class,
I have something like this:
public class Pr
May i know will the sample app(using MVP + command pattern+ EventBus)
for the talk will be uploaded any sooner? I think many are asking the
same questions.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google Web
Now I look at this, I realize that for this example, the phoneEditor
is a pop-up.
But the case is still valid in general terms.
The widget implements a widgetInterface, and to bind that widget to
the rootpanel, a cast is necessary in the go() function. How do I
avoid the cast or if I don't, is thi
I'm having trouble with one other thing in that presentation.
In the end of the MVP part, Ray concludes with
contactViewer.go(RootPanel.get());
But, since phoneEditor is a presenter, and display a interface, to
bind the widget to the rootpanel one needs to cast it:
rootPanel.add((Widget)phoneEdi
He Jason,
Yep, you are right, it's just with my MVC setup you can't just
subscribe to the bus in with a global event handler you can.
For me, it would be ur second option as the Windows.Close event is way
to course grain for me as the application is too complex and there
happens too much for a l
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 of
I am currious what whould be the performance impact of removing
listeners in the onUnload method instead of leaving them there
(assuming we don't create memory leaks).
I mean: in my case I have a left menu that shows screens on the right
side. These screens are a bit complex and contains much logi
On Jun 20, 1:33 am, Ian Petersen wrote:
> > My (limited) understanding of what Ray Ryan was saying (and what I
> > understand of MVP) is that the presenter is completely separated from the
> > DOM elements (in order to facilitate testing, and because the view is solely
> > responsible for the vie
As I myself didn't understand it completely either, I build a little
testapp for it.
And it was at the same time, my first blog post :)
check it out:
http://www.webspin.be/2009/06/learning-gwt-managing-events-with-eventbus/
On 20 jun, 00:21, Ian Bambury wrote:
> The PhoneEditor doesn't need the
The PhoneEditor doesn't need the event bus since it doesn't respond to any
events.
The ContactWidget needs the event bus in case the details change in real
time, then it can update itself.
If you (the user) want to change the phone number while you are looking at
the contact details (the ContactWi
Finally found a thread talking about this presentation. It is very
interesting for me as well.
Thomas, you mentioned slide #73, actually I have some question about
this. In this slide, from my point of view, both PhoneEditWidget and
ContactWidget are just Views in MVP. Phone Editor is Presenter i
On Thu, Jun 18, 2009 at 5:38 PM, Ian Bambury wrote:
> 2009/6/19 Ian Petersen
>>
>> On Thu, Jun 18, 2009 at 3:56 PM, Ian Bambury wrote:
>> > 2009/6/18 Thomas Broyer
>> >> Whether the eventbus has a reference to the widget is
>> >> orthogonal.
>> >
>> > I didn't realise that widgets were bird-watc
On 19 juin, 00:56, Ian Bambury wrote:
> 2009/6/18 Thomas Broyer
>
> That was my point, really, that there is no method you can just shove the
> unsubscribe into and have it just happen. You have to create one (calling it
> what you will, unload(), teardown(), destroy(), etc) and hope the develo
2009/6/19 Ian Petersen
>
> On Thu, Jun 18, 2009 at 3:56 PM, Ian Bambury wrote:
> > 2009/6/18 Thomas Broyer
> >> Whether the eventbus has a reference to the widget is
> >> orthogonal.
> >
> > I didn't realise that widgets were bird-watchers! :-)
>
> Do you mean ornithologists?
Aren't they eye-d
On Thu, Jun 18, 2009 at 3:56 PM, Ian Bambury wrote:
> 2009/6/18 Thomas Broyer
>> This I don't understand, onUnload is called by the parent widget
>> (through onDetach) when you remove its child (and it thus is detached
>> from the DOM). Whether the eventbus has a reference to the widget is
>> ort
2009/6/18 Thomas Broyer
>
>
>
> On 18 juin, 18:01, Ian Bambury < ianbamb...@gmail.com> wrote:
> > 2009/6/12 Thomas Broyer
> >
> > > As with any event, I'd subscribe in the onLoad and unsubscribe in the
> > > onUnload (would be even better if there was a destructor, so that even
> > > when not at
On 18 juin, 18:01, Ian Bambury wrote:
> 2009/6/12 Thomas Broyer
>
> > > 1- What is missing here is when would the Client UI typically
> > > subscribe/unsubscribe from the event bus. If this were a desktop
> > > application I would simply use weak reference so I would not have to
> > > unsubsc
2009/6/12 Thomas Broyer
>
> > 1- What is missing here is when would the Client UI typically
> > subscribe/unsubscribe from the event bus. If this were a desktop
> > application I would simply use weak reference so I would not have to
> > unsubscribe my UI manually to prevent a memory leak.
>
> A
On 17 juin, 14:08, "cristian.vrabie"
wrote:
> EventBus(es) work incredible well. I got the chance to test the
> pattern in a GWT 1.5 app and it proved to be "magical" :) However,
> using a GWT 1.6 handler manager as a application wide event bus, as it
> is stated at Google I/O 2009, seems to ha
EventBus(es) work incredible well. I got the chance to test the
pattern in a GWT 1.5 app and it proved to be "magical" :) However,
using a GWT 1.6 handler manager as a application wide event bus, as it
is stated at Google I/O 2009, seems to have some limitations. One of
the biggest I could spot is
Hi Benju,
The use of the HasClickHandlers interface (and other Handler interfaces) is
actually just a piece of event-driven architecture that GWT subscribes to
in the 1.6 event handler architecture. Basically, anything that implements
the HasClickHandlers interface must provide an implementation f
Thanks for the reply I have some further thoughts...
Looking at the source code for the event handling in GWT 1.6 it seems
the fundamental difference is as follows...
Old way with listeners
"I am adding this event listener to this component, when the listener
is triggered I know the source must
On 11 juin, 21:34, Benju wrote:
> I did not attend Google I/O but as soon as the video "Google I/O 2009
> - Best Practices for Architecting GWT App" (http://www.youtube.com/
> watch?v=PDuhR18-EdM) was posted I reviewed it and was a bit confused
> by the idea of an EventBus.
For my part, I was p
53 matches
Mail list logo
