Refactor Action Registration to a Separate Class

[RalfBarkow]

We need to improve the maintainability and organization of the ZettelkastenView class by refactoring the action registration logic into a separate class called ActionRegistrar. This will encapsulate the action registration responsibilities, making the code cleaner and more modular.

Tasks:

1. Create ActionRegistrar Class:

   • Create a new class ActionRegistrar responsible for registering actions and their corresponding keystrokes.
   • Implement methods for registering individual actions and initializing default actions.

2. Refactor ZettelkastenView Class:

   • Remove action registration logic from ZettelkastenView.
   • Integrate ActionRegistrar into ZettelkastenView.

3. Implement Tests for ActionRegistrar:

   • Write TestNG test cases to cover the functionality of ActionRegistrar.
   • Ensure all existing functionality is preserved and works correctly.

Acceptance Criteria:

• Action registration logic is fully encapsulated within the ActionRegistrar class.
• ZettelkastenView uses ActionRegistrar to manage actions.
• All tests pass, ensuring no regression in functionality.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.