Multiselect: sort checked up top #971

Closed
jancborchardt opened this Issue Dec 20, 2012 · 7 comments

Projects

None yet

2 participants

@jancborchardt
Member

In users for example, the multiselect plugin should automatically sort the selected entries to be first because they are the most relevant.

cc @tanghus @icewind1991

@tanghus
Member
tanghus commented Dec 20, 2012

I could add an option 'sorting':'alphaNumeric'|'checkedFirst'|'none' where 'none' is default.

@jancborchardt
Member

@tanghus let’s just do it properly, not with an option. People shouldn’t be able to configure it to behave shittily. ;)

@tanghus
Member
tanghus commented Dec 20, 2012

@jancborchardt I'd rather say let's do it properly, with an option. Programmers don't want shitty defaults ;) People - as in users - won't be able to configure it.

@jancborchardt
Member

Developers are users too. And if there’s the option it will be changed, which will turn out crappy for users. Let’s see the options:

  • »none«: what does that exactly mean? Isn’t that the same as alphanumeric? If you mean sort by order when it was added: makes no sense when you come back to it later.
  • »alphaNumeric« is standard
  • »checkedFirst« would also be alphanumeric, just with the checked (read:relevant) entries sorted up top

Of course options always seem cool, but most of the time they just don’t make sense.

@tanghus
Member
tanghus commented Dec 21, 2012

Well "none" shouldn't be an option but what happened when the sorting argument wasn't given - as it is now.

It's not because options are cool, but because it would be a bad design decision to rearrange the list per default. The plugin shouldn't be tailored just to work in one use case, then it's not a plugin.

@jancborchardt
Member

Since #994 is merged in this is fixed, yeah!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment