GWT 2.1

[Francois Wauquier]

I just had a look at http://code.google.com/intl/fr-FR/webtoolkit/doc/latest/ReleaseNotes.html

There is a proposition for a MVP base.
Here is my first impression.

What i like:
-RequestFactory http://code.google.com/intl/fr-FR/webtoolkit/doc/trunk/DevGuideRequestFactory.html
-Place and PlaceTokenizer
http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/app/place/PlaceTokenizer.html

What i dislike:
-Many classes of the package has a warning "Experimental API: This
class is still under rapid development, and is very likely to be
deleted." http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/app/place/package-summary.html
-Due to the MVP principle, there is no unification of the view
concept. You have to define your own view interfaces.
-The naming is not consistent: it is called an MVP framework, but
there is controllers, and some concepts like Activity seems to come
from Android.
- It is not lighweigth: You must write lot of code to do simple
things.

So gwt-mvc is not dead, and i will try to integrate gwt trunk
elements, in order to continue gwt-mvc goal: make it easier to write
gwt application.

[Patrice DE SAINT STEBAN]

On Fri, Oct 15, 2010 at 10:48, Francois Wauquier <wok...@gmail.com> wrote:

I just had a look at http://code.google.com/intl/fr-FR/webtoolkit/doc/latest/ReleaseNotes.html

There is a proposition for a MVP base.
Here is my first impression.

What i like:
-RequestFactory http://code.google.com/intl/fr-FR/webtoolkit/doc/trunk/DevGuideRequestFactory.html
-Place and PlaceTokenizer
http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/app/place/PlaceTokenizer.html

What i dislike:
-Many classes of the package has a warning "Experimental API: This
class is still under rapid development, and is very likely to be
deleted." http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/app/place/package-summary.html

Theses texts has been removed :
http://code.google.com/p/google-web-toolkit/source/detail?r=9033
 

-Due to the MVP principle, there is no unification of the view
concept. You have to define your own view interfaces.
-The naming is not consistent: it is called an MVP framework, but
there is controllers, and some concepts like Activity seems to come
from Android.
- It is not lighweigth: You must write lot of code to do simple
things.

It's be we this for allow other framework to build over this implementation !

So gwt-mvc is not dead, and i will try to integrate gwt trunk
elements, in order to continue gwt-mvc goal: make it easier to write
gwt application.

The final version code has been be tagged 2.1
http://code.google.com/p/google-web-toolkit/source/detail?r=9112

--
Patrice De Saint Steban
Ingénieur Études et Développement
Direction Technique - Département Innovation et Nouvelles Technologies
Groupe SFEIR
06 74 11 63 02