Re: One Login EOModel for multiple apps?
Re: One Login EOModel for multiple apps?
- Subject: Re: One Login EOModel for multiple apps?
- From: Chuck Hill <email@hidden>
- Date: Thu, 10 Jul 2003 11:59:21 -0700
I'd put it in a framework along with the classes for the eos in the model.
Then include that framework in your project.
Chuck
At 02:33 PM 10/07/2003 -0400, james o wrote:
>thanks to everyone for the help! i've successfully created one EOModel
>that works in multiple apps with different EOModel's. i wish i
>would've done things this way to start with, as i've had some class
>issues that i had to resolve. boy, isn't hindsight 20/20.
>
>-now i'm wondering where is the best place to keep this new EOModel?
>-and when i Add Files (LOGIN.eomodeld) to my project what should i
>select in Reference Style? Default, Group Relative, Absolute Path or
>Build Product Relative so that all my projects see this EOModel. if i
>leave the EOModel outside of the project dir. the EOModeller doesn't
>see the other EOModels and sometimes it complains that it can't see
>relationships.
>
>thanks,
>./james
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Ready, Set, Go >> http://primaxSTUDIO.com
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>_______________________________________________
>webobjects-dev mailing list | email@hidden
>Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
>Do not post admin requests to the list. They will be ignored.
>
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.