Thanks again, everyone. “Class” it now is.
That’s a classy outcome.
Cheers,
Nick
From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Nick Shears
Sent: Wednesday, 11 October 2017 2:39 PM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: Re: Synonym for Object
Thanks Peter. I think that “Class” should do it! It’s certainly what I’m going
to propose.
I’m no developer, but I believe “Class” is actually more appropriate than
“Object” or “Object Type”.
I understand an object to be something that has to be based on a class. So in
our earlier example, if the Class is “Speaker” then “John Citizen” would
actually be an object base on that class.
Thus the custom field “Faculty” is part of the class, the blueprint defining a
speaker, and “Engineering” is the value in that field on John Citizen’s speaker
record.
Thanks Peter, and everyone else who’s taken time to participate in this
discussion today.
Cheers,
Nick
From:
austechwriter-bounce@xxxxxxxxxxxxx<mailto:austechwriter-bounce@xxxxxxxxxxxxx>
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Peter Martin
Sent: Wednesday, 11 October 2017 2:09 PM
To: austechwriter@xxxxxxxxxxxxx<mailto:austechwriter@xxxxxxxxxxxxx>
Subject: atw: Re: Synonym for Object
Ok.... back to programming environment. Also synonym maps
class ?
On 11 October 2017 at 14:59, Nick Shears
<nshears@xxxxxxxxxxx<mailto:nshears@xxxxxxxxxxx>> wrote:
Thanks Peter,
You’re absolutely right, it’s all about what it looks like to the user. ☺
If I can get developers to use the best words on the screen itself, the user
is less likely to have to refer to the documentation I write. (And they’ll be
less likely to make false assumptions after having not read it).
“Category” could indeed work. Unfortunately it is already used elsewhere in
the app, with specific standard meanings, so a field labeled just “Category” on
this screen could confuse the user.
…
