Re: terminology help
I'm struggling to explain a concept in one of our apps that relies on a
parent/child structure of objects. Users can create a relationship between
two objects; the one they start with is automatically the parent. After the
relationship has been added, it is displayed in a list, exactly the same way
on both objects. The only difference is when you open it to edit--then you
can see which is the parent and which is the child. It is possible to have
the same type of relationship twice between objects A and B-- where
A=parent, B=child and where A=child, B=parent. It looks like the same thing
is listed twice.
In OOP, parent usually means superclass and child usually means subclass. If that's not what you mean, and your application is doing anything related to object oriented programming (or if your users are also oop developers) I suggest NOT using these terms as you describe.
You are describing a relationship between two objects. You could use Source to indicate the object that contains the foreign key (that points to the related object) and Destination for the related object. Does that work?
Hope it helps.
Want to support TECHWR-L? Get shirts, bags, hats, clocks,
and more from the TECHWR-L Store. All proceeds support TECHWR-L.
Check out the new release of RoboDemo, our easy-to-use tutorial software.
Plus, buy RoboHelp Office in August and save $100 with our mail-in rebate.
Get details and download free trial versions at http://www.ehelp.com/techwr-l
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
terminology help: From: Rosemary J Horner
Search our Technical Writing Archives & Magazine