2009/11/4 Thanks in Advance <[email protected]>

>
> From what I can glean Eclipse integration with GWT facilitates an
> integrated Java "back-end", thereby precluding the need for say
> ColdFusion/PHP.


Well, yes. If you have Java available on the server, then it's a good
solution - you can employ only Java programmers for example. That's got to
be a bonus.

PHP is more generally available (and is cheaper) and therefore isn't such a
bad fit since it lends itself to creating services, and if you intend to
market a software package for small businesses to host themselves. you will
probably increase your market if it can be hosted cheaply on some service
that provides PHP support (even GoDaddy does that). If you are creating a
one-off site for a largish concern, you'll be better off with Java.
Probably. Just comparing Java and PHP, that is.

CF et al will also do the job, but in my opinion are wannabe total solutions
and therefore don't feel happy just sending XML or JSON back to the client.
They can do it in the same way that you can use a 32-ton truck to deliver
pizza from a takeaway.


> Similarly this IDE promises straight forward
> deployment using Google App Engine (which with both pluses and minuses
> supplants using a relational database).


GAE hasn't settled down yet. Google don't need to use it for anything
(whereas they *are* using GWT). Apps that weren't hitting limits, suddenly
start to (though they haven't changed) because (I presume) Google are
tweaking settings.

I haven't been involved in it for a year or so (and will probably get shot
down in flames, or just flamed), but my impression back then was that it was
just being used by kids and the support groups were the blind nudging the
blind in the wrong direction. I seemed to spend a lot of time just trying to
get anyone to understand the problem, and when they eventually did, they
didn't have any answers. In the mean time, you'd get a lot of wrong answers
by people who obviously didn't have a clue. It's probably *so* much better
now.

But anyway, I would give GAE a miss until you see someone serious start
using it.


>  Additionally I have google-d and Barnes and Noble-d extensively yet I
> can't find a learning resource/tutorial referencing the latest Eclipse/
> GWT UI's (or at least how they appear on my machine) so suggestions
> would be welcomed.
>

There's some 1.7 stuff about, but 2.0 is still not even RC yet, so there's
nothing out there. But ask here, and there are a lot of good people who will
help.

My site is back in the dark ages of 1.5 (actually, apart from listeners
becoming handlers - the old lot listened to many things, now each handler
deals with only one - and the directory layout change - but there's not a
*lot* of difference)

Generally, each release brings new things but removes very few. Therefore,
the old stuff is still pretty relevant. But only if you know the
differences. A bit of a Catch-22, I'll admit.


> And finally, thoughts on GWT Designer (http://www.instantiations.com/
> gwtdesigner/download-trial.html) would be great -- in my experience
> with analogous Adobe software the "wizards" obfuscated necessary
> learning principles.
>

I can't comment directly, having never used it.

My personal attitude, though is that there is a parallel with the building
trade:

I'm very happy to leave JavaScript behind and use GWT, but I don't want to
be another step more remote.
I'm very happy to let other people make the bricks that allow me to design
and build a house, but I don't want to spend my life making prefabs.

And before anyone complains, I know that is an unfair comparison, but it's
the best I could come up with.


Ian

http://examples.roughian.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to