- Overhaul of kokonotsuba's HTML output and CSS files. One thing desperately needed is a complete separation of all the layout/structure/universal CSS into base.css, and all the purely aesthetic-related CSS into the user-selectable stylesheets. For a long time, this has been made nearly-impossible to due to the following...

- Make the kokonotsuba repo as close to Heyuri as possible, while also being completely independent of Heyuri/kolyma/etc.'s servers. I've heard there's been improvements in this area lately, but the last time I set up kokonotsuba it required significant amounts of fiddling to undo all the Heyuri/kolyma-specific things, while simultaneously not having many expected features found on Heyuri enabled or included by default. This made it very difficult to set up a local instance of kokonotsuba for me to work on HTML/CSS improvements, since whatever I created wouldn't necessarily work on Heyuri itself

- If possible, make it so kokonotsuba initially renders with sane default settings instead of all the less-common settings (which get undone by the default settings or user settings every page load). Currently, kokonotsuba will load the page with things like "Center threads", "Persistant navigation", etc. all activated by default, and then it applies the default/user settings to deactivate them, causing there to be a long period where the page elements are unecessarily (and annoyingly) shifting around, the board links not appearing for a while, etc. It's particularly bad on old/slow machines and devices

- Increase the size of the post previews in the post management page, as was previously done on the ban management page - currently they are so heavily truncated (20 characters) that they are almost useless

- Make the search page remember your target/method settings

- The RSS feed feature seems b0rked. It never worked well or as I expected it to, but I believe it also now spits out invalid XML (an RSS previewing add-on I have just comes back with "Error while parsing feed" - I can't remember if it always did this or is a more recent degradation)

- Needs moar tegaki

- Speaking of the post management page: a feature to customize how many posts per page are displayed (and even displaying all) would be very welcome. Additionally, the ability to filter by IP or even have a search feature would be teh awesum

I know u can do this kind of thing client-side using tablesorter and associated plugins, which works clientside using jQuery (pic related) - there's even a plugin for pagination and number of rows displayed. You can see some of these tablesorter features in action on @Party II in fact: https://cgi.heyuri.net/party2/user/49616e596568/monster_book.html

A recent post on Off-Topic has reminded me...

- Automatically scrollify long posts (and also increase the height of the scroll box from what it currently is cuz it's way too short)

>Automatically scrollify long posts (and also increase the height of the scroll box from what it currently is cuz it's way too short)
use something like

blockquote.comment {
  max-height: 400px; /*or whatever*/
  overflow-y: auto;
}

in the CSS

this should degrade gracefully on old-ass browsers except maybe FF before 3.5 (which implemented max-height before overflow-y unlike everyone else) if that matters

>>67076
oh I'm dumb lol
just use overflow instead of overflow-y, which should work on nearly everything ever

>>67078
I actually checked live on the page in the dev tools, and since the content horizontally wraps, overflow (no y) does the same thing and has significantly better old browser compatibility.
Using "auto" also puts the correct scrollbars instead of always showing them, you might be using "scroll" if they're showing up.

reference: https://github.com/Heyuri/kokonotsuba/issues/100
teh reason why there's so much extra characters is that koko uses tables for EVERY POST (as well as doublearrows). whereas vichan just uses div for each post.

On my test instance i was able to achieve a tableless koko as shown in picrel... howevar... no double arrows (;´Д`), because i couldn't get them to draw on the same line as the posts without b0rk. I'm by no means gud at css so if sumone else can manage to do it then post it in this thread.

how it werks:
table stuffz replaced with div

.reply

has 2 nu attributes,

display: table

and

margin: 5px

(make sure to clear cache if ur testing)
base.css: https://up.heyuri.net/src/3616.css
kokoimg.tpl: https://up.heyuri.net/src/3617.txt

>.reply
actually they were moved into their own class so there can be a separation between aesthetic stuff and structural, as mod-sama said

>actually they were moved into their own class so there can be a separation between aesthetic stuff and structural, as mod-sama said
They don't need to be literally different - just in separate files

i.e.

base.css

.thing {
display: table;
padding: 2em:
}

tehk00lness.css

.thing {
background-color: #f0e0d6;
color: #800000;
border: 1px solid #be8080
border-top: none;
border-left: none;
}

To explain further, the goal is to reduce the amount of duplicated/conflicting CSS - such as having "padding: 2em" in every single alternative stylesheet because it's not found in base.css

Equally, it's to prevent situations where the same CSS is reduntantly included in both base.css and the alternative stylesheets, or only found in some stylesheets but not others. This makes it much easier to create new stylesheets, and maintain old ones when new features are added

When you have a situation like:
base.css

.item {
  padding: 8px;
}

custom.css

.item {
  background-color: #eeeeee;
}

...what will happen is that ".item" will have both padding and background-color applied. Even if something is only featured in the earlier file, it will not be removed when the later file is loaded. They effectively stack together, and you can keep adding to a selector across different files or different sections of the same file

However, when you have a situation like:
base.css

.item {
  background-color: #c1b2a3;
  padding: 8px;
}

custom.css

.item {
  background-color: #eeeeee;
}

...the background-color found in the latter file will override the value set in the first file (though the value in the first file will be used until the second file is loaded). The padding will remain active throughout since it wasn't overridden in custom.css

>>67085
>They don't need to be literally different
ah

Add support for mp3/flac/wav/opus etc. I want to make a music thread

>>67140
you can upload audio files here: https://up.heyuri.net/m.php
and then post the resulting link to the file in a post

>>67085
>>67086
based on these posts i made an attempt to achieve the separation here: https://github.com/hachikuji-san/kokonotsuba-portable/tree/main/static/css (see base.css futaba.css heyuriclassic.css and oldheyuri.css). let me know if it isn't fail

>>>67167
Arigato! This seems good so far, I applied to the github repo with slight changes, also finally (mostly) tidied up Heyuri's messy static file locations. It's currently what we use on imageboards
If you ever feel like it, there is also the separate CSS files of so-called "textboard" mode, but I don't know how bad it is compared to how imageboard mode's style was. I think its bigger issue is some junk CSS in it that nothing uses anymore.

>Manage Posts is a bit uncomfortable to use over the live front end. Teh font size is too large (more of a personal dislike), which can be fixed with slight changes to css.
updated

>And you only get to view the first douzen or so characters in teh fields, especially the comment field... maybe they can be put in a textarea with the full comment
I dunno how, but it could be increased

>As for the images maybe there could be sum javascript and a preview button where it loads the image in teh page, instead of needing to open a new tab.
I already use a browser like this, but I think it should just load the file thumbnail upon hovering it with mouse, using JS

>when logging mod/janitor/admin actions it should log a username to identify the action
I think the way I wrote u about is the best way to handle this

>fix or recreate teh archive moduke that kokonotsuba used to have
Maybe, a workaround is having threads automatically move to another "archive" board (that MT already exists) once their bump order get near $LIMIT_SENSOR ? For this, using the same DB's another table (something liek imglog_archive) make sense I think. This is if one table of DB getting too hueg doesn't affect the others for kokonotsuba. It would also need a modification so their post numbers are same. Also, moving a thread with [MT] from an archive board to the live one would bring back "wiped" threads in case anti-spam measures fail for some reason. This is just mai idea

>Overhaul of kokonotsuba's HTML output and CSS files
Done for imageboards (thought you noted it still needs some improvements). Needs doing for txt styles still. I also want it so Lounge's text area doesn't exceed the screen on mobile while on it

>Make the kokonotsuba repo as close to Heyuri as possible
Done!

>If possible, make it so kokonotsuba initially renders with sane default settings
Needs doing

>the board links not appearing for a while,
I have an idea on fixing this. I think the "default" that loads with the template should be classic menu, and then JS should be applied on top of it.

>Increase the size of the post previews in the post management page
Same as second point

>Make the search page remember your target/method settings
Yes, and the catalog should remember sorting

>The RSS feed feature seems b0rked
possibly related to https://github.com/Heyuri/kokonotsuba/pull/82

>Needs moar tegaki
Noted here: https://github.com/Heyuri/kokonotsuba/issues/111


There are also some things I noted, in form of issues:

Futaba style IP display: https://github.com/Heyuri/kokonotsuba/issues/110
Actually, ID thing should be a module too, working in the same way as I noted above. Maybe I will create an issue for this too sometime

Have install.php check common pitfalls, so installing koko is easy: https://github.com/Heyuri/kokonotsuba/issues/109
Should be easy for a dev using chatgpt since install.php isn't connected to other stuff (at least doesn't need to for this update), but needs noting down of all common pitfalls (ie. stuff that may not come with the server by default)

This JS thing about inline images: https://github.com/Heyuri/kokonotsuba/issues/108
Do you have an idea how frustrating this issue is when you're fapping?
Semi-related to this, "Gallery mode" button doesn't deserve being outside of [Settings].

I don't know how hard this is, but I think doing this would make posting on Lounge almost twice as fast: https://github.com/Heyuri/kokonotsuba/issues/107

Quote backlinks: https://github.com/Heyuri/kokonotsuba/issues/5
I now think the function for backlinks should just be removed off kokonotsuba, and it should be a JS thing that can be toggled from [Settings].

File uploading board: https://github.com/Heyuri/kokonotsuba/issues/102
I'd bring back Flash@Heyuri if this ever gets done

plz make it so that short board code names in nav bar would show full board titles on hover, thx

>plz make it so that short board code names in nav bar would show full board titles on hover, thx
old threads on this board dont bump at the moment so you should maek new threads for suggestions