Re: New java class
Re: New java class
- Subject: Re: New java class
- From: "Jerry W. Walker" <email@hidden>
- Date: Fri, 7 Apr 2006 16:13:26 -0400
Hi, Chuck,
On Apr 7, 2006, at 1:42 PM, Chuck Hill wrote:
It all sounds so reasonable when you say it like that.
Heh, I was just trying to answer Jeff's unspoken question, which
seemed to me to be: "why do these three targets exist and what's the
ESSENTIAL difference between them (beyond nuance)?" I think Art
answered Jeff's other questions admirably.
The question and answer should probably go on your WO FAQ, since it
seems to keep cropping up in one form or another.
Now if only we could make the GUI as clear.
I don't think that will ever happen so long as Xcode is being used as
the primary IDE for C, C++, Objective C, Java and Python (not to
mention, nearly any other file transformation process you care to
shove into it).
I think the problem is further complicated by the fact that Cocoa is
written in Objective C and Java is a poor relative in terms of Xcode
features, functions and, most importantly, documentation.
I'm beginning to wish for a WebObjects Xcode mailing list. I've not
been particularly satisfied with either the Xcode mailing list, nor
with the Apple Java Developer's mailing list, though the latter comes
closer to my needs.
My biggest problems with these latter two lists is that they seem to
generate about 2 - 5 times the traffic that the WO lists generate and
they have a much lower ratio of content-in-which-I'm-particularly-
interested to other-stuff (it sounded crass and arrogant when I
initially wrote "signal-to-noise-ratio).
Regards,
Jerry
Chuck
On Apr 7, 2006, at 9:40 AM, Jerry W. Walker wrote:
Hi, Jeff,
Actually, the targets in Xcode for WebObjects are fairly
straightforward. Xcode is aiming for a split install in deployment
where your static HTML files and images (basically, any files that
can be served directly by the webserver) are put under the web
server root and your code and other resources which can't be
vended by the web server are put in the application directory.
A "Target" under Xcode is simply a set of files and the
instructions for turning those files into some derived product
(typically an executable through compilation and linking).
Clearly, it makes sense for Xcode to have the two targets,
"Application Server" and "Web Server" to represent the two
products it intends to build.
The third target (the project target), named after your
application, is an aggregate target simply comprising the other
two. It's instructions are simply to depend on each of the other
two, so if anything changes in one or both of the other two, it
will trigger the building of the one or both other targets.
The project target itself has no content, so nothing should be
added to it.
Regards,
Jerry
On Apr 6, 2006, at 10:26 PM, netBrackets wrote:
Thank you, thank you, thank you. I actually did try adding it to
both the Application Server and the Applicationname tagets, but
didn't try Application Server only. I never have quite gotten my
arms around the different targets. Actually I think I have
understood them in the past, but by the time I have trouble with
them again (like now) I've forgotten quite what the nuances are
between them.
Thanks again,
Jeff
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
email@hidden
203 278-4085 office
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden