I've been experimenting with an option in overboard to display recent articles by thread.

I did this in the past, but it wasn't so great, so trying again. I'm still testing, but if you want to take a look, it's running on www.novabbs.org now:
https://news.novabbs.org/computers/overboard.php?thisgroup=news.software.nntp

The thread vs. flat display will be a toggle in overrides.inc.php (with a default, of course)

I'm still testing, so no commit yet.

--
Retro Guy

Retro Guy wrote:

> I've been experimenting with an option in overboard to display recent articles by thread.

> I did this in the past, but it wasn't so great, so trying again. I'm still testing, but if you want to take a look, it's running on www.novabbs.org now:
> https://news.novabbs.org/computers/overboard.php?thisgroup=news.software.nntp

> The thread vs. flat display will be a toggle in overrides.inc.php (with a default, of course)

> I'm still testing, so no commit yet.

I've improved the sorting, removed duplicate display of article that starts a thread, and added a toggle to display 'Thread' or 'Article' view. The toggle will remain with your session, and if you are logged in, will become your default view.

Hopefully, I can add a commit later today or tomorrow. I'm still trying to find bugs, but I'm sure once I commit I'll start to find them all :)

--
Retro Guy

Retro Guy wrote:

> Retro Guy wrote:

>> I've been experimenting with an option in overboard to display recent articles by thread.

>> I did this in the past, but it wasn't so great, so trying again. I'm still testing, but if you want to take a look, it's running on www.novabbs.org now:
>> https://news.novabbs.org/computers/overboard.php?thisgroup=news.software.nntp

>> The thread vs. flat display will be a toggle in overrides.inc.php (with a default, of course)

>> I'm still testing, so no commit yet.

> I've improved the sorting, removed duplicate display of article that starts a thread, and added a toggle to display 'Thread' or 'Article' view. The toggle will remain with your session, and if you are logged in, will become your default view.

> Hopefully, I can add a commit later today or tomorrow. I'm still trying to find bugs, but I'm sure once I commit I'll start to find them all :)

Well, I got sorting sorted. HAHHAHAHA! (Yes, I'm all alone in a room and may have lost my mind)

Anyway, I have pushed a commit for the new overboard. If you don't create a default in overrides,inc.php, it will default to the original flat articles view. There is a toggle (radio buttons) on the overboard for a user to change that, and it will remain changed for that user.

--
Retro Guy

On Fri, 26 Apr 2024 12:18:08 +0000, Retro Guy wrote:

> Retro Guy wrote:
>
>> Retro Guy wrote:
>
>>> I've been experimenting with an option in overboard to display recent articles by thread.
>
>>> I did this in the past, but it wasn't so great, so trying again. I'm still testing, but if you want to take a look, it's running on www.novabbs.org now:
>>> https://news.novabbs.org/computers/overboard.php?thisgroup=news.software.nntp
>
>>> The thread vs. flat display will be a toggle in overrides.inc.php (with a default, of course)
>
>>> I'm still testing, so no commit yet.
>
>> I've improved the sorting, removed duplicate display of article that starts a thread, and added a toggle to display 'Thread' or 'Article' view. The toggle will remain with your session, and if you are logged in, will become your default view.
>
>> Hopefully, I can add a commit later today or tomorrow. I'm still trying to find bugs, but I'm sure once I commit I'll start to find them all :)
>
> Well, I got sorting sorted. HAHHAHAHA! (Yes, I'm all alone in a room and may have lost my mind)
>
> Anyway, I have pushed a commit for the new overboard. If you don't create a default in overrides,inc.php, it will default to the original flat articles view. There is a toggle (radio buttons) on the overboard for a user to change that, and it will remain changed for that user.

Just added support for user blocklist (hiding users)

On Fri, 26 Apr 2024 12:18:08 +0000
Retro Guy <retroguy@novabbs.com> wrote:

> Retro Guy wrote:
>
> > Retro Guy wrote:
>
> >> I've been experimenting with an option in overboard to display recent articles by thread.
>
> >> I did this in the past, but it wasn't so great, so trying again. I'm still testing, but if you want to take a look, it's running on www.novabbs.org now:
> >> https://news.novabbs.org/computers/overboard.php?thisgroup=news.software.nntp
>
> >> The thread vs. flat display will be a toggle in overrides.inc.php (with a default, of course)
>
> >> I'm still testing, so no commit yet.
>
> > I've improved the sorting, removed duplicate display of article that starts a thread, and added a toggle to display 'Thread' or 'Article' view. The toggle will remain with your session, and if you are logged in, will become your default view.
>
> > Hopefully, I can add a commit later today or tomorrow. I'm still trying to find bugs, but I'm sure once I commit I'll start to find them all :)
>
> Well, I got sorting sorted. HAHHAHAHA! (Yes, I'm all alone in a room and may have lost my mind)
>
> Anyway, I have pushed a commit for the new overboard. If you don't create a default in overrides,inc.php, it will default to the original flat articles view. There is a toggle (radio buttons) on the overboard for a user to change that, and it will remain changed for that user.
>
> --
> Retro Guy

Suggestion: place an interface button for each of the different views, with the option for admin to set one as default or even hide this that or the other.

Perhaps something like this would make sense: OVERBOARD | THREADED | SINGLE | FUTURE?

This would allow you to separate all views into separate PHP template files going forward.

--
www.sybershock.com | sci.crypt | alt.sources.crypto | alt.lite.bulb

SugarBug wrote:

> On Fri, 26 Apr 2024 12:18:08 +0000
> Retro Guy <retroguy@novabbs.com> wrote:

>> Retro Guy wrote:
>>
>> > Retro Guy wrote:
>>
>> >> I've been experimenting with an option in overboard to display recent articles by thread.
>>
>> >> I did this in the past, but it wasn't so great, so trying again. I'm still testing, but if you want to take a look, it's running on www.novabbs.org now:
>> >> https://news.novabbs.org/computers/overboard.php?thisgroup=news.software.nntp
>>
>> >> The thread vs. flat display will be a toggle in overrides.inc.php (with a default, of course)
>>
>> >> I'm still testing, so no commit yet.
>>
>> > I've improved the sorting, removed duplicate display of article that starts a thread, and added a toggle to display 'Thread' or 'Article' view. The toggle will remain with your session, and if you are logged in, will become your default view.
>>
>> > Hopefully, I can add a commit later today or tomorrow. I'm still trying to find bugs, but I'm sure once I commit I'll start to find them all :)
>>
>> Well, I got sorting sorted. HAHHAHAHA! (Yes, I'm all alone in a room and may have lost my mind)
>>
>> Anyway, I have pushed a commit for the new overboard. If you don't create a default in overrides,inc.php, it will default to the original flat articles view. There is a toggle (radio buttons) on the overboard for a user to change that, and it will remain changed for that user.
>>
>> --
>> Retro Guy

> Suggestion: place an interface button for each of the different views, with the option for admin to set one as default or even hide this that or the other.

> Perhaps something like this would make sense: OVERBOARD | THREADED | SINGLE | FUTURE?

> This would allow you to separate all views into separate PHP template files going forward.

I'm trying to grasp what you mean. Currently, the user can choose between 'Articles' (flat), or 'Threads'. Once they choose, it sticks to their Session, and if logged in, is written to their config.

overrides.inc.php contains a setting to choose the default view for the site.

I think you're adding the ability to remove an option from the choices on the overboard (radio buttons). Is that what you mean?

For different 'templates', each view is a separate function in overboard.php. I had to make one change to style.css (remove forcing date to the left), but other than that, the functions use the same stylesheet.

What, if anything, am I missing? (re-reading): Do you mean different overboard buttons? That might be messy as there are at least three ways to get to the overboard.

--
Retro Guy

On Fri, 26 Apr 2024 09:27:27 -0500
SugarBug <3883@sugar.bug> wrote:

> Suggestion: place an interface button for each of the different views, with the option for admin to set one as default or even hide this that or the other.
>
> Perhaps something like this would make sense: OVERBOARD | THREADED | SINGLE | FUTURE?
>
> This would allow you to separate all views into separate PHP template files going forward.

And then I looked at your site and saw you were already doing something like that with radio buttons ...

Are you eliminating the subject line only view?

--
www.sybershock.com | sci.crypt | alt.sources.crypto | alt.lite.bulb

On Fri, 26 Apr 2024 09:52:13 -0500, SugarBug wrote:

> On Fri, 26 Apr 2024 09:27:27 -0500
> SugarBug <3883@sugar.bug> wrote:
>
>> Suggestion: place an interface button for each of the different views, with the option for admin to set one as default or even hide this that or the other.
>>
>> Perhaps something like this would make sense: OVERBOARD | THREADED | SINGLE | FUTURE?
>>
>> This would allow you to separate all views into separate PHP template files going forward.
>
> And then I looked at your site and saw you were already doing something like that with radio buttons ...
>
> Are you eliminating the subject line only view?

The 'Articles' view is the old view with some minor "improvements" This is
the original layout (with the minor changes). I don't think there was a
view that only showed the subject line.

On Fri, 26 Apr 2024 14:52:13 +0000
Retro Guy <retroguy@novabbs.com> wrote:

> SugarBug wrote:
>
> > On Fri, 26 Apr 2024 12:18:08 +0000
> > Retro Guy <retroguy@novabbs.com> wrote:
>
> >> Retro Guy wrote:
> >>
> >> > Retro Guy wrote:
> >>
> >> >> I've been experimenting with an option in overboard to display recent articles by thread.
> >>
> >> >> I did this in the past, but it wasn't so great, so trying again. I'm still testing, but if you want to take a look, it's running on www.novabbs.org now:
> >> >> https://news.novabbs.org/computers/overboard.php?thisgroup=news.software.nntp
> >>
> >> >> The thread vs. flat display will be a toggle in overrides.inc.php (with a default, of course)
> >>
> >> >> I'm still testing, so no commit yet.
> >>
> >> > I've improved the sorting, removed duplicate display of article that starts a thread, and added a toggle to display 'Thread' or 'Article' view. The toggle will remain with your session, and if you are logged in, will become your default view.
> >>
> >> > Hopefully, I can add a commit later today or tomorrow. I'm still trying to find bugs, but I'm sure once I commit I'll start to find them all :)
> >>
> >> Well, I got sorting sorted. HAHHAHAHA! (Yes, I'm all alone in a room and may have lost my mind)
> >>
> >> Anyway, I have pushed a commit for the new overboard. If you don't create a default in overrides,inc.php, it will default to the original flat articles view. There is a toggle (radio buttons) on the overboard for a user to change that, and it will remain changed for that user.
> >>
> >> --
> >> Retro Guy
>
> > Suggestion: place an interface button for each of the different views, with the option for admin to set one as default or even hide this that or the other.
>
> > Perhaps something like this would make sense: OVERBOARD | THREADED | SINGLE | FUTURE?
>
> > This would allow you to separate all views into separate PHP template files going forward.
>
> I'm trying to grasp what you mean. Currently, the user can choose between 'Articles' (flat), or 'Threads'. Once they choose, it sticks to their Session, and if logged in, is written to their config.

I sent the message before I looked at your demo site. I didn't realize you already implemented the radio buttons until after I sent the first message.
> overrides.inc.php contains a setting to choose the default view for the site.
>
> I think you're adding the ability to remove an option from the choices on the overboard (radio buttons). Is that what you mean?

Yes, I was thinking that the views would show up as buttons like the former 'overboard' button. I just fired off my message before I saw the changes were already being demonstrated.
> For different 'templates', each view is a separate function in overboard.php. I had to make one change to style.css (remove forcing date to the left), but other than that, the functions use the same stylesheet.
>
> What, if anything, am I missing? (re-reading): Do you mean different overboard buttons? That might be messy as there are at least three ways to get to the overboard.

No, I was thinking buttons for each view you were proposing, and like you said earlier the ability for admin to hide any of them. But I already see you did the radio button control, which is basically the same thing in one control. I can probably use CSS display:none and visibility:hidden to hide controls at the theme level if that creates too much noise in the config files.

When playing with theme ideas I noticed duplicate class names for elements in the same table row.

In each table row, the class names of table elements repeat for the username and datebox elements. It would be much better for styling if the class names for each element were unique. For example, class='datebox_left', class='datebox_right', class='article_title', class=author_left', class='author_right', class='total_replies', etc. You can even leave the current class names in place as is, and add extra unique class names to the html output, so that they can be styled individually or as a unit. Keeping the old classes and adding new uniques alongside them would prevent breaking backward compatibility of themes.

Also I notice that when building the tables that each table row has alternating class names, 'np_thread_line1', 'np_thread_line2' and each of these class names is re-used in its same row. Something like 'np_thread_line_left_1', 'np_thread_line_center_1', 'np_thread_line_right_1' would make styling with CSS much easier. I think I need to separate header.inc and body html generation files then run search and replace on them and probably avoid 90% of the hand editing.

Basically the idea so that every element in a table row will have at least one class name that is unique or repeated in that row--and so that no class names used in the header and footer appear in the document body, or also the header and footer elements each have a unique class name so elements can be targeted individually there without much fuss. This allows a lot of cool CSS tricks for themes and responsive layout magic without having to resort to endless :nth-child() and selector strangeness. It would also make it much easier to use multiple web fonts with CSS to change fonts on selected elements in a theme. In my new theme I actually want to use two different fonts for table data elements that have the same class names.

Since I am working on a theme maybe I should send a patch for the php files showing what I mean regarding class names. I'm still wrapping my head around it so I'll check back in when I get time to dig in and finish the theme and test the changes before making a patch.

--
www.sybershock.com | sci.crypt | alt.sources.crypto | alt.lite.bulb

On Fri, 26 Apr 2024 17:14:06 -0500
SugarBug <3883@sugar.bug> wrote:

> Basically the idea so that every element in a table row will have at least one class name that is unique or repeated in that row

[sic] ...

unique or *non* repeated in that row

--
www.sybershock.com | sci.crypt | alt.sources.crypto | alt.lite.bulb

SugarBug wrote:

> On Fri, 26 Apr 2024 14:52:13 +0000
> Retro Guy <retroguy@novabbs.com> wrote:

>> SugarBug wrote:
>>
>> > On Fri, 26 Apr 2024 12:18:08 +0000
>> > Retro Guy <retroguy@novabbs.com> wrote:
>>
>> >> Retro Guy wrote:
>> >>
>> >> > Retro Guy wrote:
>> >>
>> >> >> I've been experimenting with an option in overboard to display recent articles by thread.
>> >>
>> >> >> I did this in the past, but it wasn't so great, so trying again. I'm still testing, but if you want to take a look, it's running on www.novabbs.org now:
>> >> >> https://news.novabbs.org/computers/overboard.php?thisgroup=news.software.nntp
>> >>
>> >> >> The thread vs. flat display will be a toggle in overrides.inc.php (with a default, of course)
>> >>
>> >> >> I'm still testing, so no commit yet.
>> >>
>> >> > I've improved the sorting, removed duplicate display of article that starts a thread, and added a toggle to display 'Thread' or 'Article' view. The toggle will remain with your session, and if you are logged in, will become your default view.
>> >>
>> >> > Hopefully, I can add a commit later today or tomorrow. I'm still trying to find bugs, but I'm sure once I commit I'll start to find them all :)
>> >>
>> >> Well, I got sorting sorted. HAHHAHAHA! (Yes, I'm all alone in a room and may have lost my mind)
>> >>
>> >> Anyway, I have pushed a commit for the new overboard. If you don't create a default in overrides,inc.php, it will default to the original flat articles view. There is a toggle (radio buttons) on the overboard for a user to change that, and it will remain changed for that user.
>> >>
<snip>

> When playing with theme ideas I noticed duplicate class names for elements in the same table row.

> In each table row, the class names of table elements repeat for the username and datebox elements. It would be much better for styling if the class names for each element were unique. For example, class='datebox_left', class='datebox_right', class='article_title', class=author_left', class='author_right', class='total_replies', etc. You can even leave the current class names in place as is, and add extra unique class names to the html output, so that they can be styled individually or as a unit. Keeping the old classes and adding new uniques alongside them would prevent breaking backward compatibility of themes.

I completely agree with this. Please understand that RSLight is the first time I had ever used css, so I was learning as I went. Both css and databases were new to me, so you can see that in the code. It does need to be cleaned up.

> Also I notice that when building the tables that each table row has alternating class names, 'np_thread_line1', 'np_thread_line2' and each of these class names is re-used in its same row. Something like 'np_thread_line_left_1', 'np_thread_line_center_1', 'np_thread_line_right_1' would make styling with CSS much easier. I think I need to separate header.inc and body html generation files then run search and replace on them and probably avoid 90% of the hand editing.

Yes, I agree with you.

> Basically the idea so that every element in a table row will have at least one class name that is unique or repeated in that row--and so that no class names used in the header and footer appear in the document body, or also the header and footer elements each have a unique class name so elements can be targeted individually there without much fuss. This allows a lot of cool CSS tricks for themes and responsive layout magic without having to resort to endless :nth-child() and selector strangeness. It would also make it much easier to use multiple web fonts with CSS to change fonts on selected elements in a theme. In my new theme I actually want to use two different fonts for table data elements that have the same class names.

I believe it is best to add the classes to css, then it can be modified in the code, if desired. We would leave all the existing classes alone for backward compat.

> Since I am working on a theme maybe I should send a patch for the php files showing what I mean regarding class names. I'm still wrapping my head around it so I'll check back in when I get time to dig in and finish the theme and test the changes before making a patch.

I think I get it, but feel free to demonstrate. It can't hurt :)

--
Retro Guy

Retro Guy wrote:

> SugarBug wrote:

>> On Fri, 26 Apr 2024 14:52:13 +0000
>> Retro Guy <retroguy@novabbs.com> wrote:

>>> SugarBug wrote:
>>>
>>> > On Fri, 26 Apr 2024 12:18:08 +0000
>>> > Retro Guy <retroguy@novabbs.com> wrote:
>>>
>>> >> Retro Guy wrote:
>>> >>
>>> >> > Retro Guy wrote:
>>> >>
>>> >> >> I've been experimenting with an option in overboard to display recent articles by thread.
>>> >>
>>> >> >> I did this in the past, but it wasn't so great, so trying again. I'm still testing, but if you want to take a look, it's running on www.novabbs.org now:
>>> >> >> https://news.novabbs.org/computers/overboard.php?thisgroup=news.software.nntp
>>> >>
>>> >> >> The thread vs. flat display will be a toggle in overrides.inc.php (with a default, of course)
>>> >>
>>> >> >> I'm still testing, so no commit yet.
>>> >>
>>> >> > I've improved the sorting, removed duplicate display of article that starts a thread, and added a toggle to display 'Thread' or 'Article' view. The toggle will remain with your session, and if you are logged in, will become your default view.
>>> >>
>>> >> > Hopefully, I can add a commit later today or tomorrow. I'm still trying to find bugs, but I'm sure once I commit I'll start to find them all :)
>>> >>
>>> >> Well, I got sorting sorted. HAHHAHAHA! (Yes, I'm all alone in a room and may have lost my mind)
>>> >>
>>> >> Anyway, I have pushed a commit for the new overboard. If you don't create a default in overrides,inc.php, it will default to the original flat articles view. There is a toggle (radio buttons) on the overboard for a user to change that, and it will remain changed for that user.
>>> >>
> <snip>

>> When playing with theme ideas I noticed duplicate class names for elements in the same table row.

>> In each table row, the class names of table elements repeat for the username and datebox elements. It would be much better for styling if the class names for each element were unique. For example, class='datebox_left', class='datebox_right', class='article_title', class=author_left', class='author_right', class='total_replies', etc. You can even leave the current class names in place as is, and add extra unique class names to the html output, so that they can be styled individually or as a unit. Keeping the old classes and adding new uniques alongside them would prevent breaking backward compatibility of themes.

> I completely agree with this. Please understand that RSLight is the first time I had ever used css, so I was learning as I went. Both css and databases were new to me, so you can see that in the code. It does need to be cleaned up.

>> Also I notice that when building the tables that each table row has alternating class names, 'np_thread_line1', 'np_thread_line2' and each of these class names is re-used in its same row. Something like 'np_thread_line_left_1', 'np_thread_line_center_1', 'np_thread_line_right_1' would make styling with CSS much easier. I think I need to separate header.inc and body html generation files then run search and replace on them and probably avoid 90% of the hand editing.

> Yes, I agree with you.

>> Basically the idea so that every element in a table row will have at least one class name that is unique or repeated in that row--and so that no class names used in the header and footer appear in the document body, or also the header and footer elements each have a unique class name so elements can be targeted individually there without much fuss. This allows a lot of cool CSS tricks for themes and responsive layout magic without having to resort to endless :nth-child() and selector strangeness. It would also make it much easier to use multiple web fonts with CSS to change fonts on selected elements in a theme. In my new theme I actually want to use two different fonts for table data elements that have the same class names.

> I believe it is best to add the classes to css, then it can be modified in the code, if desired. We would leave all the existing classes alone for backward compat.

>> Since I am working on a theme maybe I should send a patch for the php files showing what I mean regarding class names. I'm still wrapping my head around it so I'll check back in when I get time to dig in and finish the theme and test the changes before making a patch.

> I think I get it, but feel free to demonstrate. It can't hurt :)

I've changed the class for the new overboard 'style toggle' feature, and will continue to create a new style for anything new. I'll also add a new class when I come across them, always keeping the existing class.

Thanks for the input, it helps.

--
Retro Guy

Retro Guy wrote:

> On Fri, 26 Apr 2024 12:18:08 +0000, Retro Guy wrote:

>> Retro Guy wrote:
>>
>>> Retro Guy wrote:
>>
>>>> I've been experimenting with an option in overboard to display recent articles by thread.
>>
>>>> I did this in the past, but it wasn't so great, so trying again. I'm still testing, but if you want to take a look, it's running on www.novabbs.org now:
>>>> https://news.novabbs.org/computers/overboard.php?thisgroup=news.software.nntp
>>
>>>> The thread vs. flat display will be a toggle in overrides.inc.php (with a default, of course)
>>
>>>> I'm still testing, so no commit yet.
>>
>>> I've improved the sorting, removed duplicate display of article that starts a thread, and added a toggle to display 'Thread' or 'Article' view. The toggle will remain with your session, and if you are logged in, will become your default view.
>>
>>> Hopefully, I can add a commit later today or tomorrow. I'm still trying to find bugs, but I'm sure once I commit I'll start to find them all :)
>>
>> Well, I got sorting sorted. HAHHAHAHA! (Yes, I'm all alone in a room and may have lost my mind)
>>
>> Anyway, I have pushed a commit for the new overboard. If you don't create a default in overrides,inc.php, it will default to the original flat articles view. There is a toggle (radio buttons) on the overboard for a user to change that, and it will remain changed for that user.

> Just added support for user blocklist (hiding users)

I have moved the radio buttons to the overboard header to reduce wasted space, and used SugarBug's good idea of creating a new css class for it.

Also, fixed reading a user's default once the session ends so it doesn't default to the site default.

There is one bug I'm aware of right now, but it's not very important. I'll work on in later in the week, putting preference on any actually important bugs I find.

What you see on my sites is the latest commit.

--
Retro Guy