Basic design description for the gui #90
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: git/caesar-transfer#90
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Give a basic description how the Gui should look and act.
Description
For easier implementation and consultation, the design of the GUI app should be discussed and recorded in this ticket.
Acceptance Criteria
Which criteria has to be reached to be accepted
Tasks
Which tasks are included to add this feature
Dependencies
Which dependencies are introduced to the project
Estimates
4 hours
Additional Information
None
** GUI process: **
Sender GUI:

Receiver GUI:

Since we are short on time, I would just close this ticket and we will decide which design to use based on a simple A/B test.