TODO
====

Potential TODO items for Hatari UI (in addition to the ones listed in
its sources).

* Fix Gtk v3 and its Python bindings deprecation warnings:
  - See: https://python-gtk-3-tutorial.readthedocs.io/en/latest/
  - Menus & ActionGroups -> Application framework
  - Table -> Grid layout in dialogs
  - Positional -> named arguments

* Interface between UI and Hatari so that Hatari will forward error
  and other dialog texts to UI for showing, and waits until user has
  acknowledged them (two-way communication)

* WinUAE CPU core specific configuration options:
  - MMU
  - FPU
  - 32-bit addressing

* Support all 8 ACSI and SCSI drives

* Use file selector widget instead of text widget for specifying input
  paths for memory snapshots and devices, so that user can't provide
  invalid paths (sound, snapshot and device output files can be
  non-existing as they're created on demand)

* Separate "Atari monitor" and "Hatari window" settings dialogs
  (move options from "Display" and monitor setting from "Machine"
  dialogs to here and add VDI options to Atari Monitor dialog)

* Features for Help menu:
  - Create empty floppy images (+ convert directories to hard disks?)
  - MSA<->ST converter
  - ZIP->ST converter

* Add more Hatari debugger features to the debug UI:
  - DSP support
  - History support
  - Profiling support
  - DSP symbols loading
    (CPU symbols are loaded automatically from programs)
  - Support for stepping the emulation (both step & next commands)
  - multiple views to memory (refreshed whenever emulation is stopped)
    - supporting also register relative views (register values
      parsing should move to common functionality first)
  - breakpoint support (issue: how to stop emulation on breakpoint
    but still allow Hatari to process remote commands?)
  - trace & debug log viewers?

* Put all configuration stuff into single notebook dialog?

* Translation support for the UI:
  - use gettext
  - build needs to build & install message catalogs
  - some way for Hatari to forward dialog ID to the remote UI
    with dialog string parameters (filenames etc) which then
    need to be localized too & shown...

* Hatari UI specific configuration which stores:
  - list of last used configuration files which would be shown
    either in their own menu or dialog
  - list of last used memory snapshots (10?)
  - disk image dir (uses Hatari config value as default)
  - trace settings
    - remove dialog specific load/save stuff
  - screenshot name
    - needs support also to Hatari src/screenSnapShot.c

* Supporting other, less important Hatari configuration options:
  - keyboard repeat, key mapping type & file, mouse warping & grabbing
  - HD booting, something for multiple GEMDOS partition directories
  - separate A/B disk paths for images that are within ZIP archives
  - joystick autofire toggling, defining the keys for joyemu
  - vdi planes and size, SDL bpp forcing, spec512 threshold, ST blitter
  - cartridge image (where? it has many limitations)
  - log file and levels, console output, bios intercept, run-VBLs

(Many of these aren't supported by the internal Hatari UI either, or
are missing corresponding command line options so they will require
additional support on the Hatari control.c side too or they can
be only enabled at boot, not disabled.)
