Open nus-pe-bot opened 2 years ago
This was a specific design decision we made that we believed were in the user's interest. Force-fitting CLI would have been a worse UX and in any case, the module states only that most features needed to be CLI. We felt this was a feature that was only good as non-CLI to make a better product. As it could be easily tested, we felt it was not a failure of the other constraints and could still be valid under the module requirements.
Also a correction to the bug report: there is no need to click on the notes tab, the tab n
or tab notes
command works perfectly fine. It is only when the user is editing notes is there a need to use the mouse.
Taken from the UG Section on Notes:
Note: A discerning user may notice that Notes stands out from all the other tabs. Unlike other fields, Notes support multi-line input. As you may write at length in these multi-line fields, we deemed that force-fitting your note-taking workflow through a single-line command input would be counter-productive and unintuitive.
Taken from the module website:
Recommendation-cli-first A user who can type fast should be able to accomplish most tasks faster via CLI
--
When adding notes for a client, the notes are not entered through the command box. Instead, the user has to use his/her mouse to click on the notes tab to edit it. This functionality thus does not exactly target users who have to type fast since they have to use the mouse whenever they want to add notes.
[original: nus-cs2103-AY2122S1/pe-interim#1431] [original labels: severity.Low type.FeatureFlaw]