Nick
This is an awkward one, or at least looks like one. Forgive me if I'm
saying stuff you already know and understand. (And others might know
differently).
But it sounds as though you are wanting a label for something that derives
from programming which handles data and functions or methods within the one
entity (otherwise known as Object-Oriented Programming).
Earlier forms of programming made a clear distinctions between data to be
used in a program and stored in one or more nominated areas largely
separate from the code instructions (functions) which access that data by
reference to a particular data address.
More recent programming practice (C++, Java) creates an object which holds
data but also incorporates the program instructions (methods) to access
that data in the same combined area or container. That makes some things
easier. You build the object with its methods as one preparatory stage
of programming and set up areas within the object for all the relevant data
related to that object, and probably create the object with some
already-predetermined data. (e.g.a bird object has 2 wings initially, a
mammal is a suckler).
Then when you want to run a full scale program you declare which objects
you want to use, and then only have simple main line programs that call the
methods on each object if you need to reset or change its data. You also
usually have inheritance, so that you can have a logical 'tree" of objects
that have similar characteristics in some areas but different ones in
others, making up say, a taxonomy. You get advantages of some re-use of
code in lots of different areas if you get it right.
Ok. Just cut that down to a word or two and you should be right.. :-)
Point is, an object is both Data and Programming in one entity. You
don't get a lot of conversations about that in the pub.
Wikipedia has it as : a language mechanism for binding data with methods
that operate on that data. Hmm.
I seriously doubt if there's an equivalent other word in popular use, and
if it were me, I'd be assuming I'd have to include a quick explanation of
an object in that context as meaning something like collection of both data
and programming instructions.
-Peter M
On 11 October 2017 at 12:13, Nick Shears <nshears@xxxxxxxxxxx> wrote:
Hi Aus Techies
Can anyone help me find an alternative to the technical noun “Object” for
non-technical users of an app?
A screen has several labels using ”Type” with different qualifiers.
All refer to one of two things, so I’m proposing use of just two labels:
“Type” preceded by one of two qualifiers.
On this screens, end-users will define custom fields which they can then
use on different types of records they maintain.
Some labels will now all be “*Field Type*”. (Text field, text area, radio
buttons, etc.)
Others are currently “*Object Type*”, or “Type”, or unlabeled. (Example
values: Speaker or Session, since the app is for event automation.) What
would you use instead?
The users are non-technical, so although developers are intimately
familiar with “object”, we need an alternative. I’ve suggested “*Record
Type*”, but have been asked if there’s something else.
I’ve found nothing in the Microsoft Style Guide or Merriam Webster (the
users are largely American), nor in what’s left of my brain. No equivalent
term is used elsewhere in the app or its documentation. I don’t consider
“Data” applicable. I’d like something conversational, but can’t find it.
Can anyone help?
Thanks,
Nick
