(C++) Why use pictograms and what do they mean?
February 24, 2017 · View on GitHub
(C++) Why use pictograms and what do they mean?
FAQ.
Answer: I like to use small pictograms, because they are as expressive as I desire them in the situations I use them.
Legend of single pictograms
- Approaches:
: OKAY, works okay
: ?OKAY, work in progress, will probably
work okay
: ?FAIL, work in progress, will probably
fail
: FAIL, fails (at the time tried)
: TODO, to do
: N/A, not applicable, unlikely
- Author:
: Joost van den Bogaart
: Richel Bilderbeek
- IDE:
: command line, other
IDE
: C++ Builder
: Qt Creator
- C++ standard:
- Libraries:
- Operating system or environment:
: Android
: Cygwin
: Lubuntu
: Maemo
: Nintendo DS
: Symbian
: Ubuntu
:
VirtualBox
: Windows
: Wine
- Application type(s):
- Project type:
Legend of combinations of pictograms
Sometimes I use combinations of pictograms, especially on my C++ pages. These combinations are ordered in 'size':
- library/libraries
- IDE('s)
- development environment(s)
- target environment(s)
- application type(s)
Consider the following example: 






- library:
Qt - IDE:
Qt
Creator - development environment:


Windows that is run in
VirtualBox under Ubuntu - target environment:
Symbian - application type:
Mobile application
For Windows, I use the following combinations:


:
native Windows, a 'Windows
computer'

:
Windows simulated by Wine on a
Ubuntu computer

:
Windows installed in
VirtualBox on a Ubuntu
computer
and their elaborations:




: works on both a native
Windows computer and Wine on a
Ubuntu computer



: works on both a native Windows
computer and Windows installed in
VirtualBox on a Ubuntu
computer



: works on both Windows simulated
by Wine on a Ubuntu computer and
Windows installed in
VirtualBox on a Ubuntu
computer



:
works on all three: native Windows,
Windows simulated by Wine on a
Ubuntu computer and Windows
installed in VirtualBox on a
Ubuntu computer
:
:
:
:
:
:
:
:
: