Options, Settings, Properties, Configuration, Preferences — when and why? -


there several words similar (in sense) meaning:

options, settings, properties, configuration, preferences

english not native language. explain difference in simple english please? think following template useful:

  • use xxx in gui in order let people change behaviour of application (maybe preferences or settings?)
  • use yyy in gui in order let people change parts of object (perhaps properties or options?)
  • use zzz in code ...

what best practices?

tricky, this, there's no 1 single consistent style followed applications. (broadly) synonyms.

in truth doesn't matter long expected audience understands mean.

the biggest difference between properties, affect component or object, , others, affect whole application.

following approximate lead visual studio , other microsoft products:

  • properties represent characteristics of single component or object in application.
  • options alter global ways application works. microsoft products use customise ui toolbar, example. there's implication here can disable ui elements altogether (e.g. "simple" user interface or "advanced" user interface).
  • settings , preferences change qualities of how application works. implication here change, not disable: example, "metric measurements" or "british imperial measurements".
  • configuration application customised each user or group.

but there's no single rule.

i'd suggest use properties object characteristics , settings else that's application-wide.


Comments

Popular posts from this blog

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -

c++ - Convert big endian to little endian when reading from a binary file -

openssl - Load PKCS#8 binary key into Ruby -