TOPIC:

I like to change the standard value of 10 in the list of persons.
I know I can change it by hand to up to 1000.

See attachment

These values are set in 'datatables-attributes.phtml' (for all lists), in this line .

There is no configuration option for this - You have to adjust them directly in the view file, or create a custom module that replaces this view.

Actually 10 records per page isn't so bad - at least they fit nicely on my screen with the upper third of the screen used by the headline, the menu and JustCarmen's Fancy ImageBar. When I move down so that headline, menu and image bar disappear, 20 records fit on my screen nicely. That's ok for me, but the question should not be how to make these lists show in an optimal way just for me, but for the majority of users. Therefore I'd like to suggest to store this number of records per page with the user, not necessarily as a parameter that needs to be configured, but maybe in a cookie. I think this is done for other settings as well.

On the other hand I'd like to suggest to rethink the positioning of the three list settings for the page number (upper left), filter (upper right), records per page (lower right) - in three different corners of the screen. When I open such a list I usually use 3 steps to achieve my objective.

1. filter the list which usually reduces the number of records in question significantly
2. change the number of records per page
3. flip through the various pages

I would like to see these three list settings in that same sequence in one line both on top of the list and at the bottom of the list, preferably all aligned to the left. That would then require the smallest mouse movements and hopefully be perceived as an efficient way to flip through the list.

Does that make sense and could that be implemented for all kinds of lists?

Thanks, changed the file, deleted 10 and changed 20 to 25.
Uploaded the new file and it works.

> I would like to see these three list settings in that same sequence in one line both on top of the list and at the bottom of the list

1) There isn't enough space to put all the options (pagination, search, page-size, etc.) both top and bottom.

2) The row height changes with the data. Long text will wrap onto several lines.
With the pagination at the top, you can click the "next page" button repeatedly, as it stays in the same place.
But at the bottom, it would jump up/down after every page load.

Greg,

1) There isn't enough space to put all the options (pagination, search, page-size, etc.) both top and bottom.

2) The row height changes with the data. Long text will wrap onto several lines.

I dispute both your assertions

1) see my pull request github.com/fisharebest/webtrees/pull/3702.
2) It is true that the content affects the row height and this can cause the table height to exceed the screen height (best example is the manage media page in control panel). Now if I'm viewing the last entry and want to go to the next page, I have to scroll back to the top to access the pagination control.

> 2) The row height changes with the data. Long text will wrap onto several lines.

(Assuming my animated GIF works...)

The "next" button at the top of the page stays in the same place - so I can click "next", "next", "next" easily.
The "next" button at the bottom of the page is at a different place on every page, so it is much harder to page through the data.

I realise I'm flogging a dead horse here!

Go to Control panel - manage media

look at the last item on the page. now tell me how to get to the next page

I think we are currently looking at this topic from different angles, with different objectives - and through different screen sizes. I further believe we should handle items 1 (screen width) and 2 (screen height) separately because item 2 can only be tackled if item 1 can be resolved as suggested with all options in one line.

1. Screen width: With regard to sceeen width I used the browser's developer tools to simulate smaller screen sizes, e. g. 1.024 x 768. See the attached screenshot. Even with that size I believe there would be sufficient horizontal space for pagination, search and page-size, especially when replacing the first/last/next/previous paging texts with s.th. like <<, <, max. 5 page numbers, > and >>.
2. Screen height: For someone with a smaller screen (e. g. a laptop) who uses a page size of 10 records per page to flip through the pages I agree it is easier to continuously click on the same spot as pointed out by Greg, but someone who prefers to use a larger page-size has to go back to the top to flip to the next page.

Although I would like to understand where I might be wrong and what mimimum screen size webtrees is supposed to support, this topic is not of utmost importance to me. I thought to have a good idea, I support ddrury's proposal and I apologize for highjacking this thread while the initial post had been answered already.