On 12/2/2011 8:16 PM, Barry Books wrote:
GWT, Tapestry and jQuery are the only web development frameworks I use now.
I really like GWT but I don't use it on public sites. I'm certain that
you can it just requires more testing effort like what happens when it
runs on an IPhone. Even when I use GWT I have a Tapestry backend
because I usually have several GWT applications with some basic HTML
support pages (especially admin pages). I've done a few sensor
monitoring applications and I use GWT and Google Visualizations for
them.
Speaking of back-end, is you back-end loosely-coupled with the
front-end, I mean, is it something like a "service", I am planning to
migrate my full-blown GWT app, with services: connect, disconnect,
createAccount, etc. all connecting to another server. However, I haven't
actually worked with "services" with Tapestry.
When I do Tapestry work I head down the progressive enhancement route.
I build Tapestry components to render basic HTML then I create jQuery
mixins (widgets) and add them to the basic components to create things
like a tabbed interface. Now that I use the tapestry5-jquery module I
find myself using less GWT because I think Tapestry/jQuery development
is faster and easier. BeanEditForm is your friend. If you are careful
it's pretty easy to build and app that runs on anything.
I don't know much about BeanEditForm, is it customizable, I mean, when I
did the tutorial, the edit form is wrapped with a yellow box? I mean,
when I do things in GWT, a registration form is made up of a panel with
input textbox widgets on it and some button like ok and cancel. I also
included a ReCaptcha widget ;-)
I am not sure if this is "easily" achievable with Tapestry just like
with GWT.
In any case, I just want to keep the loose-coupling that I have with my
GWT app when migrating to tapestry, that is the client side code and the
server side code is separate. Or, tapestry does not work that way?
So I'd say jump right in. Worst case you'll end up using both they are
made for each other and you can impress your friends by using the
Eclipse debugger to single step from the client to server and back all
in Java.
Yah, I still have use with GWT, especially with web apps that are like
desktop app. I mean, like those enterprise apps which can easily live in
single-page app. However, for something that is multipage and works like
most web sites, I guess I will use T5
I haven't use Eclipse debugger for "client to server", can you share
some insights?
FYI: The trsvax-gmt module is mine but I have not worked on it in a
while. It allows you to use GWT components just like Tapestry
components and you can call Tapestry event handlers from GWT.
Yah, I tried the demo, I guess it was trsvax-gmt. However, using less
GWT is more preferable with Tapestry, Tapestry/jquery might be better.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Cheers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
