Pageby/limit widget: links instead of a form input

[GoogleCodeExporter]

What if the pageby widget (aka pageby_form()) used links instead of the form 
and select input? Yes/no?

The problem we have with the admin-side pages is that each is riddled with 
input fields. Search, upload, import, pageby, multi edit, pagination. All are 
forms.

When everything is a form, it's very hard to move stuff around. You just cant. 
For instance with the widgets, they are either before or after the table, and 
never nested. Plus it makes it hard to tell actual configuration settings that 
change your global configuration from the navigation options.

A patch attached.

Original issue reported on code.google.com by jukka.m.svahn on 22 Feb 2013 at 10:26

Attachments:

• txplib_html.php.pageby.r5288.patch

[GoogleCodeExporter]

That's a yes from me. I'd rather see a standard link-based pagination UI than 
the current form-based one.

Original comment by flaming....@mac.com on 22 Feb 2013 at 10:33

[GoogleCodeExporter]

Gets my vote too.

And if the breakpoints could be exposed via a callback so a plugin could change 
them to arbitrary values that'd be even better imo. I tried that a few years 
ago but the 15, 25, 50, 100 were previously tightly ingrained in the UI so it 
was (annoyingly) ugly to alter, primarily because each list page has an 
explicit reset to '15' in it if the value isn't one of the golden four. But if 
pagination is being revisited as part of a wider change then it might be worth 
investigating again.

Maybe callback_event_ref('admin_pageby', $event, 0, $vals);

or something?

Original comment by stefdawson on 22 Feb 2013 at 10:54

[GoogleCodeExporter]

Original comment by jukka.m.svahn on 22 Feb 2013 at 11:00

• Changed state: Assigned
• Added labels: Milestone-4.6

[GoogleCodeExporter]

Original comment by jukka.m.svahn on 22 Feb 2013 at 11:04

• Changed state: Fixed