Re: Two EOModels in one project

If you're using standalone EOModeler, it depends on PB.project being  
correct in your project folder (at least this is true with WOLips --  
not sure if Xcode has some other magic it can work to make EOModeler  
find the other eomodel).  So make sure that in the FRAMEWORKS  
section, the framework you depend on is listed there properly.  I  
believe EOModeler then shows any models defined in any of the  
frameworks in that list combined with any listed explicitly in your  
WOAPP_RESOURCES section.

ms

On Jan 24, 2006, at 4:24 AM, Paul Lynch wrote:

> OK.  Just to add another datum - I always (90%+) open mine from  
> Xcode.  My EOModeler claims to be 5.2.
>
> Paul
>
> On 24 Jan 2006, at 09:03, Guido Neitzer wrote:
>
>> I have absolutely no problems with this (despite the known  
>> EOModeler bugs). I open models from Xcode or Eclipse. If I open  
>> them from the Finder, it doesn't work.
>>
>> cug
>>
>>
>> On 24.01.2006, at 9:24 Uhr, Paul Lynch wrote:
>>
>>> I do the same as Geoff, as a result of exactly the same problems  
>>> - only I use XCode (mostly).
>>>
>>> Paul
>>>
>>> On 24 Jan 2006, at 07:58, Geoff Hopson wrote:
>>>
>>>> I always end up having problems with this. And I always end up  
>>>> opening the ModelB.eomodeld folder and editing the appropriate  
>>>> plist, manually adding the name of the entity in the  
>>>> ModelA.eomodeld to the relationship definied in the plist. Then,  
>>>> when I open the ModelB.eomodeld in EOMuddler and access my  
>>>> entity, it prompts me to find ModelA.eomodeld. And, as if by  
>>>> magic, the popup in the inspector is populated with ModelA and  
>>>> ModelB.
>>>>
>>>> I use Eclipse/WOLips as opposed to XCode, so YMMV...
>>>>
>>>> Geoff
>>
>> -- 
>> PharmaLine, Essen, GERMANY
>> Software and Database Development
>>
>>
>>
>
> _______________________________________________
> WebObjects-dev mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-dev