From 6fdf62bd05e6216000ecf6a7633008fdb9c1bf1c Mon Sep 17 00:00:00 2001 From: Ikjot Singh Dhody Date: Mon, 24 Jul 2023 22:26:09 +0530 Subject: [PATCH] blog: Rename and format blog. Signed-off-by: Ikjot Singh Dhody --- ...ementation.md => 2023-07-24-Join-MUC-With Moxxy.md} | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) rename _posts/{moxxy_implementation.md => 2023-07-24-Join-MUC-With Moxxy.md} (79%) diff --git a/_posts/moxxy_implementation.md b/_posts/2023-07-24-Join-MUC-With Moxxy.md similarity index 79% rename from _posts/moxxy_implementation.md rename to _posts/2023-07-24-Join-MUC-With Moxxy.md index 8480681..650996d 100644 --- a/_posts/moxxy_implementation.md +++ b/_posts/2023-07-24-Join-MUC-With Moxxy.md @@ -22,29 +22,29 @@ To implement MUC support in Moxxy, we need to extend its functionality and intro #### JoinGroupchatPage - This page will contain 2 text fields, one for the JID, one for the nick. It also has a button that allows us to join a MUC. It is an alternative route to the current StartChat page, if the user selects that they want to join a groupchat. +This page will contain 2 text fields, one for the JID, one for the nick. It also has a button that allows us to join a MUC. It is an alternative route to the current StartChat page, if the user selects that they want to join a groupchat. ### New Command #### JoinGroupchatCommand - This command is sent to the data layer worker (separate thread) from the UI, when the user clicks on the join groupchat button on the new join groupchat page. It contains information about the JID and the nick that the user tried to join with. This will only be sent to the worker thread if the input validations are cleared. +This command is sent to the data layer worker (separate thread) from the UI, when the user clicks on the join groupchat button on the new join groupchat page. It contains information about the JID and the nick that the user tried to join with. This will only be sent to the worker thread if the input validations are cleared. ### New Event #### JoinGroupchatResult - This event is sent back as a result of the JoinGroupchatCommand. Based on whether the request succeeded or failed, it will return the new Conversation object that has just been created. +This event is sent back as a result of the JoinGroupchatCommand. Based on whether the request succeeded or failed, it will return the new Conversation object that has just been created. ### Database changes #### GroupchatDetails table - Add a new GrouchatDetails table to the database containing two data items - the jid and the nick. The main reason to have a separate table for the groupchat details, instead of to just have a new nick item in the Conversation table - was to maintain the single responsibility principle. +Add a new GrouchatDetails table to the database containing two data items - the jid and the nick. The main reason to have a separate table for the groupchat details, instead of to just have a new nick item in the Conversation table - was to maintain the single responsibility principle. - When the user fetches a conversation of type groupchat from the database, a separate call will be made that fetches the relevant groupchat details from this new table, and attaches it to the Conversation object. +When the user fetches a conversation of type groupchat from the database, a separate call will be made that fetches the relevant groupchat details from this new table, and attaches it to the Conversation object. ### Miscellaneous changes