forked from nus-cs2113-AY2324S2/tp
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from JeffinsonDarmawan/fuzzylogic-enhancement
Fuzzylogic enhancement
- Loading branch information
Showing
19 changed files
with
690 additions
and
195 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
# Samuel Ong - Project Portfolio Page | ||
|
||
## Overview | ||
Florizz is a digital florist replacement that helps users choose appropriate | ||
flowers to put into a bouquet for various occasions. | ||
|
||
### Summary of Contributions | ||
* Code contributed: [RepoSense Link](https://nus-cs2113-ay2324s2.github.io/tp-dashboard/?search=samuelory&breakdown=true&sort=groupTitle%20dsc&sortWithin=title&since=2024-02-23&timeframe=commit&mergegroup=&groupSelect=groupByRepos&checkedFileTypes=docs~functional-code~test-code~other&tabOpen=true&tabType=authorship&tabAuthor=samuelory&tabRepo=AY2324S2-CS2113-T11-3%2Ftp%5Bmaster%5D&authorshipIsMergeGroup=false&authorshipFileTypes=docs~functional-code~test-code~other&authorshipIsBinaryFileTypeChecked=false&authorshipIsIgnoredFilesChecked=false) | ||
|
||
|
||
* **New feature**: Overall OOP of the product | ||
* Wrote the overall flow of the product, i.e. having Ui take in inputs from the user, | ||
have them be parsed by Parser, which then creates a Command to be executed by the core Florizz class. | ||
* By setting the overall structure of the code for my teammates, it made it easier for them to implement | ||
their features as they just had to create the Command as well how to parse information from the users input to the Command. | ||
|
||
|
||
* **New feature**: Creating reading and deleting bouquets | ||
* What it does: Allows the user to create and delete bouquets. | ||
* Justification: This feature allows the user to arrange their own bouquets with their own flowers, | ||
and also delete any unnecessary bouquets. | ||
* Highlights: This feature involved overriding the equals method of the Bouquet class for it to only | ||
be equals if the name of the Bouquet is the same, so that removing and adding to the Bouquet ArrayList would be much easier. | ||
|
||
|
||
* **New feature**: Flower pages | ||
* What it does: When viewing a list of flowers, instead of viewing the entire list of flowers, | ||
the user would only see "pages" of max five flowers at once. The user would then be able to type "next" or "back" | ||
to go forward or backwards respectively. | ||
* Justification: This would make the code more future ready, as if the list of flowers gets too long, | ||
the user would have to scroll up to view all the flowers if it was printed in one long list, which would | ||
be really inconvenient. | ||
* Highlights: This implementation was challenging as it required adding a memory of what list of flowers was last | ||
printed to the users as well as what page they were currently on. | ||
|
||
|
||
* **New Feature**: Ability to choose flower colour when adding/removing flowers to Bouquets. | ||
* What it does: When adding flowers, if there is more than one colour available for a flower that the user wants to add, | ||
the user has to choose the correct colour to add the flower. This can be achieved in two ways, including the colour in the | ||
original command by including the /c <colour> field after the name, or if the user omitted that field, by viewing a list of | ||
available colours for that flower after inputting the original command and choosing which colour they meant. | ||
* Justification: In flower language, some flowers have vastly different meanings and can convey different intentions | ||
if you simply change the colour. As such, it is important to specify the colour of the flower in the bouquets, lest the user | ||
accidentally convey the wrong message to their target audience. | ||
* Highlights: This command required two separate ways to implement the same feature as the storage of bouquets to memory involved | ||
writing the command to the file, hence it was more efficient to condense all the relevant flower information into one command. On the | ||
other hand, having too many fields in one command makes it inconvenient for the user to add or remove flowers, as well as the fact that | ||
many flowers only have one flower. Hence, I decided to make putting the colour in the original command optional and allow the user to decide the colour later. | ||
|
||
|
||
* **Enhancement to existing features**: | ||
* Made flower colours and occasions enums within the Flower class. (Pull request [#62](https://github.com/AY2324S2-CS2113-T11-3/tp/pull/62)) | ||
* Updated info command to show flowers with different meanings and occasions for different colours. (Pull request [#89](https://github.com/AY2324S2-CS2113-T11-3/tp/pull/89)) | ||
|
||
|
||
* **Documentation**: | ||
* User Guide: | ||
* Added documentation for features `new bouquet`, `mybouquets` and `delete bouquet` | ||
* Updated documentation for `info` and `flowers` features | ||
* Developer Guide: | ||
* Added implementation details for `new bouquet` feature |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.