yhtminceraft1010x / ped Goto Github PK

The box in which the command result is shown should ideally be right below the command input line and above the filters. This makes it easier for a fast-typist to read what went wrong if an incorrect command format were keyed in.

Formatting can be enhanced by separating the numbered points into separate lines for add_tutor_filter and add_appointment_filter. Here is an example from add_tutor_filter:

A minor one, but the first one I noticed is that the log is still saved as addressbook.log.0

I believe that the consistency of the user guide formatting can be enhanced by having a continuous comment block for the add_appointment example command (The first example below has a broken comment block) + not bolding the commands:

This keeps the formatting in line with those under the Features section

When I keyed in add_budget and delete_budget without arguments, I noticed that the error that pops out has missing space and colon. Example below shows add_budget:

There is an overlap with the Math schedule that obscures part of the Math appointment seen here. This happened when 2 separate events took up a similar slot:

The obscured appointment (index number 2):

The clashing schedule:

Possible remedies that I would like to suggest:

1. Reconfigure GUI to allow both to be displayed at once, similar to how NUSMods shows a timetable clash
2. Update the code to ensure that there are no clashing appointments and schedules

It would be helpful to mention in the User Guide's delete_tutor section that appointments have to be cleared before deleting tutors:

User Guide description:

What happens on the app:

I noticed that the budget is not shown all the time, rather, it is only shown when view_budget command is called. The budget is quite hard to keep track of.

In addition, I would also like to suggest removing the b/ prefix given that this adds more characters to type out even though the budget-related commands accept at most one parameter.

I noticed that the grades used for Tutor Tracker are A-F and S/U, similar to NUS grading system.

However, some secondary schools in Singapore (especially those taking O-Levels) use the alphanumeric grading system, which is A1, A2, B3, B4, C5, C6, D7, E8 and F9. I feel that this is something the developers should take note of given that the Tutor Tracker is catered to secondary school students.

Me trying to key in grade A1:

For reference: https://www.singaporeeducation.info/education-system/grading-system.html

Possible solutions:

1. Implement A1-F9 grading into the code.
2. Insert a table describing grade mappings into the User Guide (example: For grades A1 and A2, key in grade A)