Neo Weihong - Project Portfolio

CommandParser then returns an AddBioCommand object that stores the User to be created. EditBioCommandParser on the other hand creates an EditBioCommand object that stores an EditedUserDescription containing information on which fields are edited to be edited.

For the bio and clrbio commands, the implementations are relatively more straightforward.

An illustration of how the information flows for the editbio command is shown as follows:

Upon receival of the command fontcolour, if fontcolour has no arguments (checked by FontColourParser), a new FontColourCommand with no arguments is returned, and upon execution return a CommandResult that shows the existing fontcolour used via access of ModelManager (logic is similar to the ones for biography)

Background on the other hand, checks for additional possible arguments.

Otherwise a ParseException is returned.

An illustration of the logic for handling a bg command is shown as follows:

The ImageAnalyser class used to determine a background image’s dominant colour is inspired, collectively, by Zaz Gmy’s code example and user mhshams's code snippet.

A diabetic user’s Achievements is supported by the achvm command, that displays the list of user’s achievements. Similar to how bio is implemented, SugarMummyParser returns an AchievementsCommand that overrides the getDisplayPane() method to return DisplayPane.ACHVM – such that Ui of Ui sets the children of the MainDisplayPane node to be the AchievementsPane. Each Achievement is represented using an ImageView in JavaFX TilePane so that all images are of the same size.

When the program starts, an AchievementsMap containing a Map of RecordType to List of all Achievement objects that the program has is created in ModelManager.

The AchievementStateProcessor class is then called, which iterates through the list of all Record elements stored in ModelManager and updates the State of each Achievement if necessary.

Thereafter, for each addition and removal of Record elements, the same process described above is used to update the AchievementsMap, that maps RecordType to an AchievementsList of Achievement elements with updated State attributes.

When the achvm command is received by the program, this AchievementsMap is simply retrieved from ModelManager to LogicManager and the corresponding images representing the Achievement objects in the list, with their State values, and attributes are presented to the user via the MainDisplayPane of the MainWindow.

The full list of Achievement items, as well as corresponding State and Level possible to attain for each RecordType in the current version of the program are shown as follows:

Each Achievement State is represented by hand-drawn images, which were coloured digitally using Adobe Photoshop. If a developer intends to modify or extend the current list of Achievement items, he or she may also modify or add on to these images that are currently located in /view/images/achievements/ of the project directory.

Motivational aspects of the application are supported using motivational quotes.

Each motivational quote exists as a String in an unmodifiable List of the class MotivationalQuotes.

The List of quotes (collated from different sources but modified to have the same formats) are initialised to be part of ModelManager when the program first starts up.

Upon initialisation of the program, the MotivationalQuotesLabel.fxml file is referenced via its corresponding class.

Retrieval of the List of motivational quotes is done via LogicManager which accesses the List of motivational quotes in ModelManager.

A quote is randomly selected and then displayed to the user via the program’s user interface.

It is possible to separate the commands for fontcolour and background into different commands (eg. addfontcolour, editfontcolour, showfontcolour, clrfontcolour). However, this is likely unnecessary as this will not only require the end user to type more words, but also introduce redundancy (eg. clrfontcolour could simply be fontcolour black and still achieve the same effects as clrfontcolour).

An alternative idea to achieving fontcolour and background throughout the entire app was to visit each JavaFX child Node recursively and set the colours and backgrounds if the nodes are of specific instances with these attributes (eg. Label which has textfill attribute). However, this idea was quickly aborted as the TableView implemented only renders headers after the scene has been set and to include such a case in the recursive solution adds significant complexity to the program on top of the possibility of severely breaking abstraction.