I suppose you're right, and that I've just been indoctrinated into separating interfacee from behavior (or Control/View from Model).
Assuming for now that I actually do want to do it that way, I think I understand that the procedure is to make a new target within the project, the library, defined as being derived from the stubs (.m & .h), then somehow express to Xcode that the app needs to be linked with the library? I'm sure it's easy to do, but Xcode, on first encounter, seems a lot like a million-bladed Swiss Army knife.
Also, word has reached me that WSMakeStubs has some limits as to the complexity of the WSDL it will correctly render into stubs. Anyone have experience with this issue one way or another? On Feb 5, 2008, at 3:51 AM, Alexander v. Below wrote:
Am 04.02.2008 um 01:11 schrieb John Chandler:
I imagine I'd need to compile the stubs into a library, and get Xcode to build a Cocoa app that's linked with that library.
Why that? Unless you want it that way, you can just compile the stubs into your Application
But maybe I did not understand the question
Alex
|