tencent cloud

Feedback

Last updated: 2023-09-28 10:16:48
    TUIKit implements the sending and display for basic message types such as text, image, audio, video, and file messages by default. If these message types do not meet your requirements, you can add custom message types.

    Basic Message Types

    Message Type
    Renderings
    Text message
    
    
    
    Image message
    
    
    
    Audio message
    
    
    
    Video message
    
    
    
    File message
    
    
    
    

    Custom Message

    If the basic message types do not meet your requirements, you can customize messages as needed. The following uses sending a custom hypertext message that can redirect to the browser as an example to help you quickly understand the implementation process. The built-in custom message style of TUIKit is shown in the figure below:
    
    
    Note
    In TUIKit 5.8.1668, a new custom message scheme was designed, which introduces many changes compared with the original scheme and is easier to implement. APIs of the original scheme are retained but are no longer maintained. We strongly recommend you to upgrade to version 5.8.1668 or later to use the new scheme to implement custom messages.

    Displaying a Custom Message

    The cell element of the built-in custom message of TUIKit is shown in the figure below:
    
    
    You can receive a custom message via the onRecvNewMessage method in ChatPresenter.java, and the received custom message will be displayed in MessageViewHolder mode in the message list. The data required for MessageViewHolder drawing is called MessageBean.
    The following introduces how to display a custom message.

    Implement the MessageBean class for the custom message

    1. Create the CustomLinkMessageBean.java file in TUIChat/tuichat/src/main/java/com/tencent/qcloud/tuikit/tuichat/bean/message/. Inherit data from TUIMessageBean to the CustomLinkMessageBean class to store the text to display and the link to redirect. Sample code:
    public class CustomLinkMessageBean extends TUIMessageBean {
    private String text;
    private String link;
    
    public String getText() {
    return text;
    }
    
    public String getLink() {
    return link;
    }
    }
    2. Rewrite the onProcessMessage(message) method of CustomLinkMessageBean to implement custom message parsing. Sample code:
    @Override
    public void onProcessMessage(V2TIMMessage v2TIMMessage) {
    // Custom message view implementation. Here we configure to display only the text information and implement link redirection.
    text = TUIChatService.getAppContext().getString(R.string.no_support_msg);
    link = "";
    String data = new String(v2TIMMessage.getCustomElem().getData());
    try {
    HashMap map = new Gson().fromJson(data, HashMap.class);
    if (map != null) {
    text = (String) map.get("text");
    link = (String) map.get("link");
    }
    } catch (JsonSyntaxException e) {
    
    }
    setExtra(text);
    }
    
    3. Rewrite the onGetDisplayString() method of CustomLinkMessageBean to generate the text summary in the conversation list. The implementation effect is as follows:
    
    
    Sample code:
    @Override
    public String onGetDisplayString() {
    return text;
    }

    Implement the MessageViewHolder class

    1. Create the CustomLinkMessageHolder.java file in Android/TUIChat/tuichat/src/main/java/com/tencent/qcloud/tuikit/tuichat/classicui/widget/message/viewholder/CallingMessageHolder.java. Inherit data from MessageContentHolder to CustomLinkMessageHolder to implement the bubble style layout and click event of the custom message. Sample code:
    public class CustomLinkMessageHolder extends MessageContentHolder {
    
    public CustomLinkMessageHolder(View itemView) {
    super(itemView);
    }
    }
    2. Rewrite the getVariableLayout method of CustomLinkMessageHolder and go back to the layout of the custom message. Sample code:
    @Override
    public int getVariableLayout() {
    return R.layout.test_custom_message_layout1;
    }
    3. Rewrite the layoutVariableViews method of CustomLinkMessageHolder to render the custom message to the layout and add the custom message click event. Sample code:
    @Override
    public void layoutVariableViews(TUIMessageBean msg, int position) {
    // Custom message view implementation. Here we configure to display only the text information and implement link redirection.
    
    TextView textView = itemView.findViewById(R.id.test_custom_message_tv);
    String text = "";
    String link = "";
    if (msg instanceof CustomLinkMessageBean) {
    text = ((CustomLinkMessageBean) msg).getText();
    link = ((CustomLinkMessageBean) msg).getLink();
    }
    textView.setText(text);
    msgContentFrame.setClickable(true);
    String finalLink = link;
    msgContentFrame.setOnClickListener(new View.OnClickListener() {
    @Override
    public void onClick(View v) {
    Intent intent = new Intent();
    intent.setAction("android.intent.action.VIEW");
    Uri content_url = Uri.parse(finalLink);
    intent.setData(content_url);
    intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
    TUIChatService.getAppContext().startActivity(intent);
    }
    });
    
    msgContentFrame.setOnLongClickListener(new View.OnLongClickListener() {
    @Override
    public boolean onLongClick(View v) {
    if (onItemLongClickListener != null) {
    onItemLongClickListener.onMessageLongClick(v, position, msg);
    }
    return false;
    }
    });
    }

    Register the custom message type

    In the initMessageType method in the TUIChatService.java file, call the addCustomMessageType method to register the custom message. Sample code:
    private void initMessageType() {
    addCustomMessageType("text_link", // Unique ID of the custom message (Duplicate IDs are not allowed.)
    CustomLinkMessageBean.class); // MessageBean type of the message, which is the MessageBean class created in step 1
    }
    In the initMessage method in the ClassicUIService.java file, call the addMessageType method to register the mapping between the custom message type and message layout.
    Sample code:
    public void initMessage() {
    addMessageType(CustomLinkMessageBean.class, // MessageBean type of the message, which is the MessageBean class created in step 1
    CustomLinkMessageHolder.class); // MessageViewHolder type of the message, which is the MessageViewHolder class created in step 2
    }

    Sending Custom Messages

    As the figure below shows, the custom message sending button consists of a text title and an image icon.
    
    
    1. Add code to the customizeChatLayout method in ChatLayoutSetting.java to add the custom message sending button. Sample code:
    InputMoreActionUnit unit = new InputMoreActionUnit() {};
    unit.setIconResId(R.drawable.custom);
    unit.setTitleId(R.string.test_custom_action);
    unit.setActionId(CustomHelloMessage.CUSTOM_HELLO_ACTION_ID);
    unit.setPriority(10);
    inputView.addAction(unit);
    2. Configure click listening for the custom message sending button. Then, when the message sending button is clicked, a custom message is created and sent. A custom message is a piece of JSON data. You need to define the businessID field in JSON to uniquely identify the message type. Sample code:
    unit.setOnClickListener(unit.new OnActionClickListener() {
    @Override
    public void onClick() {
    Gson gson = new Gson();
    CustomHelloMessage customHelloMessage = new CustomHelloMessage();
    customHelloMessage.businessID = "text_link";
    customHelloMessage.text = "Welcome to Tencent Cloud Chat group";
    customHelloMessage.link = "https://www.tencentcloud.com/document/product/269/3794?from_cn_redirect=1";
    String data = gson.toJson(customHelloMessage);
    TUIMessageBean info = ChatMessageBuilder.buildCustomMessage(data, customHelloMessage.text, customHelloMessage.text.getBytes());
    layout.sendMessage(info, false);
    }
    });
    
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support