edorableraf {"ops":[{"insert":"Currently, groups are ordered alphabetically like so:\na b c\nd e f\ng h i\n\nI'm requesting an option to order groups like this:\na\td\tg\nb\te\th\nc\tf\ti\n\nIn practice it can be hard to follow when groups are large; knowing which column a group will be in is basically a guess:\nartifact\t\tbattle\n\t\t\t\t\t\tenchantment\n\ncreature\t\tland\n\n\n\ninstant\n\nsorcery\n\nIt would be nice if there was an option to sort groups based on columns, since I'd know which column to look for a group based on the top row:\nartifact\t\t\t\tinstant\n\n\t\t\t\t\t\t\t\tland\nbattle\ncreature\n\n\n\nenchantment\tsorcery\n"}]}
0
{"ops":[{"insert":"We used to do this actually, and it has a lot of problems. The largest of which is that it causes columns to move around as you edit the deck in order to attempt to \"rebalance\" the stacks. \n\nBeyond that, you need an actual rebalancing algorithm, which slows down the page on slower devices. \n\nThere's a browser feature that's been in the works for a few years now (like the people who work on chrome, safari, etc). Once that goes through, it'll make what you're asking for more feasibile, but even then the columns moving around as you edit just sucks since you can never reliably find where things are on the page (since they're always moving).\n\ntl;dr - We may go back to this at some point, but minimally we're waiting for a browser feature. Even then, I'm not sure we'd go back.\n"}]}
0
{"ops":[{"insert":"I understand that as groups move between columns it's difficult to locate where things are but I already can't reliably find groups on the page because the current ordering is unintuitive. Since there's no real concept of rows due to imbalanced stacks, locating a T group isn't always as simple as looking to the right of an S group, since it could be way lower because of a large stack above it (say, Lands). But if ordering was column-based, it would always be as simple as looking below the S group or at the top of the next column.\n\nAnd why does there need to be a rebalancing algorithm? Doesn't it only need to compute number of groups / number of columns?\n\nWhat if the columns only move on reload? Let the columns be unbalanced as new groups are added/removed and only rebalance the columns as the page is reloaded/resized?\n\n\n"}]}
0