hardoh/pe

pe's Issues

Inconsistent representation of commands in documentation

the "mod view CS2103T" statement seems to reference a command users can input. You could consider using the same format (red monospace, etc) you used when referencing commands. Makes it more readable.

Have to type too much

< Features that are not optimized enough for fast-typists or target users>

I'm a relatively fast typist but doesn't mean I like typing more than I have to. Consider using only 1 or 2 letters to represent your prefixes?

A command could be as long as: facil add /name NAME [/phone PHONE] [/email EMAIL] [/office OFFICE] /code MOD_CODE

Not so helpful response when adding a new class that clashes.

<Features that don't fit well with the product>

Great that the app lets me know of a possible clash. But it doesn't tell me where the clash happens. It's hard for me to rectify. Sure I can edit this new class but what if I want to change the old one?

Screenshot callout could be better.

If you have to use callouts, I felt consistency in font should still remain. The "This task is on..." white texts appear to be in a different font and it might stick out for readers.

Can't facil find by Module code

As stated in the title, I think this would be an important feature to have. Consider adding it in.

Clickable "modules" for no reason

< Features that don't fit well with the product>

I realised the app responds as if the modules ARE clickable with the blue box indicating "selected"? But it does not change the app in anyway. This may cause confusion to users.

Unable to call undo command "task done"

<The feature does not solve the stated problem of the intended user i.e., the feature is 'incomplete'>

The undo command is works on a number of commands, but I felt that it should have been able to set a "done" task back to "undone". This is important if I had set the wrong task to "done" in error. I do not want to recreate a new task.

Presence of unfamiliar terms (names?) beside page headings.

This may have been added during development to assign team responsiblity, but consider removing them for users to read. They may be confused with the various names.

"OS-X" inaccurate?

Really minor nitpicking but, to keep it real...

I think you can say macOS, Mac OS X. But I not OS-X I feel.

Unncessary command text for "cal"

< Features that are not optimized enough for fast-typists or target users>

There are only two variations of the calendar view command. Both of which are in weeks. Can we make this shorter?
Example, cut out week entirely? If you plan to add viewing by months, etc in the future, consider using shorter prefixes as per issue #2

Expected a screenshot or something for "dashboard"

<Not enough visuals e.g., screenshots/diagrams>

In the glossary, while the user may be expected to have seen the "Module tab" already, might be good to have a way to link them back. Or at least label as "See Figure 3."