如何解释“实例”的概念？对于普通用户
我正在创建一个应用程序，用户可以在其中创建卡片和卡片组。
他们可以做的一件事是创建一张卡牌并在套牌之间共享它的一个实例。因此，如果他们修改这张卡，所有套牌中的所有实例也将被更改。这在我的应用程序中非常有用，但它可能会让用户感到惊讶，所以我想以简单的方式解释这一点。
你会如何解释这一点？作为程序员我们都知道实例是什么，但是普通用户熟悉这个概念吗？我是否应该使用“实例”这个词，或者是否有一个用户更熟悉的等效词？
I am creating an application where users can create cards and decks of cards.
One thing they can do is create a card and share an instance of it among decks. So if they modify this card all the instances in all the decks will be changed too. This is very useful in my app however it might surprise users so I want to explain this in a simple way.
How would you go about explaining that? As programmers we all know what instances are, but are regular users familiar with the concept? Should I use the word "instance" at all or is there an equivalent word with which users would be more familiar?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
我不认为“实例”是一个完全糟糕的术语，但也许另一种解释它的方式是这样的：
...或一些此类不太详细的变体。
I don't think "instance" is a completely terrible term to use, but maybe an alternate way to explain it is something like:
...or some such less verbose variation.
你可以为这样的卡片发明一些词。简而言之，“MAdeCards”属性的变化将随处可见。并避免使用“实例”这个词。
You can invent some word for such cards. And explain in short, that changing properties of 'MAdeCards' will be visible everywhere. And avoid the word 'instance'.
我会以另一种方式看待它，并将这些实例称为“卡片”。 “模板”或“类”可以称为“卡类型”。
I would look at it the other way, and call the instances just 'cards'. The 'template' or 'class' could then be called a 'card type'.
告诉他们 OOP 的层次部分怎么样？一张卡片有一个父亲和一个母亲，代表它的左指针和右指针。一张卡片可以有子对象（同样是它的左指针和右指针）。一张主卡的每个子卡很可能都具有他的属性。主卡的一个突出属性就是独特属性。如果主卡以同样的方式修改，它的所有子卡都会以同样的方式修改，没有任何延迟？
What about telling them about the hierarchical part of OOP? A card has a father and a mother for it's left and right pointer. A card can have children (again for it's left and right pointer). It's most likely that every children of a master card share his attributes. An outstanding attribute of the master card is the unique attribute. If the master card is modified in way all it's children gets modified in the same way without any delay?
我要买一部新手机（手机）。或者一辆车。
这是一类：
我买了一辆新的三星或奥迪。那是一个实例。
非技术人员不关心我们的日常概念，所以甚至不使用“实例”也许
在现实中世界上，一张牌不会出现在好几副牌中，更不可能出现在所有牌组中。乍一看，你的模型对我来说没有意义......
I'm going to buy a new mobile phone (cell phone). Or a car.
That's a class:
I've bought a new Samsumg or Audi. That's an Instance.
Non-techie folk don't care about our day to day concepts so don't even use "Instance" maybe
In the real world, one card would not be in several decks, let alone all decks. At first glance, your model doesn't make sense to me...
实例可以替换为“编辑主卡”，并且您还可以在链接/按钮“注意：修改将反映在您所有现有的牌组中”旁边获得文本帮助。希望您能够按照“目标用户”想要的方式重新表述内容。您需要使用按钮和帮助文本来检查目标用户是否能很好地接受这些信息，或者向他们询问建议，以便他们可以更轻松地重新措辞，然后合并响应并得出结论。
Instance can be replaced by 'Edit Master Card' and also you can have text assistance next to the link / button "Note: The modification would reflect in all of your existing decks". Hope you can rephrase the content how the way the 'target user' wants. You need to check with the target users with the button and help text whether this information is well receive by them, or else ask them suggestion in what way they get it easier to rephrase it then consolidate the response and conclude.