FROM : Marco Scheurer
DATE : Sun May 01 13:57:54 2005
On May 1, 2005, at 03:12, Erik M. Buck wrote:
> I am sad to say that I have really never liked x-code. I just
> can't get it to work the way my brain works and the way I want it
> to work.
>
> What I typically want is to create one or more frameworks that
> contains the model objects. Then I want one or more frameworks
> that provide a variety of reusable view classes for viewing model
> objects different ways. Then I want to create several applications
> that use the frameworks. For example, there may be a model
> "viewer" application and a separate model "editor" application.
> There may be a IB palette containing model and view components from
> the frameworks.
> Last, I want a single aggregate project that will build everything
> and keep everything up to date. If I change a model class, I want
> the framework that contains the class to be rebuilt. Then I want
> all of the applications that use the framework to be re-linked or
> even rebuilt as necessary.
>
> I know there is an x-code list, but the thrust of this post is not
> really "how do you do such and such in x-code?"
>
> What I want to know is how other Cocoa developers are coping, and
> how non-trivial applications are being built. It seems to me that
> if I want to use CoreData, I am locked into x-code now.
>
> Are there any alternatives ?
Sorry, I Don't know about alernatives, we're dealing with xcode. It's
painful, but doable, using target dependencies upon other projects
targets. (The pain mostlycome from handling different build styles
and installation for your projects, especially frameworks.)
marco
Marco Scheurer
Sen:te, Lausanne, Switzerland http://www.sente.ch
DATE : Sun May 01 13:57:54 2005
On May 1, 2005, at 03:12, Erik M. Buck wrote:
> I am sad to say that I have really never liked x-code. I just
> can't get it to work the way my brain works and the way I want it
> to work.
>
> What I typically want is to create one or more frameworks that
> contains the model objects. Then I want one or more frameworks
> that provide a variety of reusable view classes for viewing model
> objects different ways. Then I want to create several applications
> that use the frameworks. For example, there may be a model
> "viewer" application and a separate model "editor" application.
> There may be a IB palette containing model and view components from
> the frameworks.
> Last, I want a single aggregate project that will build everything
> and keep everything up to date. If I change a model class, I want
> the framework that contains the class to be rebuilt. Then I want
> all of the applications that use the framework to be re-linked or
> even rebuilt as necessary.
>
> I know there is an x-code list, but the thrust of this post is not
> really "how do you do such and such in x-code?"
>
> What I want to know is how other Cocoa developers are coping, and
> how non-trivial applications are being built. It seems to me that
> if I want to use CoreData, I am locked into x-code now.
>
> Are there any alternatives ?
Sorry, I Don't know about alernatives, we're dealing with xcode. It's
painful, but doable, using target dependencies upon other projects
targets. (The pain mostlycome from handling different build styles
and installation for your projects, especially frameworks.)
marco
Marco Scheurer
Sen:te, Lausanne, Switzerland http://www.sente.ch
| Related mails | Author | Date |
|---|---|---|
| Erik M. Buck | May 1, 03:12 | |
| Tom Birch | May 1, 04:03 | |
| James Dessart | May 1, 04:24 | |
| Tom Birch | May 1, 04:48 | |
| mmalcolm crawford | May 1, 04:53 | |
| Andy Lee | May 1, 04:58 | |
| Marco Scheurer | May 1, 13:57 | |
| Johnny Deadman | May 1, 14:23 | |
| Kevin Callahan | May 1, 18:50 |






Cocoa mail archive

