So, what file do I need to copy/edit to create my own prototypes?

Ted


On Apr 16, 2014, at 3:40 PM, David Avendasora <[email protected]> wrote:

> 
> On Apr 16, 2014, at 7:22 AM, Hugi Thordarson <[email protected]> wrote:
> 
>> Hi all.
>> I'm using ERPrototypes in most of my projects.
> 
> Heads up. Lots of those are broken. Anjo once said that they were supposed to 
> be an example and not actually used. Developers should create their own. 
> Unfortunately that message was either never understood by anyone other than 
> Anjo or ignored. In fact almost everywhere in Wonder’s source code it assumes 
> erprototypes if not otherwise specified. Sigh.
> 
> I’m planning on a commit at some point in the near future that will either 
> add a new ERPrototypes framework with unbroken prototypes, or fix the 
> existing ERPrototypes which WILL break running apps.
> 
> Either way, it won’t happen without lots of up-front communication and 
> cooperation - so don’t worry for now. 
> 
> All my new projects I start with my own prototypes model. 
> 
> Now onto your real question.
> 
>> However, some projects (especially the legacy ones) require project specific 
>> prototypes. Anyone have a good way to use multiple sources of prototype 
>> attributes?
> 
> Yup. You can specify what Prototypes to use per Model with a … you guessed 
> it: a property!
> 
> See ERXModelGroup for a plethora of model-related properties, but I think the 
> one you are looking for is:
> 
> [MODEL_NAME].EOPrototypesFile
> 
> So:
> 
> MyEOModel.EOPrototypesFile=MyPrototypes.eomodeld
> 
> Good luck!
> 
> Dave
> 
> P.S. Missed you at WOWODC. I stayed surprisingly sober. It’s all your fault. 
> A fun group of 5 Germans did a good job of trying to replace 1 Icelandic 
> crazy man, but fell short - we found our way back to the Hotel on only the 
> 2nd try.
> 
>> 
>> If not, I’m thinking I’ll have to specify “fake” prototype names in the 
>> attributes’ userInfos and do some runtime substitution. Makes me feel like a 
>> dirty little programmer, so better ideas are welcomed.
>> 
>> Cheers,
>> - hugi
>> 
>> PS: I have always disliked the way prototypes are implemented in EOF (by 
>> polluting the entity namespace with things that aren’t actual entities). 
>> We’ll have to tackle that one in OpenWO™ :) 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com
>> 
>> This email sent to [email protected]
> 
> 
> —————————————————————————————
> WebObjects - so easy that even Dave Avendasora can do it!™
> —————————————————————————————
> David Avendasora
> Senior Software Abuser
> Nekesto, Inc.
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
> 
> This email sent to [email protected]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to