Re: Best Practice with inheritance in D2W
Re: Best Practice with inheritance in D2W
- Subject: Re: Best Practice with inheritance in D2W
- From: Ramsey Gurley <email@hidden>
- Date: Thu, 01 Mar 2012 08:30:51 -0700
For an example, have a look at
https://github.com/nullterminated/ponder/tree/master/ERR2d2w/Components/Nonlocalized.lproj/R2DCreateSubEntityChooser.wo
Ramsey
On Feb 29, 2012, at 3:46 PM, Tim Worman wrote:
> I'm working on a (hopefully) very simple D2W app. One entity I'm working with represents door keys - which I've made Abstract in the model and set up an inheritance structure for various types of keys.
>
> What I'm wondering - what is the best practice for providing a quick and easy way for the operator to add a new door key record that belongs to one of the sub-types? I can't make a new key of the Abstract parent and I wouldn't want to provide a tab in ERMD2W that represents each door key sub-entity. I know this probably isn't overly complicated but sometimes with D2W I'm still wondering how to "get there from here."
>
> Tim
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden