[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms
by Mike K (JIRA)
[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ]
Mike K commented on RF-13408:
-----------------------------
Ohh and could you please cache the list data in the client - so that when you scroll (back) you don't have to reload the data again?
> ExtendedDataTable, ajax loading delay of 1000ms
> -----------------------------------------------
>
> Key: RF-13408
> URL: https://issues.jboss.org/browse/RF-13408
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Holger Walter
> Fix For: 5-Tracking
>
>
> When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
> I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener)
> Is it possible to reduce this timeout, or make it configurable via properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13408:
------------------------------------
Ah sorry, I've been living and breathing git for so long that I forget not everyone does. A _Pull Request_ is basically a patch submitted through the git workflow mechanism, a task made easier with the web ui's of github. See this wiki page for more details:
https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA
> ExtendedDataTable, ajax loading delay of 1000ms
> -----------------------------------------------
>
> Key: RF-13408
> URL: https://issues.jboss.org/browse/RF-13408
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Holger Walter
> Fix For: 5-Tracking
>
>
> When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
> I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener)
> Is it possible to reduce this timeout, or make it configurable via properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (RF-13414) showcase - chart demo - event handling - when chart clicked it renders redundant info
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13414?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13414:
-------------------------------
Fix Version/s: 5.0.0.Alpha3
> showcase - chart demo - event handling - when chart clicked it renders redundant info
> -------------------------------------------------------------------------------------
>
> Key: RF-13414
> URL: https://issues.jboss.org/browse/RF-13414
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-output, showcase
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
> Priority: Trivial
> Fix For: 5.0.0.Alpha3
>
>
> When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered:
> {code:none}
> Point with index 3within series 3 was clicked. Point coordinates [1995,10.5]
> Series index: 3 DataIndex: 3 [1995,10.5]
> {code}
> The information is duplicated because it is retrieved in two ways: one from _server side_ -
> {code:xml}
> <h:outputText id="msg" value="#{chartEventBean.msg}"/>
> {code}
> and _client side script_.
> I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ?
> Steps to reproduce:
> # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.js...
> # click on any chart line point and see the output
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms
by Holger Walter (JIRA)
[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ]
Holger Walter commented on RF-13408:
------------------------------------
Hi Brian,
thanks for your feedback.
Just one question - what is a 'Pull Request'?
Regards
wlh
> ExtendedDataTable, ajax loading delay of 1000ms
> -----------------------------------------------
>
> Key: RF-13408
> URL: https://issues.jboss.org/browse/RF-13408
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Holger Walter
> Fix For: 5-Tracking
>
>
> When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
> I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener)
> Is it possible to reduce this timeout, or make it configurable via properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months