TO-DO
Resize optimization:
- prevent switching from resizing too moving (maybe modify the resize region)
- change the shape back to the regular cursor once done resizing
- One direction resize on the four sides
- Add maximize function
Need to think about:
- Online matchmaking
- Friend request
- right click menu deletion process (progress: deletion completed on ui but not on server side)
Allow user to upload / change profile picture (need to fit the circle instead of having its own shape, also need to save the picture in json file)
- add json file path. (profile path to url?)
Allow user to save pronoun / change intro
- Forgot password
- Optimize Resize
Email Validation
Change name from bot to username on the main window after signing in
establish signal and slot connections between the friend list (QListWidget) and chatpage.
current time function
Change friends' profile information items
- Find a dictionary API and find a way to integrate it
add maximize button to title bar
make title bar flexible
improve login UI
- change gmail logo
- change input "username" text placehoder to "username/email"
- password encryption
- mainwindow
- add dictionary page (not as a stackedwidget)
- edit setting page
- add save button
- add chat page (as a stacked widget)
- add selection QMessagebox/ or as a subwidget/ or as a stackedwidget (this is tobe decided...probably as a group)
- make a UI sample of a chat page (collection of chatting UI element) for later use
- add info page
- add details for chat page (time, profile?, name)
- listwidget only allows selection
- check compatibility (desktop app on Mac/ Windows/ Linux)
- add logo and finalize the UI part of the design
- deal with right-click menu
- deletion
- comment (quote)
- copy
- translate
User ID (random id generation)
Password safety checker
##Serena @Serena12142
祝您成功祝您胜利
client asks for requests and possible new matches when clicked on new conversation
possible refresh button?
server responds
- requests:
load, clear invalid (DNE), already friend, and expired, save, and sent to client
- matching:
input - user, output - array of possible matches; currently all users that are not friends
send user profiles when sending requests
add - new request - server save
remove delete from new matches page
friend_requests.json - ID: {{request},...} - incoming requests - username, time (possibly message)
accept - server - create new, check existence - sender send initial message - receiver if active
delete - delete from page and server
remove user - delete profile and messages
***currently receiver crashes, fix by generating initial message on server side (requires time fix first!)
client requests
time zone server side
add profile last login time (for matching possibly)
find friend - by username - view request profile as above
communicate server-client every day (clear expire)
TO-DO
Resize optimization:
Need to think about:
Robert: @RobertRen1122
Allow user to upload / change profile picture(need to fit the circle instead of having its own shape, also need to save the picture in json file)Allow user to save pronoun / change introEmail ValidationCathy @CathyF9600
Change name from bot to username on the main window after signing inestablish signal and slot connections between the friend list (QListWidget) and chatpage.current time functionChange friends' profile information itemsLindy: @LindyZh
add maximize button to title barmake title bar flexibleimprove login UI-
change gmail logo-
change input "username" text placehoder to "username/email"-
password encryption-
add dictionary page (not as a stackedwidget)-
edit setting page-
add save button-
add chat page (as a stacked widget)- add selection QMessagebox/ or as a subwidget/ or as a stackedwidget (this is tobe decided...probably as a group)
-
make a UI sample of a chat page (collection of chatting UI element) for later use-
add info page-
add details for chat page (time, profile?, name)-
listwidget only allows selectionUser ID (random id generation)Password safety checker##Serena @Serena12142
祝您成功祝您胜利
client asks for requests and possible new matches when clicked on new conversationpossible refresh button?
server responds
load, clear invalid (DNE), already friend, and expired,save, and sent to clientinput - user, output - array of possible matches; currently all users that are not friendssend user profiles when sending requestsadd - new request - server saveremove delete from new matches pagefriend_requests.json - ID: {{request},...} - incoming requests - username, time (possibly message)accept - server - create new, check existence -sender send initial message - receiver if activedelete - delete from page and serverremove user - delete profile and messages***currently receiver crashes, fix by generating initial message on server side (requires time fix first!)
client requests
time zone server side
add profile last login time (for matching possibly)
find friend - by username - view request profile as above
communicate server-client every day (clear expire)