Rough modifications needed for the issue:

• Modify bind and edit_name functions on user_prompts.rs to ensure names with over 250 chars don't get accepted
• If over 250, it should show an error text with the details, disable the confirm button, and add the error CSS to the entry
• Perhaps the bind function should be separated for name and image editing for easier handling similar to bind_int for numbers

It would be nice to have an indication on the profile section to see if it's connected to the server properly

• Add a new row on user_profile.xml and add a relevant button or image or something to communicate the status
• Bind the property to show the status with WSObject

For every New Chat that is added, the gschema should store the relevant user ID and use that when the GUI starts to re-add the users available for chatting

Currently on each restart it creates a new profile with a new user id. This should persist among launches and be able to reconnect to the WS using the previously saved User ID. gio::Settings schema can be used to save it.

Instead of storing everything on the memory, use a DB that should store

• Created Users, ID, and their profile details. Completed on #36
• All messages communicated

When the server is offline but messages are sent, it should show an indicator perhaps a spinner(?) to highlight that it has not been sent yet. Rough TODO

• Update message_row.xml with the indicator
• Update MessageObject with a var to save whether it was sent or not and bind that with the new indicator UI
• Queue processor already works with the MessageObject. Update the object's sent variable

In case of not being able to connect to the WS, it should continue to try to connect to it. Maintain a queue system in FIFO order. As soon as the WS is connected, it will start sending them, if there is anything to send. Channel could be a solution here. All WS function calls should be handled by a single function to unite them

The smiley button on textview currently does nothing but it's supposed to popup emoji selector

This can be used https://docs.gtk.org/gtk4/class.EmojiChooser.html

With the current communication style, anyone can pretend to be someone else if they have the user ID. Generate a unique token that should be passed with every request to identify if it's the correct user.

Prerequisite: #31 should be implemented first.

Manually scrolling the ScrolledWindow sets the screen as blank. This needs to be fixed

Currently the users on userlist has 2 statuses. Selected or non-selected. Selected users has a blue CSS while non-selected has gray CSS. For non-selected users, if any message is received, it should show a separate style

• Add the new CSS style that would be added on message update
• handle_ws_message function needs to be updated to properly add the new CSS on message receive

• Image link input needs to be verified on whether it's a valid link to an image
• New Chat button input should be verified to ensure it's a proper number

The UI can still use some improvement such as

• Improve color consistency
• Improve CSS styling format
• Anything that would improve the interface

Any contribution toward improving the UI is welcome!

Currently, any deletion attempt will loop the entire liststore, even if it doesn't exist. This should be verified before any deletion attempt is done

https://developer.gnome.org/hig/guidelines/app-icons.html

The plan is to eventually deploy it in Shuttle so the Gui can connect directly to communicate.

• Update setup_callbacks function to call grab_focus on new user select

After reconnecting for send message instead of /message, /new-user-message is getting used. Ideally, it should be using /message by identifying existing active connections and passing it to the proper WS session.

As of now, only new chat/users can be added using the New Chat button but cannot be removed. Would be nice to be able to delete users. The functionality can be added on a mouse right click

• Add options on right click on user_row.xml
• Connect clicked signal to delete it from the users ListStore

Currently after updating the profile it only reflects the UI. It should be broadcast to the WS where the updated info will be sent to all active sessions where the user_id (user_id of the user who's info was updated) was added.

Upon receiving a message ListStore is iterated for every single message which is highly inefficient. The same for finding the deletion target. This must be improved to prevent the UI from lagging when syncing a large amount of data.

• Use binary search to lower the amount of iteration needed

The UI currently doesn't show any time/date of when a message was created. It should be updated to show a timestamp

• Update the message_row.xml UI to show the timer. As a label perhaps? This should be done carefully with a smaller text size
• MessageObject already stores the timestamp. Only the UI needs to be connected to the variable.

Goals:

• The server should not know what message was communicated
• All sent messages should be encrypted with the receiver's key so it can be decrypted from the other side
• All encryption decryption must happen on the GUI side

When a new user is created but the server connection is not available and messages are sent in the queue, the message sending fails after the connection is established as it tries to send to User 0 which should not happen.

Currently following APIs are used

• Dicebear
• Robohash

Would be nice to have more sources of random images. The following needs to be updated

• Add a new function to generate a proper link to the new image source API on utils.rs
• generate_random_avatar_link should be updated with an option to call the new function.

It should be possible to set an empty link on the profile section which would use the AdwAvatar fallback. Adding another button on the image link row to delete this should be good enough

• Update user_profile.xml image link row with a new button. Perhaps the icon user-trash can be used on the button
• Add the functionality on the button press
• Update websocket communication on both gui and server side slightly to except a None/Null value on ImageUpdate

Rough TODO to allow deleting message

• Update message_row.xml with a menu that would open on right-click with an option to Delete Message.
• On press, collect the message number, send it to the server for deletion, and remove it from the interface.
• Update server side to handle the deletion and remove the relevant row from the DB

The server side already stores all message data. On connect/reconnect the server should send all relevant message data to the GUI so it can process and show them in the interface.

Each userobject currently uses RefCell to keep track of the queue. In certain cases, it can cause double borrow_mut and crash it. It should be updated to ensure this doesn't happen. Perhaps make use of mutex?

It spams connect to ws every 10 seconds if the connection fails. The timer should keep increasing after each failed attempt.

Use the SVG file in the project directory and make it usable as the app icon

In the current state, ListBox starts lagging with only 5k messages. Migrate from ListBox to ListView as ListView is designed to be more scalable than ListBox.

Due to the usage of MessageDialog, the UI is restricted to simple actions. MessageDialog doesn't allow further verification after the input is given when adding a new chat and editing the image link. Converting it to AdwWindow will allow verifying everything before any prompt is accepted.

The converted UI should

• Have a similar UI to MessageDialog
• Make use of destructive and suggestive action styles on the buttons
• Hide the close buttons