Event naming

[Francois Wauquier]

Hello, group memers

Since GWT 1.6, the gwt-mvc Event name is confusing.
http://gwt-mvc.googlecode.com/svn/trunk/gwt-mvc/javadoc/0.2/com/googlecode/gwtmvc/client/Event.html
So i propose you to participate to a little naming session to choose
the future name.
(Event will be preserved as deprecated at first to facilitate
migrations)

So i give you a list, and you just have to pick one and post an answer
with it.
You could also propose an other one.

Action
ActionEvent
UserAction
UserEvent
UserActionEvent
MvcEvent
ViewEvent
ViewAction

Let's go

[Guillaume FELIX]

Hi everybody !

I vote for "MvcEvent". It is still an Event and it represent the mean of communication in the MVC pattern.

The "Action" term is too close to the Struts framework. Can be confusing.
The "View" term is too restrictive, indeed we can have a controller send a message to another controller without passing by the view.
In the same way the "User" term is restrictive...

That's my way of thinking.

Have a nice day.

Guillaume

2009/7/24 Francois Wauquier <wok...@gmail.com>

[LuDo]

I think it's possible to extend the new GwtEvent & Handlers design
appeared in 1.6 creating GwtMvcEvent (extends GwtEvent<?>) class and
GwtMvcEventHandler interface (extends EventHandler).

An example of personnal extension of Gwt Event system is given here :
http://phiz.posterous.com/loose-coupling-in-client-side-web-apps-with-g

Ludo

On Jul 24, 12:17 pm, Guillaume FELIX <feli...@sfeir.com> wrote:
> Hi everybody !
>

> I vote for "*MvcEvent*". It is still an Event and it represent the mean of

> communication in the MVC pattern.
>
> The "Action" term is too close to the Struts framework. Can be confusing.
> The "View" term is too restrictive, indeed we can have a controller send a
> message to another controller without passing by the view.
> In the same way the "User" term is restrictive...
>
> That's my way of thinking.
>
> Have a nice day.
>
> Guillaume
>
> 2009/7/24 Francois Wauquier <wok...@gmail.com>
>
>
>
>
>
> > Hello, group memers
>
> > Since GWT 1.6, the gwt-mvc Event name is confusing.
>

> >http://gwt-mvc.googlecode.com/svn/trunk/gwt-mvc/javadoc/0.2/com/googl...

[Francois Wauquier]

An adaptation of gwt-mvc to get closer to the gwt Event Handler is
planned, but not for the moment.
http://code.google.com/p/gwt-mvc/wiki/Roadmap

However, about this 'survey', I count +1 for GwtMvcEvent for LuDo

[Peter Kielczewski]

"MvcEvent" sounds also BEST to me !

2009/7/24 Francois Wauquier <wok...@gmail.com>

[Francois Wauquier]

I personnaly have a preference for UserEvent, because it insist on the
oposition with BrowserEvent.

About the Guillaume Felix note about controllers calling other
controller, i think that append because the framework was not fully
'hierarchical'
It was only for browser event, not for (User)Event.
It is Guillaume that made me realized that.

for the 'view' prefix, it insists on the source of the event.

so... i vote for UserEvent.

(survey is open today and tomorrow)

[Francois Wauquier]

MvcEvent is the winner.