1. #1
    Sencha User
    Join Date
    Feb 2013
    Location
    Russian federation, Smolensk
    Posts
    38
    Answers
    5
    Vote Rating
    0
    Mike_javaJunior is on a distinguished road

      0  

    Default Answered: EventType in gxt3

    Answered: EventType in gxt3


    I'm trying to change gxt in my application from 2.2 to 3.0
    as i've found EventType doesn't exist in gxt3
    how can I replace such an easy
    final EventType type = event.getType();

  2. GXT 3 is very different than GXT 2 - events are one such example. GXT 3 changed to use an event model more like how GWT events work.

    At the time GXT 2 was written, GWT didn't have the event model it has today, so GXT used its own solution. Once GWT had another solution, we decided to follow it in GXT 3 to be more consistent.

    Instead of having a BaseEvent for all events, and using EventType instances to compare, GWT has just the GwtEvent type. Subclasses then describe both their own behavior, and the kind of handler that should get called by them.

    When listening for an event, it is almost always just as simple as invoking object.addSomeEventHandler(new SomeHandler() {...}). The handler then has a specific method that is called when that particular kind of event goes off, instead of having a general handleEvent() method.


    GWT documentation on handling events:
    https://developers.google.com/web-to...uideUiHandlers

    GXT 3 migration guide:
    http://www.sencha.com/learn/sencha-g...gration-guide/

  3. #2
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,734
    Answers
    109
    Vote Rating
    90
    Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light

      1  

    Default


    GXT 3 is very different than GXT 2 - events are one such example. GXT 3 changed to use an event model more like how GWT events work.

    At the time GXT 2 was written, GWT didn't have the event model it has today, so GXT used its own solution. Once GWT had another solution, we decided to follow it in GXT 3 to be more consistent.

    Instead of having a BaseEvent for all events, and using EventType instances to compare, GWT has just the GwtEvent type. Subclasses then describe both their own behavior, and the kind of handler that should get called by them.

    When listening for an event, it is almost always just as simple as invoking object.addSomeEventHandler(new SomeHandler() {...}). The handler then has a specific method that is called when that particular kind of event goes off, instead of having a general handleEvent() method.


    GWT documentation on handling events:
    https://developers.google.com/web-to...uideUiHandlers

    GXT 3 migration guide:
    http://www.sencha.com/learn/sencha-g...gration-guide/

Thread Participants: 1