GWT is a very powerful framework that allows you to build efficient applications, especially if you follow the best practices described by Ray Ryan at Google IO 2009:

(see for the video or for the text, thanks to Araik Minosian.) However, following these best practices is not always easy and you can end up with a project with a lot of boilerplate code that is hard to manage.

That's why Mvp4g offers a solution to following these best practices using simple mechanisms that only need a few lines of code and a few annotations.

This is all you need to create an event bus with four events:

@Events(startPresenter = CompanyListPresenter.class, module = CompanyModule.class) 
public interface CompanyEventBus extends EventBus {          
        @Event( handlers = CompanyEditPresenter.class )        
        public void goToEdit( CompanyBean company );          

        @Event( handlers = CompanyDisplayPresenter.class )         
        public void goToDisplay( CompanyBean company );          

        @Event( handlers = { CompanyListPresenter.class, CompanyDisplayPresenter.class } )         
        public void companyCreated( CompanyBean newBean );          

        @Event( handlers = CompanyListPresenter.class )         
        public void companyDeleted( CompanyBean newBean ); 



History Management/Place Service:

Not only does Mvp4g help you follow the best practices, it also provides mechanisms to build fast applications:

To understand how the framework works, you can look at the documentation, the tutorials or the examples.

Mvp4g has been successfully used on several commercial projects, take a look at a few of them. You can also read and post feedback on the official GWT marketplace or Mvp4g forum.

Any comments or ideas to improve the framework are more than welcome. If you want to help us to improve and contribute to this project, feel free to do so.

To ensure quality, library code is covered by JUnit tests.


Mvp4g uses heavily generators. Also it has a dependency to GIN, which is at least end of life. That are some of the reasons why mvp4g will never work with j2cl/GWT 3!

Of course mvp4g will be maintained in the future. Bugs will be fixed, etc. But, you will not see any no features, etc.

If you are planning to update your project and make it j2cl ready, you have two opportunities:

  1. switch to mvp4g2
  2. switch to Nalu

Both frameworks have been tested with j2cl!

In case you are uncertain, which one of the frameworks to choose, ask inside the Nalu Gitter room.