20180117 Magnus Schieder

  20170317 BER: Reproduce and then fix a defect that it is surprising which
  entries are moved by `m` or deleted by 'd'.
  It probably has to do how multi-selection are handled. Maybe they
  are not cleared properly at the end of an operation.
  One description: It happens when you have changed a lot of entries
  from different projects (I assume), e.g. by editing the description,
  the length or timedate and then use move where you intend to only move
  one, the unwanted result is several moved entries.

  reproduced with getan 2.1
  20180118BER Reproduced with urwid v1.3.0, python3.4.6, getan 2.2.dev1 r445

  Creating a new database with test data:

  1) Delete getan_test_data.db if it already exists to create a new database.
  2) Execute getan_test_data.py to get the test database getan_test_data.db.
     (getan/test_data/getan_test_data.py)

- Bug 1.0
  2) Open getan with the test database. (getan /path/getan_test_data.db)
  3) Switch to the entries from the project pro1 with tab.
  4) Mark with return and arrow keys ent1 and ent2.
  5) Go back to the projects with tab.

  20180118BER:
    Observation: ent1 and ent2 are not highlighted anymore.

  6) Switch back to the entries of project pro1.
  7) Mark this time ent3 and ent4.
  8) Press m, then 3 and then y to move ent3 and ent4 to pro3.

  Expectation:
    ent3 and ent4 are moved to pro3.

  Result:
    ent1, ent2, ent3 and ent4 were moved to pro3.

- Bug 1.1
  Execute 1) to 7) from 1.0.
  8) Press d to delete ent3 and ent4.

  Expectation:
      ent3 and ent4 are deleted.

  Result:
    ent1, en2, ent3 and ent4 are deleted.

- Bug2
  Execute 1) to 4) from 1.0.
  5) Press m.
  6) Now also mark ent3 and pro ent4.
  7) Press 3 and then y to move ent1, ent2, ent3 and ent4 to pro3.

  Expectation:
    After pressing m, you can not mark additional entries.

  Result:
        Only ent1 and ent2 are moved, though all are selected.


20180104 BER (minor) Display licensing information with --version and
  usage. Implementation idea: change this when moving away from optparse.

20170709 BER: Give scripts/getan-eval.py a more specific name and add
  it as a script to be installed.

20170529 BER: Python compatibility: switch from deprecated optparse module
  to argparse. Affects getan/main.py and scripts/getan-eval.py.

20170504 BER: Some multi-user installations do not want a logfile by default.
  We could solve this requirement by making it configurable.

20160912 BER: Better code: states.py: classes EditEntryState and
  AdjustEntryState have same methods exit() and set_focus(), maybe join them?

Older:

- Create a 'Help-Widget' to give the user an information about all possible
  keys.

- reimplement RPN input for current getan implementation (28489e672e61)

- The sum of previous times and currently running time should be displayed as
  in previous versions of getan.

- The currently running time should be shown near the project.