Open joeltio opened 1 week ago
As stated in the CS2103 tP: Constraints Website, the application should be optimised for CLI.
As mentioned in the recommendations, non-CLI inputs will reduce the suitability of the product to target users. Our current user interface assumes that users prefer to interact with the app via a CLI interface.
However, future iterations can also optimise the app for GUI.
Team chose [response.NotInScope
]
Reason for disagreement: Although the CS2103T website says that the application should be optimised for CLI, this is different from being solely usable via the CLI. Perhaps the user guide says it better:
It should still have some basic benefits of a GUI although the application is CLI-first. I would expect that clicking on a student to view it is basic.
Although the user can view a student using the
view_student
command, the user would also expect to be able to use the GUI to view a student when clicking on a student from the list.Expected: Student that is clicked on is shown.
Actual: Student that is clicked on is not shown.