There is also the Expenses example which in GWT 2.1M2 has been
separated from the rest (Places, Activities, Presentation Widgets).
http://code.google.com/p/google-web-toolkit/source/browse/#svn/trunk/bikeshed/src/com/google/gwt/sample/expenses
I just started putting together some tutorial myself
In M2, things have been cleaned up a bit. The framework has been moved
out of bikeshed into "user" folder, thus promoted into gwt.jar and out
of bikeshed.jar file (Bikeshed contains only the example apps now). If
you're using Roo, you have to fix the POM manually or wait for Roo M2
to be released (
Hi all.
While GWT team is clearly working hard to promote 2.1 to more mature
releases, some documentation would had been of help in evaluating the
impact of the new design (MVP, Activity, cell-based components) on
existing projects. While experimenting with GWT's recent branches, I
decided to writ
Hi.
You might also want to keep an eye on the recent GWT 2.1 development
(still at milestone maturity level) on MVP, as described in this video
at Google IO 2010:
http://www.youtube.com/watch?v=M5x6E6ze1x8
Instead of AppController, Presenter and Displays you would have
ActivityManager, Activitie
Thanks to everybody for sharing your opinion.
I think there is a way to keep your project code and roo code side-by-
side, as roo tries to keep the separation as tidy as possible through
AspectJ, secluded packages, etc.
I am not yet convinced, though, that keeping roo inside your project
is necess
I've been giving a closer look at GWT 2.1.0 M1 and Expense application
lately, as the best way to be educated after Google I/O 2010 sessions.
In your opinion, how long a real-world application shall be coupled
with Spring Roo infrastructure/annotations?
It's obvious that the default views generate
