You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+63-1Lines changed: 63 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# SOLID Chat
2
2
3
-
## Our Progress (Last Updated on Nov 20)
3
+
## Our Progress (Last Updated on Nov 21)
4
4
5
5
Each of us have created one or more PRs and most of these have been merged into the main branch. Many members have functional UI's (and they are likely happy to demonstrate in tutorial) and others have a basic non-interactive UI and the inner layers of clean architecture. While they may not be able to do an interactive demo, screenshots of these user interfaces are included below.
6
6
@@ -11,6 +11,68 @@ Each of us have created one or more PRs and most of these have been merged into
- Update on inner layers of the conversation history feature:
15
+
- The ConvHistInteractor, responsible for displaying a conversation history, was tested (see [here](https://github.com/CSC207-2022F-UofT/course-project-SOLID-chat/pull/32)). To focus testing on the interactor, a mock data access class was used. While the test does not currently pass, the structure of the test is there.
16
+
17
+
### Profile display
18
+
- By Parmis
19
+
- Implemented by UserSearchUI, which allows a user to type in a user's username to view their features (user and username so far).
20
+
- User information is captured using UserPresenter interface, which uses UserDatabse's interface UserRetriever to retrieve the user of interest, then UserReader reads features of the reader that are eventually presented:
21
+
-
22
+
- Here, Alex123 is not a user of the chat system:
23
+
-
24
+
- parmis is a user of the chat system though:
25
+
-
26
+
27
+
### Profile feature modification
28
+
- By Parmis
29
+
- Implemented by UserMdoificationUI, which allows a user to verify their authority to access their account by confirming their username and password, and then choosing the feature they wish to modify, and enter the new value for it.
30
+
- User information is captured using ChangeController interface, which uses UserDatabse's interface UserRetriever to retrieve the user of interest. Then, UserAuthenticationI confirms user's authority to make the change, then we use Changeable interface (use case) to make the changes to the User entity, and finally use UserModificationGateway to relay the changed info to UserDatabase:
31
+
-
32
+
- Here: Parmis's password is actually 123, so she doesn't get the chance to change her email:
33
+
-
34
+
- as you can see, her email is unchanged.
35
+
- now she enters the right password and tries again:
36
+
-
37
+
- This time, change was successful. She could use this tool to similarly change her username or password too:
38
+
-
39
+
40
+
41
+
### App Screen UI
42
+
- By Amy
43
+
- The App Screen UI is the screen that acts as a proxy between the user's login screen and their individual chats
44
+
- Upon logging in, a user will will be rendered with a view of app screen
45
+
- App screen provides an ordered list of a user's chats and also allows a user to create new chats
46
+
- Each chat button will also display a date indicating the date of the last message in a chat's conversation history, or no date if a chat has no messages
47
+
- ChatView (the window referenced above) will open upon clicking an existing chat to display the chats's GUI
48
+
- With respect to ChatView, clicking on the +Private Chat and +Group Chat buttons will also open an instance of ChatView for a user to create a new chat
- The User will be prompted to include the credentials to create a new account. Then he will be asked to choose a method to deliver the verification code:
Now(after clicking enter and choosing to verify via email), an email with the verification code will show up, and user will be prompted to enter the verification code:
If the incorrect verification code is entered, the following message shows up. Upon closing the message, the user can re-enter the correct verification code, upon which the login UI - asking for the username and password will show up:
If the user enters the credentials of an account that does not exist, the following message shows up. A similar message shows up if the user enters an incorrect password for the username
0 commit comments