The whole point of _my_ use of Xcode and especially D2JC is that it
is nearly zero work to quickly mock-up and prototype object model and
have it as a running application (D2JC) in a mater of seconds with no
configuration of the development environment. It either Just Works™
or I have a problem in my model somewhere. I don't ever have to
question if the problem is somewhere in the configuration of the IDE
or the numerous third-party plugins.
To me the reason WO-newbies would shy-away from WOLips is that they
are already trying to learn WO and Xcode does an excellent job of
just getting out of the way and letting you get an initial project up
and running quickly. With WOLips, you likely have to learn not only
WO, but you have to learn Eclipse's interface and jump through all
sorts of hoops like figuring out how to download and install plugins
and such before you can even start a project, and I don't think
anyone can say that the Eclipse UI is not intimidating when you first
get started. Xcode is not intimidating, it holds your hand and asks
you some questions and gives you a running WO Application.
There is a much higher barrier to entry with WOLips (to my
perception) even if in the long run it is a far superior set of tools.
On May 8, 2007, at 1:33 AM, Simon McLean wrote:
but I can click a button and get either a Direct-To-Java-Client
app, or a running web-application that just works.
You can do this with Eclipse too. I can safely say I have never
tinkered with the build scripts in either XCode or Eclipse.
Simon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
