[Feature] Multi-column lists

In category: Site Bug Reports & Feature Requests

Requested feature overview description.

A method of making multi-column lists.

Why would it be useful?

When writing out a long list, especially if the entries of that list are very short, a lot of screen space remains unused. Allowing a method to split the list into 2 or 3 columns will better utilize the screen space and reduce the amount of scrolling needed to read the entire list.

See the "Jewelpets" section of jewelpet for an example of a list that could benefit from having three columns instead of one.

The table feature is too fiddly for this and always adds borders and background colors to its contents whether you want it or not.

What part(s) of the site page(s) are affected?

Anywhere with Dtext.


We already have one:

h5. Jewelpets:[table] | | 
[[alex_(jewelpet)|Alex]][sup]!wa[/sup] | [[amelie_(jewelpet)|Amelie]][sup]xwa[/sup] | [[angela_(jewelpet)|Angela]][sup]!w[/sup]
[[aqua_(jewelpet)|Aqua]][sup]xwa[/sup] | [[brownie_(jewelpet)|Brownie]][sup]!wa[/sup] | [[charotte_(jewelpet)|Charlotte]][sup]xwa[/sup]
[[chite|Chite]][sup]xwa[/sup] | [[coal_(jewelpet)|Coal]][sup]!w[/sup] | [[dian_(jewelpet)|Dian]][sup]!w[/sup]
[[diana_(jewelpet)|Diana]][sup]w[/sup] | [[flora_(jewelpet)|Flora]][sup]!w[/sup] | [[garnet_(jewelpet)|Garnet]][sup]w[/sup]
[[granite_(jewelpet)|Granite]][sup]!w[/sup] | [[io_(jewelpet)|Io]][sup]!w[/sup] | [[jasper_(jewelpet)|Jasper]][sup]!w[/sup]
[[kaiya_(jewelpet)|Kaiya]][sup]!w[/sup] | [[king_(jewelpet)|King]][sup]!w[/sup] | [[kohaku_(jewelpet)|Kohaku]][sup]!w[/sup]
[[kris_(jewelpet)|Kris]][sup]!w[/sup] | [[labra_(jewelpet)|Labra]][sup]!w[/sup] | [[lapis_(jewelpet)|Lapis]][sup]!w[/sup]
[[larimar|Lorimar]][sup]!wa[/sup] | [[lolip|Lolip]][sup]xwa[/sup] | [[luea_(jewelpet)|Luea]][sup]!wa[/sup]
[[luna_(jewelpet)|Luna]][sup]!w[/sup] | [[milky_(jewelpet)|Milky]][sup]!w[/sup] | [[nephrite_(jewelpet)|Nephrite]][sup]!w[/sup]
[[nix_(jewelpet)|Nix]][sup]!w[/sup] | [[opal_(jewelpet)|Opal]][sup]w[/sup] | [[peridot_(jewelpet)|Peridot]][sup]w[/sup]
[[prase_(jewelpet)|Prase]][sup]!w[/sup] | [[rald]][sup]xwa[/sup] | [[rin|Rin]][sup]xwa[/sup]
[[rosa_(jewelpet)|Rosa]][sup]!w[/sup] | [[ruby_(jewelpet)|Ruby]][sup]w[/sup] | [[ryl|Ryl]][sup]xwa[/sup]
[[sango_(jewelpet)|Sango]][sup]w[/sup] | [[sapphire_(jewelpet)|Sapphie]][sup]w[/sup] | [[tata_(jewelpet)|Tata]][sup]!w[/sup]
[[titana|Titana]][sup]xwa[/sup] | [[topaz_(jewelpet)|Topaz]][sup]!w[/sup] | [[tour_(jewelpet)|Tour]][sup]!w[/sup]
[[yuku_(jewelpet)|Yuku]][sup]!w[/sup]
[/table]
Jewelpets:
Alex!wa Ameliexwa Angela!w
Aquaxwa Brownie!wa Charlottexwa
Chitexwa Coal!w Dian!w
Dianaw Flora!w Garnetw
Granite!w Io!w Jasper!w
Kaiya!w King!w Kohaku!w
Kris!w Labra!w Lapis!w
Lorimar!wa Lolipxwa Luea!wa
Luna!w Milky!w Nephrite!w
Nix!w Opalw Peridotw
Prase!w raldxwa Rinxwa
Rosa!w Rubyw Rylxwa
Sangow Sapphiew Tata!w
Titanaxwa Topaz!w Tour!w
Yuku!w

^ OP said tables weren't suitable and specified why.

On a slightly different topic, is a fixed number of columns actually desirable? If we could do automatically determined #columns, that would accommodate mobile users better.

Snowy
Privileged
1 month ago
ambiguous_gender annoyed anthro cute dragon frill grumpy helvetica_(artist) lol_comments membranous_wings purple_scales rar scales scalie scowl smoke solo spade_tail wings

Rating: Safe
Score: 12
User: Anomynous
Date: October 10, 2007

A responsive list feature would be neat. I'm just not sure that it's used enough to justify putting any dev time into it. A flag for the table tag to turn off the background colors and outlines might also be neat, but I have the same doubts.

In the meantime, if you think that the table feature is too fiddly, here is a script that will* convert a list into a table for you. It's in python because I've been meaning to learn python and this seemed like a slightly practical exercise.

*Probably. It seems to work. I'm not claiming to be any good at this stuff.


savageorange said:
^ OP said tables weren't suitable and specified why.

On a slightly different topic, is a fixed number of columns actually desirable? If we could do automatically determined #columns, that would accommodate mobile users better.

Holy smokes, just took a look at the updated wiki on my phone, the table is bad for mobile!


Furrin_Gok said:
Holy smokes, just took a look at the updated wiki on my phone, the table is bad for mobile!

What do you mean? On an iPhone it doesn't look bad. A bit small if not zoomed, though.