User talk:JackPotte/2023

Hi
I know its unrelated to anything, but I noticed on your userpage that you are a near-native speaker of English. Just like to say that you seem so good at it, it feels weird to say only "near" native. Although I assume it also has to do with your spoken English as well.

I know somebody who says their English is bad, but honestly they are really good (at least in writing). I'm so terrible at other languages, my best french is "Bonjor" (is that even how you spell that!?). Anyway, have a good day/night. 21:47, 17 January 2023 (UTC)
 * Bonjour, and thank you for the compliment. Actually I've started to speak English at school when I was 10 and never stopped since. But only one hour per day, so I'm sure that it must be more difficult for me to formulate sentences, than for a native speaker. JackPotte (discuss • contribs) 10:29, 18 January 2023 (UTC)

TOC for JavaScript
Thank you for your improvements to the Wikibook JavaScript in general. But I'm not happy with your last changes concerning the TOC. The new template is used twice: as part of the complete TOC on the main page and as a fast navigation within each page. I suggest that the navigation shall keep much shorter, only to important pages. The actual version is so huge that it downgrades the readability of most pages. This does not only apply to browsers on a desktop, the UX on smartphones is significantly deteriorated. What do you think about a split: the complete list of pages on the main page and a template with a shortened list to few pages? Kelti (discuss • contribs) 03:10, 14 February 2023 (UTC)

The new page JavaScript/JS_at_server does not support linking to the next/previous page. Any idea why? --Kelti (discuss • contribs) 03:53, 14 February 2023 (UTC)
 * hello. For JavaScript/JS_at_server, it was the server cache and it has refreshed itself now.
 * Concerning the double TOC system, you're right that it makes sense for the mobile rendering, so we could hide (or toggle) some chapters, only for mobiles.
 * But if we do it for PCs too, we really should explain it (in a comment) because it looked like we had an up-to-date and a deprecated list to sync. JackPotte (discuss • contribs) 05:50, 14 February 2023 (UTC)
 * I suggest to create a heading "Fast Navigation" within JavaScript/TOC, shorten it significantly, and put links to all subpages literally to the main page. OK? Kelti (discuss • contribs) 16:03, 14 February 2023 (UTC)
 * actually the print version Lua module uses to dynamically display a whole book content, its /TOC page if defined, its main page otherwise. So if we don't rename it for the sidebar, it would be shortened too. Moreover, I've just checked that the old sidebar rendering on mobile was hidden too (its Lua added class="sidebar nomobile nowraplinks"), so would it be only for desktops? JackPotte (discuss • contribs) 16:25, 14 February 2023 (UTC)
 * Dynamically print: It's ok to rename /TOC to something else and take the printing from the main page where we shall have all links to subpages. By this, the meaning of /TOC changes to "Fast Navigation". But because it's a great help to have a lot of often used elements like 'navigation to sister pages' or 'BookCat' on a central place, these features should survive.
 * Rendering on mobile: The distinction between mobile and desktop concerning rendering sounds a little strange to me. Shouldn't we take such decisions from the availability of pixes in x-direction - independent from the kind of hardware?
 * Kelti (discuss • contribs) 19:03, 14 February 2023 (UTC)
 * I would be OK for a "Fast Navigation" bar, but I'd rather split the book pages into several chronological navigation sidebars, to provide access to all of them from their neighbors, without taking half of each page.
 * Concerning the distinction between the mobile and desktop renderings, it's already made by MediaWiki at a lower level, by selecting either https://en.wikibooks.org or https://en.m.wikibooks.org according to the device. But changing the URLs can override this, so I can't see what we could do in addition. JackPotte (discuss • contribs) 20:48, 14 February 2023 (UTC)
 * I'm sorry, but I have one more question: which template creates the navigation on the top of the page? The 'backlink' to the main page (on a separate line) and the two links (with arrow-pictogram) on the left and right side to the sibbling pages? Is it the template Book navigation? And: how to repeat the links to the sibblings on the bottom of the page? And: how to omit these links and use the template subpage navbar instead - it also creates the links automatically? Kelti (discuss • contribs) 20:28, 15 February 2023 (UTC)
 * the navigation templates called by Book navigation are AutoHeader and footer. For now, this system does not support subpage navbar because this template doesn't use the same Lua algorithm to retrieve the TOC pages. JackPotte (discuss • contribs) 11:51, 16 February 2023 (UTC)
 * Now there is a collapsible version of TOC. When I publish it (JavaScript/TOC&oldid=4238114), the dynamically printing and the head and foot navigation fails. Do you have an idea why? --Kelti (discuss • contribs) 10:34, 18 February 2023 (UTC)
 * This is a TODO I wanted to treat for a few years, because it's needed in the book Puppy Linux too. I just need to improve the Lua page name extraction from the TOC line... JackPotte (discuss • contribs) 21:14, 18 February 2023 (UTC)


 * for now [//en.wikibooks.org/w/index.php?title=Template:Book_navigation&diff=prev&oldid=4237346 I've just hidden it completely on mobiles]. JackPotte (discuss • contribs) 08:56, 14 February 2023 (UTC)

AuthorsAndContributorsBot
Hi Jack, due to things irl, I won’t be able to stay active in this wiki for much longer. Would you be interested in incorporating the task of to JackBot? I can release the latest version of the source code in a subpage of the bot’s user page. Thanks in advance, -Slava Ukrajini Heroyam Slava (discuss • contribs) 22:27, 13 April 2023 (UTC)
 * Hi, yes I must be able to maintain it if it's written in PHP, Python or JS. JackPotte (discuss • contribs) 06:46, 14 April 2023 (UTC)
 * Thank you very much! The code is written in python. I have released it in User:AuthorsAndContributorsBot/source code. Notice that it generates what the contents of the page are supposed to be, and then if it’s not the same as what actually is in the page, it updates the page. That means that if you change the message at the beginning of the list, it will be updated in all pages. -Slava Ukrajini Heroyam Slava (discuss • contribs) 10:06, 14 April 2023 (UTC)

New book idea
Hi there,

I’m new here. Do you think a reference guide for cases in the Ukrainian language is in the scope of Wikibooks? Thanks in advance, -Futurama forever (discuss • contribs) 13:24, 24 June 2023 (UTC)
 * Hello, it depends on if it would be a double of the book Ukrainian, or if it could be integrated into it. JackPotte (discuss • contribs) 17:39, 24 June 2023 (UTC)
 * I plan to create a single-page book. Each case in the Ukrainian language will have its own section which tells how words in this case change, and also when this case should be used with examples. -Futurama forever (discuss • contribs) 16:54, 7 July 2023 (UTC)

Hello,I need to You
@JackPotteHello dear friend, I want you to do something for me, can you help me in writing my books?

I alone cannot complete five books Germany Poul Ah (discuss • contribs) 07:26, 15 August 2023 (UTC)