Hello Daniel,
thanks for sharing! Your very neat diagram inspired me to rework the
layout and clarify some things in my own depiction.
About your generator framework: Isn't that what Spring Roo is all
about? - I have to admit, I am no real fan of generator solutions.
Often they are only good for bootstrapping or they break, if you stray
from the default (read expected) path of the underlying framework.
Best regards,
Achim.
On 18 Okt., 17:38, Daniel Dietrich cafeb...@googlemail.com wrote:
Hi Hans-Joachim,
as Jens mentioned, you find my post here:http://goo.gl/a6db2
Here is a direct link to the drawing:http://goo.gl/u7Ntq
The activity places vs. mvp question arises on and on.
What gwt gives to us is a toolkit - but not a framework.
There are lot of frameworks out there which give us a solution for making
our apps testable or add browser history support.
Currently I'm working on a generator which automagically generates all the
technical boilerplate code on base of a simple description of the
application to have this architecture out of the box. I see me as engineer
who creates a factory for developers. Each developer should not concern
about how to apply architectural design patterns. A developer should
implement business logic, not technical boilerplate.
I started an example generator for JPA + Request Factory
here:https://github.com/danieldietrich/xtext-javatools(running but work in
progress)
It needs this plugin to be
installed:https://github.com/danieldietrich/xtext-protectedregions
See the README.textile files for more information...
Next step is a generator for the ui stuff...
Greetz
Daniel
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.