Threaded chat support for NodeBB

[phenomlab]

Following on from the “Threaded post support for NodeBB” topic below

Loading...

Please wait while the description loads.

Loading...

I am delighted to now announce something “similar” for chat See below - forgive the blurred image - it’s set that way intentionally to maintain privacy for individual members, but it’s enough for you to see the flow

This specific code is less complex than posts as there is “less to target” in terms of actual elements, and less global positioning of other elements to take into consideration. Without further ado…

Loading...

Please wait while the description loads.

Loading...

You’ll need to copy the content of style.css and paste this into ACP->/admin/appearance/customise, and also the content of functions.js into ACP->/admin/appearance/customise#custom-js

IMPORTANT

For this to work as intended, you need a temporary patch file which is discussed here

Loading...

Please wait while the description loads.

Loading...

And the actual file itself here

Loading...

Please wait while the description loads.

Loading...

This new hook does not exist pre 3.5.0 and will need to be added manually to your existing NodeBB core, then rebuild, and restart.

If you don’t want to modify the core, then you can comment out (or remove) the below lines of functions.js but then you will lose the ability to convert to threaded chat when new data is added to the DOM

$(window).on('action:chat.onMessagesAddedToDom', function(data) {
        	$(document).ready(function() { 
    	    console.log('hook triggered'); 
        threadedChat();
});
});

You may also land up with an error in the console which could result in the remainder of the site not loading properly if either the core patch is not applied, or the above lines removed.

As soon as 3.5.0 is released, this hook will be there by default and no longer needs to be added.

Finally, if you are using chatBanner then you will need this updated function

Loading...

Please wait while the description loads.

Loading...

[DownPW]

Another crazy job from our favorite dev

Test this now on dev

Many thanks

[DownPW]

I’m a tester with stock harmony

I have not change color or var for the moment.

RESULT:

It seems that the system event messages are not in the loop.

I note the following things too:

• The backgrounds on the left and on the home page are impacted too.

• The backgrounds remain even if you deactivate the view via the button.

[phenomlab]

@DownPW said in Threaded chat support for NodeBB:

It seems that the system event messages are not in the loop.

Yes, because you have to use the updated chatBanner as per the first post. Not sure what’s happening otherwise and I’ll be to check this on my stock harmony dev install. It was developed for sudonix, so that’s probably why.

I’ll revert over the weekend with an update.

[DownPW]

No problem

just for information, I have updated chatBanner function.

I search for the moment

[phenomlab]

Code in GIT has been updated to work with stock Harmony theme. If you’ve already used the code previous to this post, please remove all of it and replace with this new code. You still need to apply the pre 3.5.0 patch, and will of course need all of the css, plus the function itself.

Demo below

[cagatay]

@phenomlab i also should copy/paste git codes?
i have a problem chat area…

[phenomlab]

@cagatay Yes, you should. The problem in the chat area is because you haven’t updated the chatBanner function as I mentioned.

[cagatay]

what is your git adress for it?

[phenomlab]

@cagatay it’s in the first post

Loading...

Please wait while the description loads.

Loading...

[cagatay]

thank you did it, but there is a small problem, button is transparented and do not seem.

[phenomlab]

@cagatay this is because your are using the sudonix theme which isn’t stock Harmony which this post is designed for.

You will need custom CSS to resolve this which is why I am reluctant to provide the sudonix code and associated themes because of the issues it will cause further down the line when you attempt to use add-on code that is not designed for direct usage, but for stock Harmony.

[DownPW]

hello @phenomlab

Test the last code.
Working very well, definitively better

Notice the bug for system event persist even having updated the chat banner code

And other question : I see that there is no border for the arrows, can we add some like this ?

[phenomlab]

@DownPW Yep. Let me have a quick look.

[phenomlab]

@DownPW said in Threaded chat support for NodeBB:

And other question : I see that there is no border for the arrows, can we add some like this ?

This is actually a lot more complex than it looks - mostly because you cannot draw an additional border around the pseudo element because one already exists. It’s still possible, with the below changes

[data-self="1"].threaded {
    /* box-shadow: 0 0.5rem 1rem rgba(0, 0, 0, 0.15) !important; */
}
[data-self="0"].threaded {
    /* box-shadow: 0 0.5rem 1rem rgba(0, 0, 0, 0.15) !important; */
}
 
[data-self="1"].threaded {
    border: 1px solid var(--bs-border-color);
}
[data-self="0"].threaded {
    border: 1px solid var(--bs-border-color);  
}
[data-self="0"].threaded::before {
    border-color: transparent var(--bs-border-color) transparent transparent !important;
}
[data-self="0"].threaded:after {
    content: " ";
    position: absolute;
    top: 20px;
    z-index: 2;
    border: 15px solid var(--bs-body-bg);
    border-color: transparent var(--bs-body-bg) transparent transparent !important;
    left: -14px;
    border-width: 15px 15px 15px 0;
}
[data-self="1"].threaded::before {
border-color: transparent transparent transparent var(--bs-border-color) !important;
}
[data-self="1"].threaded:after {
    content: " ";
    position: absolute;
    top: 20px;
    z-index: 2;
    border: 15px solid var(--bs-body-bg);
    border-color: transparent transparent transparent var(--bs-body-bg) !important;
    right: -29px;
    border-width: 15px 15px 15px 0;
    border: 15px solid var(--bs-body-bg);
}

Obviously, we are removing the box-shadow directive here and replacing it with a border. Then we need to add :after pseudo elements to “overlay” the :before to create the transparent background. This then yields the below effect

If you want to go cheap, you could skip this CSS altogether, and just use a background on the [data-self="0"].threaded and [data-self="1"].threaded elements - as long as it is the same color as the border, it’ll be fine.

For example

[data-self="1"].threaded {
    /* box-shadow: 0 0.5rem 1rem rgba(0, 0, 0, 0.15) !important; */
    background: var(--bs-body-navbar);
}
[data-self="0"].threaded {
    /* box-shadow: 0 0.5rem 1rem rgba(0, 0, 0, 0.15) !important; */
    background: var(--bs-body-navbar);
}
[data-self="0"].threaded::before {
    border-color: transparent var(--bs-body-navbar) transparent transparent !important;
}
[data-self="1"].threaded::before {
    border-color: transparent transparent transparent var(--bs-body-navbar) !important;
}

This would yield

As you can see, it’s a lot less effort to not include any borders. However, there are some great examples shown here - it really depends on how complex you want it to be

Loading...

Please wait while the description loads.

Loading...

[phenomlab]

@DownPW said in Threaded chat support for NodeBB:

Notice the bug for system event persist even having updated the chat banner code

I cannot replicate this on your dev environment.

[DownPW]

hmmm strange same things in incognito mode.
Have you tets to go here :

[phenomlab]

@DownPW Wait - I see it now - wrong room

Try this

[component="chat/system-message"] {
    clear: both;
}

[DownPW]

Definitively better, you can add it to git

In any case, enormous work and as usual : many thanks
I think my users will be happy to have this functionality !!!

[phenomlab]

@DownPW said in Threaded chat support for NodeBB:

I think my users will be happy to have this functionality !!!

Yes, I think this makes chat so much easier to navigate.