|
Huge refactoring: Introduction of Traits to Actions.
This change is really big but the introduction of the Trait concept (at least
in its current light form) is so fundamental that lots of pieces had to be
changed in order to get everything working.
The main point why it was necessary to add these traits in the first place was
to comfortably allow for adding extension of Actions information-wise, i.e.
with stuff that is only important for the QtUI, such as icons, or tooltips, ...
This extra information should not be stored with Action itself, as it has
nothing to do with the workings of the Action. And neither should it get
stored with some blown-out-of-proportions MapOfActions class ...
The gist of the change is as follows:
- OptionTrait contains the token, description, shortform and type of an option,
such as ("position", "position in space, none, typeid(Vector)).
- ActionTrait is the derived form for actions where additionally MenuPosition
and MenuName are stored (and probably more to come for the GUI), also
we have a set of OptionTrait instances, one for each option of the Action.
- Action then contains this ActionTrait, specialized for each Action.
- the preprocessor macros have been enhanced to gather all this information
from the .def files.
- MapOfActions is gone. Completely. Most of its use was to store this extra
information and the ValueStorage part now is just in class ValueStorage.
- ValueStorage is no more an interface to MapOfActions but as the name says
a (type-safe) ValueStorage.
Listing the (remaining) changes in alphabetical order of the class:
- Action
- member value ::name dropped, ::getName() uses ActionTraits::getName()
- new define NODEFAULT which is used in paramdefaults in .def files
- all derived actions classes such as Process, Calculations, MakroAction,...
have been adapated to use the ActionTrait concept as well.
- ActionHistory
- extraced RedoAction and UndoAction, shifted implementation into their own
object files and they use .def files as well (i.e. streamlined with method
used for other actions)
- MenuDescription
- contain information on Menus such as name, ...
- new unit test checks for consistency
- molecule
- const member functions: Copy(), Output() and OutputBonds()
- OptionRegistry
- new registry class for options only
- we want the same type throughout the code for each token, e.g. "position"
- the registry containts checks for consistency
- OptionTrait
- default values are specified in paramdefaults, none are given by NODEFAULT
- introduced default for translate-atoms, point-correlation, pair-correlation
- Registry pattern
- new unit test, but only sceleton code so far
- ...Query, also ...Pipe
- atoms, molecule and elements are now all const
- also ValueStorage's signatures all have const therein
- ValueStorage
- set/queryCurrentValue from MapOfActions
- at times VectorValue has been in .def files where Vector was in the
signature. This is cleared. Such stuff is only present for e.g. BoxVector
being queried as a Vector. But this is a feature and intended.
- World
- most of the (un)selection functions now work on const atoms and molecules
- in one case we need a const_cast to remove this, but this is intentional,
as the vector of selected atoms stores non-const pointers and this is ok.
There is only one test which had to be changed slightly because a specific
option token as "position" must now have the same type everywhere, e.g. always
Vector.
- TESTFIX: Simple_configuration/2: --position -> --domain-position (and
associated to BoxVector)
|
