nus-pe-bot
commented
4 years ago Team's Response
As per requirement, this program is catered for CLI users thus in a standard CLI interface, most CLI will be able to read through the commmands easily line by line. If it is catered for other users that are not familiar with CLI interface, then a GUI approach would be more appropriate but that is out of our syllybus.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: What I meant by 'user input and application output clogged together in UI' is not about not being 'able to read through the commmands easily line by line', it's about there is no clear separation between user input and application output (as stated in the issue description). Users can surely read easily line by line but it is difficult to identify which ones are commands or which ones are responses from the application.
When everything is clogged together, it makes it difficult for users to trace back what commands they have entered and what were the responses. But it is necessary/useful for the users to trace back thre previous responses they got from earlier commands they entered because some commands are related.
The dev response does not really address this issue.
The UI is quite clogged sometimes and there is no clear separation between user input and application output. This is inconvenient for users to identify what they have entered and what were the outputs.