[v1.1][F09-B1]Your TA

build.gradle

@@ -57,7 +57,7 @@ dependencies {
 }
 
 shadowJar {
-    archiveName = "addressbook.jar"
+    archiveName = "yourta.jar"
 
     destinationDir = file("${buildDir}/jar/")
 }

docs/DeveloperGuide.adoc

@@ -647,7 +647,7 @@ This utilizes the `MarkCommand` command to update the participation marks of a `
 
 The user will input a command, `markPart INDEX marks/DIGITS`, to the application to update the marks.
 
-The following figure 12 and paragraph below shows the sequence of how the `MarkCommand` command functions:
+The following figure 13 and paragraph below shows the sequence of how the `MarkCommand` command functions:
 
 .MarkCommand Sequence Diagram
 image::MarkCommandSequenceDiagram.png[width="700"]
@@ -691,14 +691,14 @@ image::MarkCommandSequenceDiagram.png[width="700"]
 === Display picture
 
 Users are able to add a display picture for any person within the application. The user can utilise 3 different commands (`add`, `edit` and `updateDP`) to create and specify a display image for the person.
-It fully supports the `undo` and `redo` commands. It adds a drop shadow around the frame to indicate the level of participation (see above section 5.3) of the person.
+It fully supports the `undo` and `redo` commands. It adds a drop shadow around the frame to indicate the level of participation (see above <<Participation, section 5.4 Participation>>) of the person.
 
 This feature allows the user to enter a path to their selected image file when entering any of the above 3 commands and copies the image into the `data/displayPic` folder.
 
 It utilises the `DisplayPicStorage` class to handle all image storage related operations.
 
 It also makes use of the `Participation` feature to display a colored shadow around the display picture.
-This image will be shown in the application next to the details of the person as seen in figure 13 below.
+This image will be shown in the application next to the details of the person as seen in figure 14 below.
 
 .Display Picture example
 image::displaypic_personcard.PNG[width="250"]
@@ -725,7 +725,7 @@ For persons that were not specified a `dp/` during the `add` command, the `Displ
 The display picture can also be changed by using the `edit` or `updateDP` commands.
 The implementation of the UpdateDisplayCommand (`updateDP`) command closely follows the `edit` command, hence we will only showcase the implementation of the `UpdateDP` command.
 
-The following figure 14 is the sequence diagram of the `updateDP` command to show how it functions:
+The following figure 15 is the sequence diagram of the `updateDP` command to show how it functions:
 
 .UpdateDisplayCommand Sequence Diagram
 image::UpdateDisplayCommandSequenceDiagram.png[width="800"]
@@ -739,7 +739,7 @@ image::UpdateDisplayCommandSequenceDiagram.png[width="800"]
 
 To fully support the `undo` and `redo` commands, image files cannot be immediately deleted when it is not in use by the `UI`.
 
-To work around this, a new class `UniqueItemList` was added to the model of the `AddressBook` as seen below in Figure 15.
+To work around this, a new class `UniqueItemList` was added to the model of the `AddressBook` as seen below in Figure 16.
 
 .AddressBook Class Diagram
 image::AddressBookClass.png[width="600"]
@@ -780,7 +780,7 @@ which is stored in `src/resources/images/displayPic` as `default.png`.
 If a valid path to an image is provided, the image will be processed and copied over to the `data` folder where the `addressbook.xml` is stored as well.
 
 The filename of the image copied over will be a <<sha-256,SHA-256>> hash. This hash is calculated over the `Person` object's details (i.e Name, Phone and Email) to ensure a unique filename.
-The following activity diagram in Figure 16 shows how the files are saved:
+The following activity diagram in Figure 17 shows how the files are saved:
 
 .Activity diagram for storing image files
 image::StoreDisplayPictureActivityDiagram.png[width="800"]

docs/UserGuide.adoc

@@ -301,7 +301,7 @@ Command entered: `edit` `2` `p/91234567` `e/johndoe@example.com` `dp/C:\Users\Na
 
 Result: This changes the details of the person with index 2 (Betsy Crowe) and writes over her original saved details (Figure 14).
 
-.Phone and Email of 2nd Person (Betsy Crowe) Edited +
+.Phone, Email and Display Picture of 2nd Person (Betsy Crowe) Edited +
 image::FirstEdit.png[width="300"]
 
 If you find that you've added someone with incorrect details, you can change the entry.
@@ -310,7 +310,7 @@ Command entered: `edit` `1` `n/John Doeser` +
 
 Result: This changes the details of the person with index 1 (originally John Doe) and updates his details (see Figure 15).
 
-.Name Changed to "John Doser" +
+.Name Changed to "John Doeser" +
 image::SecondEdit.png[width="300"]
 
 === Sorting all entries: `sort`
@@ -327,13 +327,13 @@ Adds to the participation marks of a person (student). The maximum limit for par
 and the maximum amount that can be added per execution of the command is 100. +
 i.e. if someone has 90 marks and you add 20, the participation marks will be capped at 100.
 
-If the marks is below 50, there will be a red frame surrounding the person's profile picture. If the person has 50 or more marks, the colored frame around the user will change to green.
+If the marks are below 50, there will be a red frame surrounding the person's profile picture. If the person has 50 or more marks, the colored frame around the user will change to green.
 
 Format: `markPart` `INDEX` `marks/DIGITS`
 
 ****
 * The `INDEX` refers to the index number shown in the most recent listing.
-* The marks to be added must be a *positive integer* between 0 and 100 inclusive.
+* The marks to be added must be a *integer* between 0 and 100 inclusive.
 ****
 
 Examples:
@@ -356,7 +356,7 @@ Command entered: `find` `David` +
 
 Result: Returns David as a result (see Figure 18). +
 
-.Find command returns David
+.`find` Command returns David
 image::markPart2David.png[width="300"]
 
 Command entered: `markPart` `1` `marks/70` +
@@ -380,13 +380,13 @@ Format: `updateDP` `INDEX` `dp/[IMAGE PATH]`
 ****
 * The `INDEX` refers to the index number shown in the most recent listing.
 * The index must be a *positive integer* 1, 2, 3, ...
-* Do note that unused display pictures will be deleted upon the next application startup when logging in to the same account.
+* Do note that unused display pictures will be deleted upon the next application startup when logging in to the same account that updated the display picture.
 * You can reset a person's display picture to default by typing `dp/` with no [IMAGE PATH] written after it.
 * The aspect ratio of the image will be used to fill a circle for the display picture, thus using an image with an aspect ratio close to 1:1 pixels would be optimal.
 ****
 
 [NOTE]
-Do refrain from using high resolution images as display pictures, the optimum resolution is 300 x 300 pixels.
+Do refrain from using high resolution images as display pictures, the optimum resolution is 500 x 500 pixels.
 
 Examples:
 

docs/team/Alaru.adoc

@@ -1,6 +1,7 @@
 = Chia Kah Sheng Ellery - Project Portfolio
 :imagesDir: ../images
 :stylesDir: ../stylesheets
+:repoURL: https://github.com/CS2103JAN2018-F09-B1/main
 
 == PROJECT: Your TA
 
@@ -44,7 +45,7 @@ The existing commands (add, edit, delete and clear) were also updated to support
 ** Documentation:
 *** Help update README (PR https://github.com/CS2103JAN2018-F09-B1/main/pull/66[#66]), changed application icon (PR https://github.com/CS2103JAN2018-F09-B1/main/pull/108[#108]) and name (PR https://github.com/CS2103JAN2018-F09-B1/main/pull/123[#123]).
 *** Updated screenshots used in the User Guide: (PR https://github.com/CS2103JAN2018-F09-B1/main/pull/57[#57], PR https://github.com/CS2103JAN2018-F09-B1/main/pull/130[#130])
-*** Edited the developer guide for English usage, added prefaces, updated images, made explanations clearer (PR https://github.com/CS2103JAN2018-F09-B1/main/pull/123[#123]) and added manual testing cases.
+*** Edited the developer guide for English usage, added prefaces, updated images, made explanations clearer (PR https://github.com/CS2103JAN2018-F09-B1/main/pull/123[#123]) and added manual testing cases (PR https://github.com/CS2103JAN2018-F09-B1/main/pull/130[#130]).
 *** Sequence diagram was added (PR https://github.com/CS2103JAN2018-F09-B1/main/pull/108[#108]) and was edited and used by teammate (PR https://github.com/CS2103JAN2018-F09-B1/main/pull/124[#124]).
 ** Community:
 *** Reported bugs and suggestions for another team in the class (examples:  https://github.com/CS2103JAN2018-F12-B2/main/issues/83[1], https://github.com/CS2103JAN2018-F12-B2/main/issues/80[2], https://github.com/CS2103JAN2018-F12-B2/main/issues/76[3])

src/main/java/seedu/address/MainApp.java

@@ -45,7 +45,7 @@
  */
 public class MainApp extends Application {
 
-    public static final Version VERSION = new Version(1, 4, 0, true);
+    public static final Version VERSION = new Version(1, 5, 0, false);
     private static boolean isTest = true;
     private static final Logger logger = LogsCenter.getLogger(MainApp.class);
     private static final String LOGIN_FILEPATH = "data/login.xml";

src/main/java/seedu/address/model/person/Participation.java

@@ -12,7 +12,7 @@
 public class Participation {
 
     public static final String MESSAGE_PARTICIPATION_CONSTRAINTS =
-            "Participation marks cannot be negative or over 100!";
+            "Participation marks must be between 0 to 100 inclusive!";
     public static final String UI_DISPLAY_HEADER = "Participation marks: ";
 
     public final Integer threshold;