Make it a two step process where they select the type first? If all of the data is the same for all types, I will suggest that you are misusing inheritance. Perhaps Role, not Type, is what you want?
Chuck On Jul 26, 2010, at 8:54 AM, James Cicenia wrote: > Hello - > > I was wondering what is the best way to approach this issue. > > Normally, when someone clicks new i will instantiate a new object. > Then my edit/add dialog is the same and I just reference the current object > that is either new or existing and the bindings all work nice. > > However in this instance I won't know the proper subclass until > the user selects a "Type". > > Do I do everything with variables and then assign / write during > the reads and writes? Or is there some other easier way? > > Thanks > James > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net > > This email sent to [email protected] -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
