User talk:Jack McKalling/sandbox

Version nav

 * "Rework the version nav template with more intuitive arrow links"

What are your ideas for this? I could help implement it. – Nixinova   23:41, 11 February 2019 (UTC)
 * Thanks a lot for the offer! I wanted to change how the next/prev, parent and nextparent/prevparent parameters (the arrow buttons) work. They are incredibly confusing and I can't possibly figure out how to use their values. I tried many times but I kept using them wrong. I wanted the navigation to link between each and every release, including snapshots, pre-releases and full releases, and not "cap" each full release to just the related sub-versions. That the small next and prev arrows would move forward/backward simply to the closest version, regardless of what type it is, and the big arrows to the closest full release version. Such that the "next" button would link 18w32a&rarr;18w33a, 1.13.1&rarr;1.13.2-pre1 (not 1.13.2), and 1.13-pre10&rarr;1.13&rarr;18w30a (instead of just "stopping" at pre10). And such that the "nextparent" button would link 1.13-pre10&rArr;1.13 (not 1.13.1) and 18w30a&rArr;1.13.1 (not 1.13.2). In other words, everything in chronological release order. I also think the current &lArr;&larr;&rarr;&rArr; layout is not intuitive. I was thinking of something more of a left/right and up/down orientation but I'm not sure yet. Lastly, I'm not sure exactly how this idea could be tested/sandboxed. – Jack McKalling [ Grid Book and Quill.png Diamond Pickaxe.png ] 00:40, 12 February 2019 (UTC)
 * Hmm, so maybe a two-row system? For example, on the page "14w03a",
 * {| style="text-align: center; border: solid 1px black;"


 * ◄◄ 1.7.2  ◄ 1.7.10 &emsp;1.8&emsp; 1.8.1 ►   1.9 ►►
 * ◄◄ 1.7.10-pre4  ◄ 14w02a &emsp;14w03a&emsp; 14w04a ►   1.8-pre1 ►►
 * }
 * – Nixinova Nixinova sig image 1.png Nixinova sig image 2.png 03:36, 12 February 2019 (UTC)
 * – Nixinova Nixinova sig image 1.png Nixinova sig image 2.png 03:36, 12 February 2019 (UTC)


 * I think I understand what you're trying to do, namely navigating full releases in the top and non-full releases in the bottom. While that does cover more options to navigate to, it uses up even more horizontal space than the current thing and isn't more intuitive. Also the numbers of your example aren't navigating exactly how I had in mind. So to correct your example, the numbers would become these:
 * {| style="text-align: center; border: solid 1px black;"


 * ◄◄ 1.7.2  ◄ 1.7.10 &emsp;1.8&emsp; 1.8.1 ►   1.8.8 ►►
 * ◄◄ 14w02a  ◄ 14w02c &emsp;14w03a&emsp; 14w03b ►   1.8-pre3 ►►
 * }
 * Basically following the logic for the top row: parent full release in the center, previous full release to its left, the first full release of the same major version further to the left. The next full release to the right, last full release of the same major version further to the right. And following the logic for the bottom row: current version in the center, previous one to its left, first minor release of the same parent full release further to the left. The next minor version to the right, last minor version of the same parent full release further to the right.
 * Although this would be the kind of navigation logic I had in mind, it isn't the best layout yet. In fact, it is worse, because it gets so wide that each row will wrap to most likely three rows, and I disliked the two rows of the current system already. It could maybe work if you place the bottom row vertical around the other one, in table cells to make sure nothing will ever wrap. So like this:
 * {| style="text-align: center; border: solid 1px black;"
 * {| style="text-align: center; border: solid 1px black;"


 * colspan=2 |
 * ▲▲ 14w02a
 * colspan=2 |
 * colspan=2 |
 * ▲ 14w02c
 * colspan=2 |
 * ◄◄ 1.7.2 || ◄ 1.7.10&emsp;
 * style="border: solid 1px black" | 1.8 14w03a
 * &emsp;1.8.1 ► || 1.8.8 ►►
 * colspan=2 |
 * 14w03b ▼
 * colspan=2 |
 * colspan=2 |
 * 1.8-pre3 ▼▼
 * colspan=2 |
 * }
 * I'm not sure about this yet though, what do you think? – Jack McKalling [ Grid Book and Quill.png Diamond Pickaxe.png ] 09:08, 12 February 2019 (UTC)
 * More specifically, I want those arrow buttons to intuitively be imagined as "conveyor belts". The horizontal conveyor belt can roll from left to right or back, the vertical one is bound/defined by the current slot of the horizontal conveyor belt, and rolls from top to bottom or back, between versions related to the selected cell of the horizontal belt. Sort of like that. If you're following me. – Jack McKalling [ Grid Book and Quill.png Diamond Pickaxe.png ] 09:21, 12 February 2019 (UTC)
 * colspan=2 |
 * }
 * I'm not sure about this yet though, what do you think? – Jack McKalling [ Grid Book and Quill.png Diamond Pickaxe.png ] 09:08, 12 February 2019 (UTC)
 * More specifically, I want those arrow buttons to intuitively be imagined as "conveyor belts". The horizontal conveyor belt can roll from left to right or back, the vertical one is bound/defined by the current slot of the horizontal conveyor belt, and rolls from top to bottom or back, between versions related to the selected cell of the horizontal belt. Sort of like that. If you're following me. – Jack McKalling [ Grid Book and Quill.png Diamond Pickaxe.png ] 09:21, 12 February 2019 (UTC)