Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sort all the things! #91

Open
thesecretmaster opened this issue Oct 18, 2017 · 4 comments
Open

Sort all the things! #91

thesecretmaster opened this issue Oct 18, 2017 · 4 comments

Comments

@thesecretmaster
Copy link
Collaborator

We need to make more of the things sortable! @MeghanUX, what are all the things you want to get sorted?

@thesecretmaster
Copy link
Collaborator Author

Some images from @MeghanUX:

scot_broadcast_input_v02png

scot_broadcast_input

@bmoelk
Copy link

bmoelk commented Oct 21, 2017

Seems like the easiest way to resolve this issue is to apply sorting directly on the client via: https://datatables.net/ (jquery dependent, full featured, heavy) or http://github.hubspot.com/sortable/ (no dependencies, simple, getting a bit longer in the tooth)

Is there an option to push all data directly to the client and paginate there or should we maintain server-side pagination?

@ArtOfCode-
Copy link
Owner

Ideally, we should keep server-side pagination - sending all the data to the client at once is not such a great solution once your dataset starts getting larger.

@thesecretmaster
Copy link
Collaborator Author

From @MeghanUX in #73:

On "Status - All Requests" page - these filter/sort options:

  • date submitted
  • ID number
  • who submitted it
  • from language
  • to language
  • who translated it (or, who it is assigned to)
  • status (pending, completed, unassigned, ...)

Reply from @ArtOfCode- in #73:

If I could, I would willingly include every field we have in the database in every table. However, once you go over about 5-6 columns, especially if any of them are lengthy, there just isn't enough space on a screen. This is coming from a guy with a big screen, too, so I can imagine it's only worse on smaller screens or mobile.

I'm quite happy to change some of the info that's in the table, if there are more important fields we could be showing instead, but I don't want to add any additional columns - that's what the details view is for.

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

No branches or pull requests

3 participants