Skip to content

Material View Support for Stock NodeBB

Unsolved Let's Build It
51 3 16.4k 1
  • better with video :

    blink3.gif

    @DownPW You’re missing a hook 🙂

    I’ve added this

    $(window).on('action:topics.loaded', function (data) {
        material();
    });
    
    

    Works now !

  • @phenomlab said in Material View Support foir Stock NodeBB:

    @DownPW Did you review the classes as I mentioned?

    yes but added the wrong class name, it’s better now.

    I’m here at the moment.

    JS :

    // ------------------------------------------
    // material View Mode
    // ------------------------------------------
    
    function material() {
        $(document).ready(function () {
            // Check if the screen width is 460px or more
            if ($(window).width() >= 460) {
                // Check if the custom thread view button already exists
                if ($('#materialThreadViewButton').length === 0) {
                    // Create the button for custom thread view mode with custom IDs
                    var threadViewButton = $('<div class="material-threads-wrapper"><form class="form"><div class="form-check form-switch material-threads-wrapper"> \
                        <input class="form-check-input" id="materialThreadViewButton" type="checkbox" data-field="materialThreadView"> \
                        <label class=" d-none d-md-inline fw-semibold" for="materialThreadViewButton"></label> \
                    </div></form></div>');
                    
                    // Append the button to the right sidebar
                    $('[component="sidebar/right"]').append(threadViewButton);
                }
                
                // Check if there's a stored state for the checkbox and update it
                var storedState = localStorage.getItem('materialThreadViewState');
                if (storedState === 'true') {
                    $('#materialThreadViewButton').prop('checked', true);
                }
                
                // Toggle the class 'material' on or off when the checkbox changes state
                $('#materialThreadViewButton').on('change', function () {
                    var isChecked = $(this).is(':checked');
                    var theTooltip = isChecked ? "Material Thread View Off" : "Material Thread View On"; // Update tooltip message
                    
                    // Toggle CSS rules when the button is turned on or off
                    if (isChecked) {
                        console.log('Material Thread view is active.');
                        // Apply your CSS rules here
                        $('[component=post]').addClass('material'); 
                        $('[component="category/topic"]').addClass('material'); 
                        $('[component="categories/category"]').addClass('material');
                    } else {
                        console.log('Material Thread view is inactive.');
                        // Remove the CSS rules here
                        $$('[component=post]').removeClass('material');
                        $('[component="category/topic"]').removeClass('material');
                        $('[component="categories/category"]').removeClass('material');
                    }
                    
                    // Store the checkbox state in localStorage
                    localStorage.setItem('materialThreadViewState', isChecked);
                    
                    // Update the tooltip title
                    $(this).attr('data-original-title', theTooltip).tooltip('dispose').tooltip({
                        placement: 'bottom',
                        title: theTooltip,
                        trigger: 'hover'
                    });
                });
    
                // Check for changes in the checkbox state when the page loads
                $('#materialThreadViewButton').trigger('change');
            }
        });
    }
    
    // Attach the material function to relevant events
    $(window).on('action:ajaxify.end', function (data) {
        material();
    });
    
    $(window).on('action:posts.edited', function (data) {
        material();
    });
    
    $(window).on('action:posts.loaded', function (data) {
        material();
    });
    

    CSS :

    .material-threads-wrapper {
        display: flex;
        left: 5px !important;
        position: relative !important;
    }
    
    @media (min-width:460px) {
    
    [component=post].material, [component="category/topic"].material, [component="categories/category"].material { 
        background: #F7F7F7 !important;
        border-radius: 0.375rem;
        margin-bottom: 20px;
        padding-left: 20px;
        border: 1px solid var(--bs-border-color);
    }
    
    }
    

    – There are quite a few things left, for example:

    • if we scan the recent or unread ones, the rest is not in the background :

    f3fe08cf-fbc1-4f47-8497-866557c4ec25-image.png

    • And the block + timeline in the topics :
      35beb3bc-8871-4689-b31c-cd2c489907a4-image.png

    I would also like to change the button which is not suitable for a vertical display

    For the moment, I haven’t found for all of that but I’m looking for.

    @DownPW said in Material View Support foir Stock NodeBB:

    I would also like to change the button which is not suitable for a vertical display

    You could rotate it?

    .material-threads-wrapper {
        display: flex;
        left: 5px !important;
        position: relative !important;
        transform: rotate(45deg);
        margin-left: -2px;
        margin-top: 5px;
    }
    

    fc9f46cc-2235-47fe-a613-3baa9d5aa436-image.png

  • @DownPW could you pls share updated and enclosed codes for css and js?

  • @cagatay The code is not mature yet. There is still work to be done and phenomlab will have to validate it because I am not a developer

    @phenomlab said in Material View Support foir Stock NodeBB:

    You could rotate it?

    yep sure it’s better 🙂
    but I was thinking of a 2-state radio button like the form-switch because I believe Bootstrap offers it if I don’t say bullsh*t.

  • @cagatay The code is not mature yet. There is still work to be done and phenomlab will have to validate it because I am not a developer

    @phenomlab said in Material View Support foir Stock NodeBB:

    You could rotate it?

    yep sure it’s better 🙂
    but I was thinking of a 2-state radio button like the form-switch because I believe Bootstrap offers it if I don’t say bullsh*t.

    @DownPW said in Material View Support foir Stock NodeBB:

    but I was thinking of a 2-state radio button like the form-switch because I believe Bootstrap offers it if I don’t say bullsh*t.

    Something like this?

    https://jsfiddle.net/milanandfriends/p9AaY/

  • yes maybe, I had thought about that but just one button not two but why not :

    image.png

    https://getbootstrap.com/docs/5.0/forms/checks-radios/

    I’m not closed off I’m trying to see what could be better.

  • see this @phenomlab

    the element is perfect regardless of the mode engaged but a refresh does not replace it correctly.
    A missing hook?

  • see this @phenomlab

    the element is perfect regardless of the mode engaged but a refresh does not replace it correctly.
    A missing hook?

    @DownPW No. More likely a CSS class is not being applied on load.

  • hmm that doesn’t help me much 🙂

  • hmm that doesn’t help me much 🙂

    @DownPW Add this to your existing css class of

    .page-topic .topic .posts.timeline [component="topic/event"].timeline-event, .page-topic .topic .posts.timeline [component="topic/necro-post"].timeline-event
    
        margin-left: 52px;
    

    So you land up with

    .page-topic .topic .posts.timeline [component="topic/event"].timeline-event, .page-topic .topic .posts.timeline [component="topic/necro-post"].timeline-event {
        margin-bottom: 10px;
        margin-left: 52px;
    }
    

    That will fix it.

  • no it’s worse 🙂

    Maybe, the best would be to add a .material class but I can’t do it at the moment

  • no it’s worse 🙂

    Maybe, the best would be to add a .material class but I can’t do it at the moment

    @DownPW I remember this same issue now when I came across it whilst writing the threaded function. The problem here is that [component="topic/necro-post"] actually isn’t present in the DOM on page load, but added afterwards. This is why once the page has loaded, you can target the element with the toggle switch because it is in the DOM at the time. Because the this specific element is loaded afterwards, you cannot target it if it doesn’t exist.

    This effectively means you cannot add a class to an element that is not there. To work around this, you’d either have to wait for the page to load, add the necro element, then target it.

    Or, use the CSS I provided, and then “counter” it using other CSS when the class is removed. This is what I do in thwe threaded function.

    Raised this as an issue here

    https://community.nodebb.org/topic/17590/necro-function-dom-changes

    EDIT - should work now 🙂

    I’ve added a loop in your material function that looks specifically for the necro post

    $('[component="topic/necro-post"]').each(function () {
         // Add the 'material' class to matching elements
         if ($(this).hasClass('timeline-event')) {
         $(this).addClass('material');
         }
     });
    

    And also (on the advice of Baris) added a new hook as below

    $(window).on('action:topic.loaded', function (data) {
        material();
    });
    

    There are two separate hooks that look very much the same, but do different things (one has an “s” at the end, whilst the other doesn’t - “action:topic.loaded” and “action:topic%(#fa0000)[s].loaded”

    Now it works as intended 🙂

  • ohh yes better 🙂

    I undersxtand for adding .each(function () for [component=“topic/necro-post”]

    I have read the thread on nodeBB communauty. On the other hand, I don’t really understand the difference for the hook in topic and topicS

  • ohh yes better 🙂

    I undersxtand for adding .each(function () for [component=“topic/necro-post”]

    I have read the thread on nodeBB communauty. On the other hand, I don’t really understand the difference for the hook in topic and topicS

    @DownPW I think the difference is that the topic hook is for single, and topics for a selection. Makes sense, but not very well explained in the documentation!

  • Thanks for explain. Make sense, indeed but it’s not easy to know without Baris help 🙂


    Still with the idea of improving the code, I’m going to focus now on making the selection button appear on Smartphone.

    Indeed, currently, it does not appear because it seems that on Smartphone another component is used

    b46c3d29-7f77-4f85-b207-790f2f10378b-image.png

    10d1925e-fad1-42e0-b209-12fcc9dc6ca5-image.png

  • I test this :

    // ------------------------------------------
    // material View Mode
    // ------------------------------------------
    
    function material() {
        $(document).ready(function () {
            var $buttonContainer = null;
    
            // Check if the screen width is 460px or more
            if ($(window).width() >= 991) {
                // Check if the custom thread view button already exists in the right sidebar
                $buttonContainer = $('[component="sidebar/right"]');
            } if ($(window).width() <= 991) {
                // Check if the custom thread view button already exists in the bottom bar
                $buttonContainer = $('[component="bottombar"]');
    
            }
    
    
  • I test this :

    // ------------------------------------------
    // material View Mode
    // ------------------------------------------
    
    function material() {
        $(document).ready(function () {
            var $buttonContainer = null;
    
            // Check if the screen width is 460px or more
            if ($(window).width() >= 991) {
                // Check if the custom thread view button already exists in the right sidebar
                $buttonContainer = $('[component="sidebar/right"]');
            } if ($(window).width() <= 991) {
                // Check if the custom thread view button already exists in the bottom bar
                $buttonContainer = $('[component="bottombar"]');
    
            }
    
    

    @DownPW yes, the same methodology is used for the theme switcher in NodeBB v2.x 😀

  • ohh yes, don’t see that to be honest.

    Button appear but hard to position it correctly for all resolution.
    The button moves according to the resolution. it is not fixed

  • ohh yes, don’t see that to be honest.

    Button appear but hard to position it correctly for all resolution.
    The button moves according to the resolution. it is not fixed

    @DownPW if you use apend then it should reflect the div it is inserted into.

    The version of the theme switcher from the NodeBB v2 series used the same mechanism, and that code is still listed in this forum. It would be a good idea to review that code for inspiration as the placement for the switcher drop down was set depending on screen estate.

  • @DownPW this should provide the functionality you are looking for

    // ------------------------------------------
    // material View Mode
    // ------------------------------------------
    function material() {
        $(document).ready(function () {
                // Create the button for custom thread view mode with custom IDs
                if ($('#materialThreadViewButton').length === 0) {
                    var threadViewButton = $('<div class="material-threads-wrapper"><form class="form"><div class="form-check form-switch form-switch-sm material-threads-wrapper"> \
                        <input class="form-check-input" id="materialThreadViewButton" type="checkbox" data-field="materialThreadView"> \
                        <label class=" d-none d-md-inline fw-semibold" for="materialThreadViewButton"></label> \
                    </div></form></div>');
                    
                            // Check if the screen width is 460px or more
            if ($(window).width() >= 991) {
                // Check if the custom thread view button already exists in the right sidebar
                var buttonContainer = $('[component="sidebar/right"]');
                // Append the button to the selected container
                buttonContainer.append(threadViewButton);
            } 
            if ($(window).width() <= 991) {
                // Check if the custom thread view button already exists in the bottom bar
                //$buttonContainer = $('.bottombar-nav.p-2.text-dark.bg-light.d-flex.justify-content-between.align-items-center.w-100');
                if ($("#logged-in-menu").length > 0) {
                var buttonContainer = $('.bottombar-nav ul#logged-in-menu');
                }
                else {
                    var buttonContainer = $('.bottombar-nav ul#logged-out-menu'); 
                }
                            // Prepend the button to the selected container
                buttonContainer.prepend(threadViewButton);
            }
                }
                // Check if there's a stored state for the checkbox and update it
                var storedState = localStorage.getItem('materialThreadViewState');
                console.log("Stored State is " + storedState);
                if (storedState === 'true') {
                    $('#materialThreadViewButton').prop('checked', true);
                }
                
                // Toggle the class 'material' on or off when the checkbox changes state
                $('#materialThreadViewButton').on('change', function () {
                    var isChecked = $(this).is(':checked');
                    var theTooltip = isChecked ? "Material View Off" : "Material View On"; // Update tooltip message
                    
                    // Toggle CSS rules when the button is turned on or off
                    if (isChecked) {
                        console.log('Material Thread view is active.');
                        // Apply your CSS rules here
                        $('[component="category/topic"]').addClass('material'); 
                        $('li[component="category/topic"]').addClass('material'); 
                        $('[component="categories/category"]').addClass('material');
                        
                        $('.posts-container').addClass('material')
                        $('ul[component="topic"]').addClass('material')
                        $('.post-container').addClass('material')
                        $('.timeline-event').addClass('material')
                        $('[component="post/footer"]').addClass('material')
                        $('li.pt-4.deleted').addClass('material') 
                        
                        $('.page-topic .topic .posts.timeline .timeline-event > div:first-of-type, .page-topic .topic .posts.timeline > [component="post/placeholder"] > div:first-of-type, .page-topic .topic .posts.timeline > [component=post] > div:first-of-type').addClass('material');
    
                        $('[component="post"]').each(function () {
                            // Add the 'material' class to matching elements
                            if ($(this).hasClass('pt-4') || $(this).hasClass('self-post')) {
                                $(this).addClass('material');
                                $('[component="sidebar/right"]').addClass('material');
                            }
                        });
                        $('[component="topic/necro-post"]').each(function () {
                            // Add the 'material' class to matching elements
                            if ($(this).hasClass('timeline-event')) {
                                $(this).addClass('material');
                            }
                        });
    
                    } else {
                        console.log('Material Thread view is inactive.');
                        // Remove the CSS rules here
                        $('[component="category/topic"]').removeClass('material');
                        $('li[component="category/topic"]').removeClass('material');
                        $('[component="categories/category"]').removeClass('material');
                        
                        $('[component="post"]').removeClass('material');
                        $('ul[component="topic"]').removeClass('material');
                        $('.posts-container').removeClass('material')
                        $('ul[component="topic"]').removeClass('material')
                        $('.post-container').removeClass('material')
                        $('.timeline-event').removeClass('material')
                        $('[component="post/footer"]').removeClass('material');
                        $('li.pt-4.deleted').removeClass('material'); 
                       
                        $('.page-topic .topic .posts.timeline .timeline-event > div:first-of-type, .page-topic .topic .posts.timeline > [component="post/placeholder"] > div:first-of-type, .page-topic .topic .posts.timeline > [component=post] > div:first-of-type').removeClass('material'); 
    
                        $('[component="sidebar/right"]').removeClass('material');
                        
                    }
                    
                    // Store the checkbox state in localStorage
                    localStorage.setItem('materialThreadViewState', isChecked);
                    
                    // Update the tooltip title
                    $(this).attr('data-original-title', theTooltip).tooltip('dispose').tooltip({
                        placement: 'bottom',
                        title: theTooltip,
                        trigger: 'hover'
                    });
                });
    
                // Check for changes in the checkbox state when the page loads
                $('#materialThreadViewButton').trigger('change');
            
        });
    }
    

    Result

    6246743e-a9dd-40e3-b07f-5a69f6e54002-image.png

    I ddjusted some of your CSS - added this block

    #logged-out-menu .material-threads-wrapper {
        top: 5px;
        position: relative;
    }
    

    Also removed this block

    #materialThreadViewButton {
    }
    

    Not needed 🙂

    There are are two checks - one tests the screen estate and positions the menu item depending on size, and the other will see if the user is logged in or not, and if they are, it uses ul#menu-logged-in else it uses ul#menu-logged-out

    But only for the mobile view because .bottom-bar is based on both logged in and logged out sessions

    Enjoy


Related Topics
  • 50 Votes
    107 Posts
    34k Views
    @crazycells [image: 1711908210287-7f4c7193-7c28-4e2e-80e8-d439ac7285c6-image.png] [image: 1711908232109-3ab9c33d-04b9-4c15-91e6-891450aebfc2-image.png]
  • The theme came with space on left side

    Solved WordPress css
    7
    3 Votes
    7 Posts
    2k Views
    @phenomlab yes it’s a different theme. The other one was not offering much on editable sidebar. It was like flarum hahah
  • Rotating Star Effect

    Solved Let's Build It wordpress css
    17
    12 Votes
    17 Posts
    3k Views
    @phenomlab thanks a lot for these, both of the below are awesome! https://codepen.io/bennettfeely/pen/vYLmYJz https://codepen.io/C-L-the-selector/pen/MWZbWBo
  • hover link effect

    Solved Customisation css link hover
    18
    1
    6 Votes
    18 Posts
    4k Views
    @DownPW Looking at the underlying code, class start is being added on hover by jQuery in this function document.querySelectorAll(".button-gradient, .button-transparent").forEach((button) => { const style = getComputedStyle(button); const lines = document.createElement("div"); lines.classList.add("lines"); const groupTop = document.createElement("div"); const groupBottom = document.createElement("div"); const svg = createSVG( button.offsetWidth, button.offsetHeight, parseInt(style.borderRadius, 10) ); groupTop.appendChild(svg); groupTop.appendChild(svg.cloneNode(true)); groupTop.appendChild(svg.cloneNode(true)); groupTop.appendChild(svg.cloneNode(true)); groupBottom.appendChild(svg.cloneNode(true)); groupBottom.appendChild(svg.cloneNode(true)); groupBottom.appendChild(svg.cloneNode(true)); groupBottom.appendChild(svg.cloneNode(true)); lines.appendChild(groupTop); lines.appendChild(groupBottom); button.appendChild(lines); button.addEventListener("pointerenter", () => { button.classList.add("start"); }); svg.addEventListener("animationend", () => { button.classList.remove("start"); }); }); }) The CSS for start is below .button-gradient.start .lines svg, .button-transparent.start .lines svg { animation: stroke 0.3s linear; } And this is the corresponding keyframe @keyframes stroke { 30%, 55% { opacity: 1; } 100% { stroke-dashoffset: 5; opacity: 0; } } It’s using both CSS and SVG, so might not be a simple affair to replicate without the SVG files.
  • [NODEBB] Reply Button/arrow answer

    Solved Customisation css nodebb
    25
    4
    4 Votes
    25 Posts
    8k Views
    Topic open https://sudonix.com/topic/207/nodebb-help-for-my-custom-css
  • [NODEBB] Welcome Message

    Solved Customisation css html nodebb
    20
    2
    13 Votes
    20 Posts
    7k Views
    @DownPW the ‘js’ code for the banner takes the time from the client, so what it displays really depends on the regional settings for the operating system. I’ve not seen this issue myself but would like to see some examples of screenshots if possible.
  • Avatar on Topic Header

    Solved Customisation css avatar header
    9
    1
    0 Votes
    9 Posts
    2k Views
    @jac said in Avatar on Topic Header: @downpw said in Avatar on Topic Header: Great Plugin I make it a bit cleaner via this CSS code: /*------------------------------------------------------------------*/ /*---------------- nodebb-plugin-browsing-users -----------------*/ /*------------------------------------------------------------------*/ /*Space between the avatar and the RSS icon */ .topic [component="topic/browsing-users"] { margin-bottom: -5px; padding-left: 10px; } /*Space between avatars*/ .pull-left { float: left!important; padding-right: 5px; } Do you have a screenshot of how this looks with the CSS change? Just added this change, thanks @DownPW
  • CSS Help on my Flarum

    Solved Customisation
    5
    2
    2 Votes
    5 Posts
    2k Views
    @mike-jones Yes, you’ll typically see this type of behaviour if there is another style that has higher priority in the sense that yours will be overridden. Using !important will override the higher preference, but should be used sparingly rather than everywhere.