You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Nicolas Malin (JIRA)" <ji...@apache.org> on 2018/12/19 12:58:00 UTC
[jira] [Commented] (OFBIZ-10716) Browser Unresponsive when Loading
Entity with Large Results
[ https://issues.apache.org/jira/browse/OFBIZ-10716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724972#comment-16724972 ]
Nicolas Malin commented on OFBIZ-10716:
---------------------------------------
Hi [~devanshu.vyas]
I agree, this method to rendering the pagination is a pain.
Instead a input box we can use this pattern :
[Begin] ... [viewIndex-2][viewIndex-1][viewIndex][viewIndex+1][viewIndex+2] ... [End]
Display Example for a list with 40 pages :
* on page 1 : *1* 2 3 ... 40
* on page 15 : 1 ... 13 14 *15* 16 17 ... 40
* on page 38 : 1 ... 36 37 *38* 39 40
* on page 40 : 1 ... 38 39 *40*
For a number page greater that 100, I'm in favor to stop and set 99+
* 1 ... 13 14 *15* 16 17 ... 99+
Maybe on this case we can set a input box after the '99+' but inn general a huge pagination isn't manageable by human so it's better to restart the search with more constraint in filter or thinking about a consolidate screen
On other idea for the pagination would be the infinite scroll but is't premature at this time.
> Browser Unresponsive when Loading Entity with Large Results
> -----------------------------------------------------------
>
> Key: OFBIZ-10716
> URL: https://issues.apache.org/jira/browse/OFBIZ-10716
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/webtools
> Affects Versions: Trunk
> Reporter: Devanshu Vyas
> Assignee: Devanshu Vyas
> Priority: Major
>
> Recently, I came across a situation where an entity was taking too much of a time(browser asked me to either wait or kill) while loading/searching results in the Webtools application. The entity had close to 5M records, and I checked the server responded timely but the rendering of the screen was taking time.
> When I explored the issue I came across a macro which renders the pagination on the screen, and it had a code block which was causing the screen rendering delay.
> {code}
> <#assign x=(listSize/viewSize)?ceiling>
> <#list 1..x as i>
> <#if i == (viewIndex+1)><option selected="selected" value="<#else><option value="</#if>${i-1}">${i}</option>
> </#list>
> {code}
> This code seems logical enough to me, and what I gather from this is that the list will render a select box with 250,000 options.
> I would like to propose a change in this UI/UX from select box to an input text box so a user can navigate to any page, similar to a navigation input box in a PDF document reader application.
> Please let me know your thoughts on this and share some more ideas to how we can improve/resolve this issue. Looking forward to your replies!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)